21–30 of 129 posts
I was a bit worried about the title saying "Senior Software Engineer" because this may trigger people. But, surprised that all the discussions are about this, instead of the content.
It's easy to become a senior software engineer, anyone can do it with these simple steps: 1. Open an index.html, include a javascript file and write an alert or console log. 2. Create your own company. 3. Title yourself as a senior software engineer. Joke aside, during my career I've met several senior software engineers that are anything but and several "normal devs" that are a lot better than most people who have t…
If I start my own company, I’ll be the Supreme and Exalted Overlord . Not something silly like a senior dev.
While it’s not impossible. I find it hard to believe anyone could become senior (in terms of actual skill) in two years.
It's easy to become a senior software engineer, anyone can do it with these simple steps: 1. Open an index.html, include a javascript file and write an alert or console log. 2. Create your own company. 3. Title yourself as a senior software engineer. Joke aside, during my career I've met several senior software engineers that are anything but and several "normal devs" that are a lot better than most people who have t…
If I start my own company, I’ll be the Supreme and Exalted Overlord . Not something silly like a senior dev.
While it’s not impossible. I find it hard to believe anyone could become senior (in terms of actual skill) in two years.
But what "senior engineer" means varies from company to company. So it becomes a loose term.
To start with, "Senior" and related titles basically mean a person who doesn't need much hand-holding. This might be related to time spent, but often you find there's a lot of variation. People I consider senior software engineers have a can-do-anything vibe about them. They have a wide range of skills in the field, and have that T-shaped experience profile: there's some area they seem to know everything about, and t…
While it’s not impossible. I find it hard to believe anyone could become senior (in terms of actual skill) in two years.
This is a very subjective question. I think a senior engineer is an engineer who can develop features without hand-holding. The technical leader should be able to say, "Develop feature X. These are the requirements." and then not worry. But what "senior engineer" means varies from company to company. So it becomes a loose term.
In pretty much all companies those were just called "software engineers". Seniority requires decision making and longterm leadership skills, not just implementation work.
To start with, "Senior" and related titles basically mean a person who doesn't need much hand-holding. This might be related to time spent, but often you find there's a lot of variation. People I consider senior software engineers have a can-do-anything vibe about them. They have a wide range of skills in the field, and have that T-shaped experience profile: there's some area they seem to know everything about, and t…
I feel I can do anything as well, because if I can't then I will simply find a way to learn it, because to me it's not a question of whether I'm capable of learning it but how fast I'm capable of learning it. So I'd be careful with that vibe as a heuristic ;-)