3 ms·
Simple is robust. Focus on product market fit (PMF) and keep things as straightforward as possible. Create a monolith, duplicate code, use a single RDBMS, ado
by jumploops 2y ago
Simple is robust.
Focus on product market fit (PMF) and keep things as straightforward as possible.
Create a monolith, duplicate code, use a single RDBMS, adopt proven tech instead of the “hot new framework”, etc.
The more simple the code, the easier it is to migrate/scale later on.
Unnecessary complexity is the epitome of solving a problem that doesn’t exist.
- kaptainscarlet 2y agoYeah, I would focus on a better user experience over a beautiful backend architecture.
- ghomem 2y ago... and this!
- ghomem 2y agoMore of this.
- dgan 2y agoCan you expand om what of code duplication you deem reasonable?
- jumploops 2y agoEarly in a project you see a lot of similar code paths, and so it’s often tempting to take the logic from two or three e.g. API routes and merge the “clean” abstraction into single piece of logic both routes can call. Over-time this “clean” abstraction adopts a bunch of optional parameters based on the upstream API routes, leaving you with an omni-function that is more convoluted, and thus harder to change, than if the API routes weren’t overly optimized from the get-go. As a personal rule, I’ll let myself copy something 3 times before taking a step back and figuring out a “better” way.
- dgan 2y agoA very reasonable approach indeed