Yeah, it sounds to me like the article could have been titled "How I learned to stop over-engineering and love to code." The "being vs. doing" duality seems forced to me, and doesn't always align with the overall message of creating solutions that are oriented around solving a problem rather than engineering for its own sake.
