Dennis Doomen<p>One of the challenges in my job as a consultant (typically in the role of <a href="https://mastodon.social/tags/LeadDeveloper" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LeadDeveloper</span></a> or <a href="https://mastodon.social/tags/SoftwareArchitect" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SoftwareArchitect</span></a>) is that I love to code. I believe it's the best way for me to help development teams get the most out of practices like <a href="https://mastodon.social/tags/TestDrivenDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TestDrivenDevelopment</span></a>, <a href="https://mastodon.social/tags/CleanCode" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CleanCode</span></a>, <a href="https://mastodon.social/tags/DRY" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DRY</span></a>, and technologies like <a href="https://mastodon.social/tags/DotNet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DotNet</span></a>, <a href="https://mastodon.social/tags/CSharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CSharp</span></a>, and <a href="https://mastodon.social/tags/TypeScript" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TypeScript</span></a>. However, in most of my assignments, coding is not my top priority. Meetings, discussions, documenting decisions, preparing proposals, and...</p>