4 ms·

Yeah, I stopped reading after this line. Sorry, but if you call yourself "senior" with 6 years of experience you've lost all credibility in my book.

wink 4y ago
The author said that, we don't know if the mentioned person does it.
throwaway4233 4y ago
Seniority is the fact or state of being older or higher in rank or status than someone else. Within an organisation, a senior engineer could be the engineer with the most experience with the codebase everyone else is working on. I do agree that certain habits or experience from working for additional years might be missing, but as the first engineer of a codebase, IMO, there will always be something to learn from them. Which makes the article credible enough to warrant a read.
pcthrowaway 4y ago
Years of professional experience isn't a great metric of time steeped in software practices. There's a difference between someone who did a bootcamp and worked for 6 years compared to someone who started contributing to open source software at the age of 12, studied computer science, and then went into the industry. The latter might be more experienced at 1 year than the boot camp grad at 6 years.
runevault 4y ago
I wouldn't instantly go that far. There are people who can be senior in 6 years. People truly that good are the exception, not the rule though.
MikeTheRocker 4y ago
Much of the most widely used software in the world comes out of mid 20s so-called Senior Engineers in Silicon Valley (and other major US metros). Gatekeeping on the basis of years of experience is naive and unproductive. IMO "senior" is a function of behavior not time. At FAANG, levels are formally defined by traits. For example, a senior engineer can plan and lead 6-12 month long projects, delegating some parts of the implementation to others where appropriate. I personally was fulfilling this definition at 25 and I know several dozen others in similar situations.

wink 4y ago

The author said that, we don't know if the mentioned person does it.

throwaway4233 4y ago

Seniority is the fact or state of being older or higher in rank or status than someone else. Within an organisation, a senior engineer could be the engineer with the most experience with the codebase everyone else is working on. I do agree that certain habits or experience from working for additional years might be missing, but as the first engineer of a codebase, IMO, there will always be something to learn from them. Which makes the article credible enough to warrant a read.

pcthrowaway 4y ago

Years of professional experience isn't a great metric of time steeped in software practices. There's a difference between someone who did a bootcamp and worked for 6 years compared to someone who started contributing to open source software at the age of 12, studied computer science, and then went into the industry. The latter might be more experienced at 1 year than the boot camp grad at 6 years.

runevault 4y ago

I wouldn't instantly go that far. There are people who can be senior in 6 years. People truly that good are the exception, not the rule though.

MikeTheRocker 4y ago

Much of the most widely used software in the world comes out of mid 20s so-called Senior Engineers in Silicon Valley (and other major US metros). Gatekeeping on the basis of years of experience is naive and unproductive. IMO "senior" is a function of behavior not time. At FAANG, levels are formally defined by traits. For example, a senior engineer can plan and lead 6-12 month long projects, delegating some parts of the implementation to others where appropriate. I personally was fulfilling this definition at 25 and I know several dozen others in similar situations.