Picking Your Tech Stack For Dummies (and the future)

Picking a tech stack in an early-stage startup is framed as one of the most important decisions. The post says the right choice depends on where the company is now, not on future possibilities that may never matter.

Reading notes

#

• If the startup is still in prototype mode, has fewer than four developers, and is in do-or-die mode, the advice is to use what you already know and optimize for coding speed.
• A bad choice is tying the company to a technology that loses mindshare and support, because that can force painful migrations later.
• To pick likely winners, the text points to popular technologies, technologies that have stayed popular for years, technologies used by major companies in core parts of their products, and technologies maintained or formally supported by public companies.
• The stack should be mostly boring, because product engineering is usually about combining technologies and building models and business logic rather than doing something novel from a technical standpoint.
• Being too boring can make hiring harder, so the text recommends a balanced stack with proven technologies and some emerging winners.
• As the company grows, tech that does not scale should be replaced intentionally, but major transitions should be made sparingly.