"Each class in his own file...." I think there's a subtle trap where programmers think their code isn't nicely organized unless they themselves have written al

"Each class in his own file...." I think there's a subtle trap where programmers think their code isn't nicely organized unless they themselves have written all those abstraction layers. But one of the virtues of picking up a framework is precisely that it's already there for you. Hopefully it matches what you need. But within reason, if you pick a good framework for your task, you don't then need to layer on another set of abstractions... it's already got them! It's completely sensible to pick up a framework and bash out 2000 lines of code that simply spends the abstraction budget of the core framework. It's half the value of the framework in the first place. Obviously if you're going to build another 100K of lines on the framework you may need to bring some additional organization to the party, but the space of "framework + 2K lines of code" is a pretty rich one.