4 ms·
I'm amazed that there aren't more discussions about code readability -- the judicious use of whitespace, the choice and conventions for variable naming (includi
by randcraw 11y ago
I'm amazed that there aren't more discussions about code readability -- the judicious use of whitespace, the choice and conventions for variable naming (including plurals and uppercase vs lowercase to denote semantics other than classes), and the sundry other choices we routinely make. Like language choice (and hungarian notation), coding style has a big impact on code legibility and can greatly clarify the intended semantics.
I'd love to see a range of rigorous experiments that explore which conventions are more comprehensible and maintainable. It's curious that after 30+ years of software development, such practices seem to have been minimally explored, much less clinically assessed. I'm puzzled that we programming pros are satisfied with groupthink (like OOP), apocrapha, and unending religious debates.
So where's the 'engineering' in software engineering?
- collyw 11y agoIn the last 6 months I have inherited two codebases. What bothers me more than any of this is the unnecessary complexity people have introduced. Complex code for doing very simple stuff. Way more database calls than are needed. Joins in the app. Python written in the style of Java. Loads of loops that could be eliminated with a bit of thought up front and a marginally different design. Instead everyone gets caught up worrying about small stuff like this. Sure it makes a difference, but in the grander scheme of things the architecture makes a far bigger difference.