Re:Things I Learned to Become a Senior Software Engineer
by geofft on Monday September 07, 2020 @07:05AM
(#24398527)
Only in the sense that we demand to be judged by our knowledge and ability and not by our age. If you're going to make a title and say "nobody's eligible for this until they're 40," we'll certainly try to prove you wrong. If you don't make the title, millennials as a group aren't going to care.
[ Parent
| on HN ]
Re:Things I Learned to Become a Senior Software Engineer
by aronpye on Monday September 07, 2020 @07:10AM
(#24398551)
Expertise and experience is broadly correlated. Titles should also be earned, and that requires time in order to deliver work in multiple scenarios that proves your abilities.
Re:Things I Learned to Become a Senior Software Engineer
by aronpye on Monday September 07, 2020 @07:33AM
(#24398665)
> do you agree that the writer of this article has some skills that people new to the industry do not?
No, not really from what I have gleaned from that article. Most of his knowledge seems to be surface level chauffeur knowledge, he never talks about fundamental data and instructions beneath the abstractions. However, it is not fair for me to judge him based on one article alone and without reviewing his work, I’m talking in a more general sense.
Re:Things I Learned to Become a Senior Software Engineer
by geofft on Monday September 07, 2020 @07:20AM
(#24398601)
They are broadly correlated, yes, but you can absolutely spend 20 years learning nothing and 1 learning a lot. Do you think that the writer of this article has not earned their title? If you didn't know about the number of years, would you still come to the same conclusion?
Maybe another way of putting this is - leaving aside the word "senior," do you agree that the writer of this article has some skills that people new to the industry do not?