5 ms·
I worked the majority of my career at an "elite" Japanese corporation. It's one that has a brand pretty much synonymous with "Quality." Many of my peers were am
by ChrisMarshallNY 4y ago
I worked the majority of my career at an "elite" Japanese corporation. It's one that has a brand pretty much synonymous with "Quality." Many of my peers were among the finest engineers and scientists in the world.
I was often the dumbest guy in the room, and I'm smarter than the average bear.
Dealing with these folks could be infuriating. Every time I would suggest orthogonal approaches (because, like, software is different from hardware), I'd be called "lazy," or "sloppy."
It made me write good code, though.
If those folks saw the way I work now, they'd be horrified. They'd call me a "reckless cowboy," or something to that effect.
But most folks in today's software industry think I'm a stuck-up prig.
I work quickly. I leave good, highly-documented code, that lasts a long time (For example, one of my C SDKs was still in use, 25 years later), and I don't want to toss my cookies, whenever I look at my old code (sometimes, though, I shake my head, and wonder what I was thinking).
I'm my own best customer. I'm the one that usually needs to go into my old codebases, and tweak them, so I write code that I want to see, in the future.
I've come to realize that the term "over-engineered" can mean a couple of things:
1) This code is too naive, complex, and byzantine, which makes it prone to bugs, inflexible, and difficult to maintain; or
2) I don't understand this code. That makes it bad.
I used to have an employee who was "on the spectrum."
Best damn programmer I've ever known. Crazy awesome. Had a high school diploma, and regularly stunned the Ph.Ds in Japan.
His code was written very quickly, was well-designed, well-structured, well-documented, bug-free, highly optimized, and an absolute bitch to understand.
- idopmstuff 4y agoI think the other thing that "over-engineered" can mean is code that's unnecessarily good for its purpose. If you're building a quick demo of a product to get user feedback, and you write perfect code that's highly maintainable, you've wasted time - better to throw together something as quick as you can and rebuild it if it's actually going to be used by/sold to customers. That's really overengineering in my mind - doing a poor job with the quality/speed tradeoff given the purpose of the thing you're building.
- ChrisMarshallNY 4y ago> If you're building a quick demo of a product to get user feedback, and you write perfect code that's highly maintainable, you've wasted time In my experience, this is a trap. The demo almost always becomes the product, because upper management sees the demo, and says "Hey! It's almost done! Let's ship!" This is how you end up with these gigantic Frankencodebases. These days, my test harnesses and demos are generally "ship quality." It also means that I can mine them for snippets, without holding my nose. I have spent a great deal of time, however, practicing, so that I write top-shelf code, by habit. These test harnesses are often churned out very quickly.
- plasticchris 4y agoThis is why some people will make the demos rough in some obvious ways before presenting them.
- vineyardmike 4y agoMy advice to younger engineers is ALWAYS to remember demos don’t get rewritten. if a demo appears works, some one will want to ship it as is.
- nerdponx 4y agoAt the same time, not everything you ship needs to be a master work. "Working well enough to ship" is not the same as "flawlessly architected". It also depends a lot on the business context, whether you can trust leadership to respect technical debt or not.
- ChrisMarshallNY 4y ago> whether you can trust leadership to respect technical debt or not Most C-suite folks, these days, are running leveraged up the yin-yang, financially; so I suspect that "tech debt" is almost meaningless. I'm trying to remember if I have ever known an [American] manager, that gave the slightest damn about tech debt... ... Nope. I got nothing.