Ask HN: When are you considered a “senior” programmer?

#1

Post by lollipop25 » Thu, Sep 29, 2016, 4:29 AM UTC

I have been doing web development for as long as I remember. I get by with tools that are needed for the job. I don't fancy the new and shiny. I just get things done fast and done properly.

But I feel like I'm always a step behind the rest. There's this guy in the team knows how to operate Amazon, or this guy who that knows how to use Spring, or this guy that knows how to scaffold a Java app in minutes. Sure, I can write in the Java language but I don't know Spring by heart. I can build and run containers, but I don't know how to launch them in the cloud.

When is one considered to be a "senior" developer? Is there a means to measure where I am? How do I get there?

Re: Ask HN: When are you considered a “senior” programmer?

#2

Post by source99 » Thu, Sep 29, 2016, 5:40 AM UTC

Check out this recent thread: https://news.ycombinator.com/item?id=12557149

Re: Ask HN: When are you considered a “senior” programmer?

#3

Post by peterkelly » Thu, Sep 29, 2016, 6:06 AM UTC

It's a pretty arbitrary term, but based on what you've said, especially "I don't fancy the new and shiny. I just get things done fast and done properly", would be enough for me to label you a senior programmer.

Our industry is way too obsessed with fashion... sooner or later you realise that most of the "new" stuff is largely existing ideas re-hashed in a slightly different form. Senior programmers realise this and can pattern match to understand the role of various new technologies, and learn the details if and when necessary.

How do you get there? You already are, you just don't realise it yet.

Re: Ask HN: When are you considered a “senior” programmer?

#4

Post by supercoder » Thu, Sep 29, 2016, 6:09 AM UTC

When someone gives you the title.

Re: Ask HN: When are you considered a “senior” programmer?

#5

Post by BurningFrog » Thu, Sep 29, 2016, 6:12 AM UTC

It's mostly just a title on a business card and/or org chart.

Some times it's given to people instead of money.

Don't worry about the title. Worry about getting good at what you do, and an asset to your team and organization.

Re: Ask HN: When are you considered a “senior” programmer?

#6

Post by z3t4 » Thu, Sep 29, 2016, 6:15 AM UTC

I would consider you a “senior” programmer? Mainly because you know that you do not know much. While a junior or intermediate programmer think they know everything. There are of course more to it, like when you are stuck on something; you ask the senior programmer, that will probably have solved it ten times in the past. Or if you want to know what the best method is to do this, you ask the senior programmer, that have done it hundreds of times and thus found out the optimal way, with all edge cases included. So I would say it's mostly about experience, and then expertise. Also, a senior programmer should have gone though at least two paradigm shifts.

Re: Ask HN: When are you considered a “senior” programmer?

#7

Post by astdb » Thu, Sep 29, 2016, 6:20 AM UTC

One aspect that would separate a 'senior' engineer from the rest would be initiative, leadership and mentoring ability. These are the engineers who go the extra mile to ensure that the team gets stuff done, and assistance and guidance is provided where required. A senior developer isn't just someone who knows a lot of stuff, but has a time-honed wisdom as well, which they can parlay into their leadership and mentoring duties.

Re: Ask HN: When are you considered a “senior” programmer?

#8

Post by navyad » Thu, Sep 29, 2016, 6:22 AM UTC

sometimes these title can be dangerous.

Re: Ask HN: When are you considered a “senior” programmer?

#9

Post by jkot » Thu, Sep 29, 2016, 6:29 AM UTC

In my experience:

- you are technically competent

- can handle design aspects of full stack (backend, persistence, frontend)

- have enough credibility and confidence to say NO to business people

- you can lead a small team of developers (2 to 5 people)

Re: Ask HN: When are you considered a “senior” programmer?

#10

Post by jakecarpenter » Thu, Sep 29, 2016, 6:30 AM UTC

To me, it is about what they are able to create independently, and the value of the end product.

Senior people have made the right mistakes, wasted weeks of time, and know what to avoid, what to embrace, and what to ignore. A senior dev can understand the requirements and figure out what is important and deliver something without a lot of external input.