3 ms·
Mixed in with this may also be architectural decisions based from a "let's just spin something up quickly" mentality. Those foundational architectural decision
by cellularmitosis 2y ago
Mixed in with this may also be architectural decisions based from a "let's just spin something up quickly" mentality. Those foundational architectural decisions have a way of becoming set in stone, long after the freelancers have left, dooming the project to scalability and latency problems which seem to linger forever.
- carlmr 2y agoI've seen equally many projects never achieve lift-off because they were stuck in analysis paralysis trying to architect MVP for scalability, extensibility etc. And even if that succeeded you often end up with fear of change because the complicated architecture can't be touched. It's really important to have the right balance here, but KISS and YAGNI are often easier to scale when you need it, than the reverse. If you don't have the mentality that the MVP must never be rewritten.
- switch007 2y ago> Mixed in with this may also be architectural decisions based from a "let's just spin something up quickly" mentality That, plus "they're probably going to fire us in a year anyway, who cares" thinking And "we don't need to understand the business domain, let's just MVP", which they get away with because they would get accused of not being agile if they did boring stuff like trying to understand the business I refer more to bigger off shore consultancy shops than individual freelancers