5 ms·
That's the thing here. Knuth can easily juggle far more complexity in his head than the average programmer, and that's fine for software that only he has to mai
by mcv 7y ago
That's the thing here. Knuth can easily juggle far more complexity in his head than the average programmer, and that's fine for software that only he has to maintain. But when something needs to be maintainable by average programmers, you need to write for them and avoid that complexity.
- squiggleblaz 7y agoWho's writing for the average programmers? It's the average programmers. How can average programmers write code that is sufficiently abstract that it hides the complexity they can't handle? How can they change that code when it doesn't work? Does every company of 5 devs need to have a PhD?
- mcv 7y agoEverybody who writes code that's going to be supported by other people, should be writing for the average programmer.
- hyperpallium 7y ago> How can average programmers write code that is sufficiently abstract that it hides the complexity they can't handle? Well said. Hiding complexity is harder than handling it. Designing an effective way to expose it for use amounts to (part of) a "programming system" [Brooks]. So it's library writers who hide the complexity for average programmers, with a "programming product": stdlib, open source project or (rarer these days) commercial "engine". When there is no such library, we get the current state of our art: many projects failing.