7 Signals That You Aren’t a Competent Senior Developer (Yet)
<p>The speed of promotion in software engineering roles is astounding. That isn’t an issue in itself, but sometimes the “wrong” people are being promoted to senior roles. Wrong in this context are those that are fast at completing simplistic programming tasks, rather than those who focus on collaboration and helping the team. <strong>Any senior should place the team at the heart of their focus.</strong></p>
<blockquote>
<p>Who cares about people?</p>
</blockquote>
<p>Over time I’ve seen “senior” developers behave in the same way one might expect a junior. Difficult to read code, comments describing what rather than why, and code that shows the author thinks SOLID is something to do with geometry.</p>
<p>The <a href="https://medium.com/@tsecretdeveloper/the-peter-principle-destroys-programming-teams-a51b1a9c1c5a" rel="noopener">Peter Principle</a> benefits a certain type of poor coder. These “seniors” strongly exhibit these 7 tell-tale signs of their junior skills.</p>
<h2>Arrogance Clouding Judgement</h2>
<p>It’s fairly normal for software engineers to be judgmental. As a developer moves through the competency hierarchy, their behavior should change and mature.</p>
<p>Specifically, when software engineers earn the <strong><em>senior</em> </strong>badge, they should listen more than speak. Have an open mind about finding solutions, rather than pressing for their own idea. It doesn’t matter where the solution comes from, what matters is the problem is solved.</p>
<p><strong>To think you’re always right? A junior trait.</strong></p>
<p><a href="https://medium.com/@tsecretdeveloper/7-signals-that-you-arent-a-competent-senior-yet-72c8a7be917f"><strong>Click Here</strong></a></p>