3 ms·
> the answer isn't always splitting it into 5 smaller ones To someone who just read a book about it, it is. I've heard this called "rabbit hole" programming;
by michaelcampbell 2y ago
> the answer isn't always splitting it into 5 smaller ones
To someone who just read a book about it, it is. I've heard this called "rabbit hole" programming; it's function after function after function, with no apparent reason for them other than the line count. It's maddening.
- LandR 2y agoI think the whole Uncle Bob clean code movement has a lot to answer for.
- bluGill 2y agoWhile then Uncle Bob clean code movement has a lot of answer for, it is far far better than much of what came before. I've had to work with 60,000 line functions where #ifdefs worked across brace boundaries ... #ifndef foo break; case SomeCondition: doSomething(). #endif moreCode(); break; I'll take the worse uncle Bob can throw at me over that mess.
- dsego 2y agohttps://github.com/johnousterhout/aposd-vs-clean-code https://github.com/johnousterhout/aposd-vs-clean-code