"Attitudes That Lead to Maintainable Code" Well that assumes the code is the problem and not the programmer. The code might be perfectly maintainable but the p

"Attitudes That Lead to Maintainable Code" Well that assumes the code is the problem and not the programmer. The code might be perfectly maintainable but the programmer lack skills to do just that. I've only seen very rarely really-hard-to-maintain code, and there were of two sorts: 1) over-engineered pseudo-senior object-oriented spaghetti plate -- generally resulting from methods that supposedly make the code more maintainable. 2) logically-wrong over logically-wrong spaghetti plate -- the kind of code that programmers hate to admit they do: simply logically-wrong code. On the other hand, I've seen plenty of beginners making critics about a code that is supposely hard-to-maintain whereas the problem was them because: 1) they don't know how to read and learn a code base. They typically start working on a projets and they don't read the codebase. They jump on a task. They actually never read the codebase, but only piece of it. 2) they think the code is "obfuscated" whereas it is, well, just not. The programmer is just a beginner that needs to learn how to read a boolen expression for example (typically: var ok = cond1 && !cond2 || cond3 -- omg the code is obfuscated!).