4 ms·
This is fairly basic advice, and it feels a bit insulting to assume I'm just hating on some tech. Obviously, if things were as easy as "here's the immediate and
by stavros 2y ago
This is fairly basic advice, and it feels a bit insulting to assume I'm just hating on some tech. Obviously, if things were as easy as "here's the immediate and unambiguous problem with this approach", I would have gone that way.
Things would be great if the risks were as simple as this. The actual problem is "six years later, the frontend is a ball of spaghetti code and it takes you two sprints to change a component".
How many developers do you think heed those warnings?
- j45 2y agoNot enough. But they will scoff at other technologies old and new.
- willcipriano 2y ago> heed those warnings It's not a warning. It's a functional requirement that you put into the ticket. The project isn't done if the rewritten page takes longer to load than the old one did. Don't ship it, don't pay bonuses based on shipping it.
- stavros 2y agoPlease read my comment more carefully, you're being patronizing. I can't put "I want feature development on this codebase to be faster than two sprints in six years" in the requirements.
- willcipriano 2y agoSounds like you should talk to the person who is actually in charge then.
- stavros 2y agoI'll have a chat with the mirror.