3 ms·
The average programmer, including someone straight out of college, should be able to understand Absolutely strongly disagree, especially given what's happened
by userbinator 6y ago
The average programmer, including someone straight out of college, should be able to understand
Absolutely strongly disagree, especially given what's happened to the "average programmer" over time. The only way you can maintain (and improve) skill is by NOT continually pandering to the dumbing-down crowd.
In other words, what someone might call "more readable" can actually be "cruft that gets in the way" to someone else.
Related: https://www.linusakesson.net/programming/kernighans-lever/index.php https://www.linusakesson.net/programming/kernighans-lever/in...
- atomicity 6y agoWhat happened to the "average programmer" over time? They seem to be building things that make more money now. Isn't that the main reason companies pay for software engineers? I believe the "decline" is due to the fact that being a software engineer nowadays is more like being a sysadmin or DBA than a programmer of the past. You spend 80% of your time using frameworks and systems that you don't fully understand (or even understand a bit).
- imglorp 6y agoSussman and Abelson got tired of that decline, calling it "programming by poking", and quit teaching SICP. I call it glue and duct tape. Everything is integration these days. Mixed blessing of that resusability we were promised and the poking that goes with it. https://web.archive.org/web/20160504164044/http://www.posteriorscience.net/?p=206 https://web.archive.org/web/20160504164044/http://www.poster... Discussion at the time https://news.ycombinator.com/item?id=11628080 https://news.ycombinator.com/item?id=11628080
- generalk 6y agoI didn't get the context of your quote, and had to go grab the complete quote: > The average programmer, including someone straight out of > college, should be able to understand and work on a well > put-together codebase. I think straight out of college is definitely a little squishy -- someone just out of college may be just out of a theory-heavy CS degree, or a very product-focused CIS degree, or maybe not at all a tech-oriented degree. But let's focus on average programmer. If I have a solid developer, with a year or two in their field, and they can't make heads or tails of the codebase put in front of them? That says more about the codebase than it does of the dev reading it. > especially given what's happened to the "average > programmer" over time And what, indeed, has happened to the "average programmer" over time? From my view, more people today are making computers do new things than ever before; from "secretaries" (oof, that term) maintaining excel spreadsheets that run entire small businesses, to bootcamp graduates who can (with a little guidance) ship fully functional MVPs to prove a line of business. If something's beyond the skillset of a newer developer that's reasonable, but the goal should be to continually make that not the case.