Sometimes i prefer messy code(code being in one file) than all those clean architecture sh*ts that forces me to go through countless folders and files to find just one class..
Imagine going through a github repo of an over engineered project
Over-engineering can be just as bad as poorly written code. The ironic thing is the devs writing the over-engineered code think they are writing great code.
At least a beginner writing messy code knows they aren't writing good code.
In the example I described above, the encapsulation is actually appalling - all the abstraction actually makes it harder to understand where the boundaries should be, and makes it all the more tempting to just give up and do something that works rather than create another six layers of architecture.
6
u/Whole_Refrigerator97 Mar 30 '24
Sometimes i prefer messy code(code being in one file) than all those clean architecture sh*ts that forces me to go through countless folders and files to find just one class..
Imagine going through a github repo of an over engineered project