If you were a defender of code quality, no one would be able to tell. You would look like any other engineer. You could be a quality assurance engineer, trying to figure out how the application is supposed to work. You could be the young engineer trying to make a mark at the company you work at. You could be a program manager, a development manager, a lead engineer trying to teach code quality. You may well have an affiliation with Amazon, Apple, Google, or Microsoft. But you are hard to identify just from the way you think—which is good, because someday soon dark forces may try to prevent you to release a high-quality project that meets the user requirements, on time.
You understand this sounds crazy, but it true. You know that a small group of manipulators, operating in the shadows, telling management everything is going smoothly. You know that they are powerful enough to abuse common software engineering practices without retribution. You know that the open-source community is their handmaidens, in partnership with Stackoverflow and the secretive denizens of the underworld.
You know that only dotNetDave stands between you and a damned and ravaged code world. You know that a clash between good and evil coding practices cannot be avoided, and you yearn for the awakening that is coming. And so, you must always be on guard. You must shield your ears from the scorn of the ignorant. You must find those who are like you. And you must be prepared to fight for code quality.
You know all this because you believe in D.
Discover more from dotNetTips.com
Subscribe to get the latest posts sent to your email.
