3 ms·
Its not theat IDEs force you to generate code, its that IDEs are quick to hide code. I almost never read java files from start to finish, I just quickly navi
by raducu 6y ago
Its not theat IDEs force you to generate code, its that IDEs are quick to hide code.
I almost never read java files from start to finish, I just quickly navigate by methods/call hierarchy, in some side view, so its really easy for forgive Java for being verbose.
Actually I rarely remember java class names or methods, I just know a heuristic shortcut on how to find them.
After 15+ years of Java, I don't even see the boilerplate code, my brain ignores it like it ignores adds on webpages.
- lmm 6y agoImagine how much more effective you'd be if you'd been working in a non-boilerplatey language and spent 15+ years learning to see the essence of what code was doing, rather than having to expend that mental capacity on skipping over boilerplate.
- raducu 6y agoWhen you work with huge codebases, 80% of the time is spent reading/navigating code. The IDE hides the boilerplate, I really don't mind it.
- lmm 6y ago> When you work with huge codebases, 80% of the time is spent reading/navigating code. And you don't see this as an indication that reducing code size is important?
- raducu 6y agoNot really -- the IDE overview means it doesn't really matter if the codebase is 1X or 2X or 3X the amount of lines. Then, I just think, excluding some horrendous language and some corner cases, experienced programmers are limited by their brain and not the programming language, just like certain languages that are more verbose are spoken faster and terser languages are spoken slower, but the information flow is done at the same speed.