5 ms·
I've also seen the other side where the argument is: "we should be doing things correctly from the start" 2 years later: "the maintenance of custom doesn't d
by dirkc 3y ago
I've also seen the other side where the argument is:
"we should be doing things correctly from the start"
2 years later:
"the maintenance of custom doesn't deliver business value and makes recruitment and on-boarding increasingly difficult. We should rewrite in $framework since it's well known, maintained and flexible enough to do whatever they need"
...
- sanitycheck 3y agoThere have been a few occasions where this has led to (literally) years of extra maintenance work for me, as I patiently wait for a team of devs to replace my custom app with v2 using $wellKnownFramework. Sometimes that v2 is eventually abandoned and I'm contracted to build v3.
- marcus_holmes 3y agoAlso seen this where the $wellKnownFramework is dumped before v2 is completed, and the whole thing is rewritten in $newHotFramework for no other reason than the dev team wanted to work in $newHotFramework. There are lots of anti-patterns around this ;)