|
|
|
|
|
|
by rev_bird
3952 days ago
|
|
|
This is really interesting, thanks for responding. It seems, though, like the vast majority of these problems aren't coming from the necessary evils brought about by outdated technologies -- it just seems like inexperienced (or just...bad) coders trying to shove stuff out the door on the cheap. If the people who made the original project had been "using" React, I'd imagine you'd just be dealing with the busted CSS and mangled JSX everywhere. This raises an interest point that I think I was missing before -- "imposing structure on your developers via solid frameworks and tools." The idea that even if you don't need the functionality of a particular framework, a framework's prescriptive way of doing things might reduce enough of the variance in styles to make a big project more coherent. |
|
|
Having a framework in place minimizes the impact of those "bad programmers" to just a single ui component, or api route, or database migration.
Not having a framework in place means that that intern or contractor from india can now introduce bugs that impact the entire system and are nearly impossible to track down.
I feel like it shouldn't be such a hard sell to get software engineers to admit that structure and consistency are good things.