7

Lets make a rant before going to bed

Who had the marvelous idea that a developer's proeficiency could be measured by years?

So at my new job Ive been waiting for credentialls, server access software installation, etc ( i know i know but thats for another rant ) and all that idle time has given me opportunity to crawl in the company's sharepoint page which has the career path for a software developer, since Im a student Im listed as trainee, but after that I have to wait 3 years + certifications to be considered as senior and then be able to hop to next hierarchy level Software Designer and then another three years to be able to become a software architect. So my point, as I was seeing this I thought "I dont wanna wait 6 years to become a software architect, Im going to be better faster in order to become needed and make them promote me faster"

The thing is Ive always wanted to become a softwsre architect and learning that I have to wait 7 years to be considered a proeficient architect just makes me mad.

Pd: One of the requirements for a senior developer is knowing Lines of code time stimation

Comments
  • 1
    7 years seems pretty reasonable to me. But you have a point, it should probably be measured by number of successful projects.
Add Comment