3 ms·
The author's getting tripped up on whether Uncle Bob is suggesting to use "correctness techniques" and missing the forest for the trees a bit. Uncle Bob's centr
by 0xbadcafebee 6y ago
The author's getting tripped up on whether Uncle Bob is suggesting to use "correctness techniques" and missing the forest for the trees a bit. Uncle Bob's central theme of advice is basically to stop thinking in cargo cults. "If I just do X Technique / use X Tool, my code will be better" is a fast track to "I am doing all 100 Techniques / using all 100 Tools and my code still has bugs. Maybe I just need new Techniques / Tools."
Nothing is enough. As humans, we build things shittily. And the chaos of the universe also makes sure that everything slowly becomes shitty over time. You should consider techniques as a small part in a grander scheme, which is the holistic implementation, operation, and maintenance of the products your code makes up.
I have been running systems for a while. I've seen a lot of code - some of it even good. It still makes for shitty products, because the people writing the code are thinking more about the code than how it's operated/maintained/supported and how the user experiences it. There is no technique or tool or code that can ensure the rest. Show me the best code in the world and I will show you an unhappy user.
- buescher 6y agoBob's article dismisses a whole host of techniques as a setup to preaching the "discipline" of unit testing. You're projecting a bunch of your own frustration with user experience and software lifecycle issues onto his vagaries. User experience is its own engineering domain, by the way, and most people, including developers, are terrible at it without exposure to the best ideas in it. It's not just a matter of "thinking" about user experience (or lifecycle requirements, for that matter).