|
|
|
|
|
|
by alex_lav
1122 days ago
|
|
|
Just really learn to internalize "Off the shelf solution", "We can fix it later" and "Minimum viable" and you'll be fine (or, statistically probably not, but that's usually unrelated to technical decisionmaking). Database schema: the minimum viable database schema that we can fix later Product analytics: What off the shelf solution can we find to satisfy a minimum viable analytics setup I've worked with countless engineers at startups that are addicted to building overly complex solutions in-house. They're just wasting time and money (aka runway). The thing many devs don't seem to internalize is that lots of startup development (outside of "hard" tech, where the tech _is_ the startup) is very very unsexy/unflashy. Configuring cheap SaaS products to satisfy your need as fast as possible. Anything that keeps you in business is good enough, and if you continue to exist you can fix it later. Literally everything other than your secret sauce should be answered by 1-3 of the above mentioned mantras. |
|
|