How to avoid the biggest tech co-founder pitfalls?

Question

Are there any guides for tech co-founders who are managing the architecture, planning, hiring, for the first time and cover the biggest pitfalls (eg painting yourself into an architectural corner, technical debt) and how to avoid them?Even if its with non-technical solutions like having a mentor etc. Just the big ticket items. It needn't be too nuanced but any advice appreciated.

Jugurtha · Accepted Answer

I post this from time to time, including here: https://news.ycombinator.com/item?id=28422944 with some editing. Recycling some replies. More context here https://news.ycombinator.com/item?id=26182988
It addresses different topics, from nitty gritty to communication, alignment, product development, to architecture, etc. Doing these little things, like reducing information asymmetry and conducting meetings well will tremendously help into building a team that can operate in the fog (you made sure everyone is aligned, the rationale is explained, so they can make pretty good decisions in times of uncertainty).
Understanding codebases:
- https://news.ycombinator.com/item?id=19924100
Testing pipelines, scaffolding, issue templates:
- https://news.ycombinator.com/item?id=26591067
Making the most out of meetings and leveraging your presence:
- https://news.ycombinator.com/item?id=22873103
Product development:
- https://news.ycombinator.com/item?id=22827841
Giving a damn:
- https://news.ycombinator.com/item?id=20356222
If I disappear, what will happen:
- https://news.ycombinator.com/item?id=25008223
Consulting, understanding the problem your "client", who can be your manager, has:
- https://news.ycombinator.com/item?id=24972611
On taking notes. When you're told something, or receive a remark, make sure to make a note and learn from it whether it's a mistake, or a colleague showing you something useful, or a task you must accomplish.. don't be told things twice or worse. Be on the ball and reliable:
- https://news.ycombinator.com/item?id=24209518
Product, architecture, and impact on the team:
- https://news.ycombinator.com/item?id=24503365
Onboarding new hires to a codebase, what if it were you, improve code:
- https://news.ycombinator.com/item?id=22860716
Tips to learn from videos:
- https://news.ycombinator.com/item?id=22710623
- https://news.ycombinator.com/item?id=22723586
Communication with the team:
- https://news.ycombinator.com/item?id=21598632
- https://news.ycombinator.com/item?id=21614372
Reduce information asymmetry, template for taking minutes of meetings to dispatch to the team. Notes are in GitHub/GitLab so the team can access them, especially if they haven't attended:
- https://news.ycombinator.com/item?id=21427886
More meeting notes. Reply to a person who had trouble talking in corporate meetings:
- https://news.ycombinator.com/item?id=20323660
Communication, alignment:
- https://news.ycombinator.com/item?id=24177646
Useful things for the team and product that add leverage:
- https://news.ycombinator.com/item?id=21808439
Management involvement as a spectrum:
- https://news.ycombinator.com/item?id=22715971
Researching topics:
- https://news.ycombinator.com/item?id=25922120
Keeping up with a firehose of information:
- https://news.ycombinator.com/item?id=26147502
Fractal Communication: communication that can penetrate several layers of management and be relevant to people with different profiles and skillsets:
- https://news.ycombinator.com/item?id=26123017
Remote work, use existing tooling and build our own. Jitsi videos, record everything, give access to everyone so they can reference them and go back to them, meetings once a week or two weeks to align:
- https://news.ycombinator.com/item?id=26179539
Write better. Always.