Why I Strive to be a 0.1x Engineer
Throughout my career I&#x27;ve definitely been lumping the skills described in this article about not doing work in with the whole &quot;10x developer&quot; catch phrase.<p>Like:<p>Customer needs a CMS.<p>Clyde looks at the requirements for the CMS.  He sets off to write hundreds of thousands of lines of code by himself, complete with CI, continuous deployment, tests and documentation because he is a very good developer.  Through the course of the project he leverages his years of experience and background in CS and engineering to make a well-factored body of software that will be maintainable for years.  He did this in only a couple months.<p>Bob looks at the requirements for the CMS.  He thinks &quot;I know, I will use a good application framework and an ORM&quot;.  Bob writes a couple thousand lines of code with all the tests and stuff that Clyde had.  Bob&#x27;s tests and app code, however, are more focused on the customer&#x27;s needs, making in maintainable for anyone who can read the documentation of the software he&#x27;s chosen to use.  It takes him a couple weeks.<p>Alice looks at the requirements for the CMS.  She realizes the customer will do just fine with Wordpress with a couple of tweaks. She sets up a hosted blog so nobody has to actually maintain it. She has better shit to do with her time.<p>Alice did the least work but that doesn&#x27;t make her less productive.  You&#x27;re solving problems. If you do work to solve those problems, fine, but having more &quot;output&quot; doesn&#x27;t make you go from a 1x to a 30x engineer.