4 ms·
Honestly, while I love these articles as food for thought, they really aren't the solution to the problem. In my experience, programmers generally have a sense
by erikpukinskis 11y ago
Honestly, while I love these articles as food for thought, they really aren't the solution to the problem.
In my experience, programmers generally have a sense of what parts of their code need to be cleaned up. If they are a newer developer their ideas might be a little screwy. They might not see the root problems, but they know which closets are producing ghouls.
The issue I see is that developers don't think refactoring is a good a use of their time, or someone up the food chain doesn't think it's a good use of their time, or there's just so much institutional inertia making people question whether it's a good use of their time.
If you want your code to be better though, don't read about architectural problems, just take some time to fix the stuff you know is bad in whatever way you know how.
That's better than any article or class and it pays you money and it makes your code more fun.