The Conjoined Triangles of Senior-Level Development
I liked a lot of the article until I got to<p>&gt;Our hiring “secret sauce” largely stems from the fact that it seems to take significantly less time for someone with leadership and community skills to develop technical skills than the other way around. I’m seeing a large number of people who graduated from code bootcamps 3 and even 2 years ago now handily and gracefully filling the role of senior developer.<p>This statement makes me concerned that they have greatly devalued technical skills. There are not a whole lot of areas where we would consider a three month course plus 2 years experience anywhere close to being senior.  According to <a href="http:&#x2F;&#x2F;www.plumbingapprenticeshipshq.com&#x2F;how-to-become-a-journeyman-plumber&#x2F;" rel="nofollow">http:&#x2F;&#x2F;www.plumbingapprenticeshipshq.com&#x2F;how-to-become-a-jou...</a> to become a journeyman plumber (mid-level) requires a 4-5 year apprenticeship!<p>When technical ability is devalued so much in a company, there is a real danger that this turns into a Dunning-Kruger clique, where &quot;senior&quot; developers that have been programming for 2.5 years automatically favor hiring experienced business people over experienced developers (remember you can turn someone who has never programmed into a senior developer in a little over 2 years)<p>Think about law, medicine, engineering, or the military. We would never call a lawyer that started training 3 years ago a senior attorney. A doctor after 4 years of medical school is called an intern and basically expected to mess stuff up. As mentioned above, even a plumber with 3 years of experience is an apprentice. Why should we as software developers devalue our craft so much?