Don't design for infinite scale. Design for what your customers actually need. Solve their problems now, not what they may theoretically face in 1-2 years and iterate #SoftwareEngineering #scalability
Don't design for infinite scale. Design for what your customers actually need. Solve their problems now, not what they may theoretically face in 1-2 years and iterate #SoftwareEngineering #scalability
How often has someone presented a solution without a problem?
Whenever something doesn't pass the sniff test, ask, "What problem are we trying to solve?"
It gives you a better understanding of the problems facing the organization, and maybe it kills bad ideas #firstprinciples
I've seen this a lot when juniors start to near senior. They've learned enough patterns and "best practices" from books and apply them way too liberally. The good devs start to realize they can pull back and become more pragmatic, solving for the problem instead of figuring out what pattern to use
Do you think this is lack of will or skill?