4 ms·
Then what ? That junior dev could produce working software, and fix the css issue later (if needed). Give that "senior CSS developer" a day and figure out how
by revskill 3y ago
Then what ? That junior dev could produce working software, and fix the css issue later (if needed).
Give that "senior CSS developer" a day and figure out how to manage state, then what you get is a crap.
- nicoburns 3y agoThe problem is that if the end state you want is a clean codebase implementing your use case, that’s also easy to modify and extend, then the mess such a developer will produce is a much worse starting point than starting from scratch.
- gibbitz 3y agoBusiness doesn't fund "fix it later" -- it just becomes tech debt. You have to push to do it right the first time or approve merges you can live with in perpetuity.
- sfn42 3y agoYeah that's gonna work out great when the entire app is built using weird overcomplicated solutions to simple problems, let's just clean it all up later! Doesn't matter how you write your code as long as it seems to work, well deal with all the bugs we discover later! The proper way to do it is to do code reviews and teach newbies how to do things like this. Ideally they should have asked about it(or just googled) before the review. I think "well just fix it later if needed" is asking for trouble and you're basically just writing legacy code.