But that doesn't mean it's a good way to write software. Accept that most of what devs do is fairly mundane, and focus your mental effort where it's actually needed and you'll be a better developer than anyone who obsesses over the performance/elegance/extensibility of every line they write. Obviously it's a spectrum, and it takes balance, but I know which side I'm currently on!
> I have wasted countless hours on needlessly efficient
> implementations of the wrong interface, or, on the other
> end of the spectrum, coming up with the perfect interface
> for code that will never be used again.
SAME HEREI know I've certainly done enough optimizations that left the code clearer and shorter (despite often being more verbose with naming), while being more performant due to shedding whatever messy, tortured approach was in use before. Enough small gains like this have come out of code where I was the original author that it isn't a case of conceit.
Clear and simple code can frequently beat clever code, regardless of which metric you choose to apply from the "performance or understandability" bag.
This does mean you can't skimp on good design, making your project a collection of modular, replaceable components.