zlacker

not sure what he's on about, 100% of the tech debt I have experienced is from people doing too much rather than too little

my advice to future coders is to try to put your entire project into a single file...you'll have to drop every bright idea, abstraction, layer, etc just to make it palatable...and the world will thank you

>>oldper+(OP)
> my advice to future coders is to try to put your entire project into a single file...you'll have to drop every bright idea, abstraction, layer, etc just to make it palatable...and the world will thank you

My advice to future coders is to never do this. Clearly we don't work in projects or IDEs that are in any way similar.

>>oldper+(OP)
> 100% of the tech debt I have experienced is from people doing too much rather than too little

“The tactical tornado is a prolific programmer who pumps out code far faster than others but works in a totally tactical fashion. When it comes to implementing a quick feature, nobody gets it done faster than the tactical tornado. In some organizations, management treats tactical tornadoes as heroes. However, tactical tornadoes leave behind a wake of destruction. They are rarely considered heroes by the engineers who must work with their code in the future”

A Philosophy of Software Design. John Ousterhout

>>oldper+(OP)
what kind of projects do you work on where this is reasonable? The only projects I've been able to reasonably keep in a single file are small (<250ish LOC, maybe even 500 depending on language) hobby projects.