DEV Community

Cover image for Go from Junior to Senior developer in a couple of hours

Go from Junior to Senior developer in a couple of hours

Thomas Hansen on September 06, 2022

I have 25 years of experience as a professional developer, and 40 years of experience in total. I have been Head of Development, Project Lead, CTO,...
Collapse
 
simplegeek profile image
SimpleGeek

This is an interesting perspective. I agree that junior devs sometimes focus on things that senior devs have rightfully learned to ignore. "Boring" tech is boring for a reason - it's an effective way to solve a problem. SQL and jQuery are great examples of tech that gets bashed for being boring, but you can still solve problems very effectively with them. They're reliable and understandable tools.

I'm not sure Joel was necessarily criticizing all the higher levels of abstractions and tools that come out, though - I think he was pointing out that you'll never get anything done if you spend all your time running down every hot, new tech solution that comes out. Just my take, though, and it is an excellent article. :-)

To get back to the main subject, the seniors I've known that I felt truly deserved their title have had superior debugging skills, superior ability to read through, understand, and reason about other people's code, a good sense for what makes maintainable code, a greater technical skill set (knowledge of the language/ecosystem, how to solve its problems) and the ability to teach those skills to others. Wouldn't you say that these skills are really part of being a senior dev too?

Point well made, though. Always follow the money!

Collapse
 
polterguy profile image
Thomas Hansen

I think he was pointing out that you'll never get anything done if you spend all your time running down every hot, new tech solution that comes out

Of course. Some new tech is interesting.

Wouldn't you say that these skills are really part of being a senior dev too?

Yes, and of course I am exaggerating - The point still stands ... ^_^

Collapse
 
cheetah100 profile image
Peter Harrison

The difference between junior and senior is responsibility. A junior isn't responsible for anything. A intermediate is responsible for their own work. A senior is responsible for mentoring, product design, and the whole product. You don't learn it all in a day.

Collapse
 
polterguy profile image
Thomas Hansen

This is of course true, but you never learn it if you keep on chasing all the "latest new tech stuff" ...

Collapse
 
nombrekeff profile image
Keff

Sure buddy, sure!

Collapse
 
nombrekeff profile image
Keff

I think it's not all about speed of delivery. Just because you provide a solution fast it does not mean it's good. I would much rather that you spend a bit more time and deliver a robust system, than delivering a inferior product in half the time.

Even if the delivered system is powerfull and cool I would not make you a senior because of that, that's bullshit!

Collapse
 
polterguy profile image
Thomas Hansen

I think it's not all about speed of delivery

Actually, you're wrong. Speed leads to quality. However, thank you for the comment, you gave me an idea for my next article ^_^

Thread Thread
 
nombrekeff profile image
Keff

Would you mind expanding on why you think that?

Thread Thread
 
polterguy profile image
Thomas Hansen

The experiment with pottery shows that if you create 10 pots in the same time as somebody creates 1 pot, you end up creating better quality at the end of the time frame. Hence, more speed, better quality in the end, and more learning ...

Thread Thread
 
nombrekeff profile image
Keff

This makes no sense to me if i'm completely honest... do you mean that by doing 10x more work you're learning 10x faster, hence becoming 10x better at what you do? That could make sense, but I still think that spending a bit more time on something results in a better product

Thread Thread
 
polterguy profile image
Thomas Hansen • Edited

Check out the ceramics pottery experiment. It's a universal truth. If you can do 10 projects in the same time as your neighbour does 1 project, the quality of what you're delivering will soar, while the quality of your neighbour's product will fall behind. Quantity is a pre-requisite for quality. And I didn't say it made sense, I didn't say it was easily understood, but it's a scientific fact, proven many times over and over again ...

Resulting to a conclusion, which is as follows; Basically, the only difference between Tiger Woods and me is that Tiger has swung a bajillion times, while I've swung some few hundreds of times ...

If you find it difficult to believe in, bring it up with Alpha Zero ... ;)

Thread Thread
 
nombrekeff profile image
Keff

I see. This makes a bit more sense, basically practice makes perfect. I'd change speed for practice, but I kinda get it...

Thread Thread
 
polterguy profile image
Thomas Hansen • Edited

I'd change speed for practice

This is the largest paradox about the pottery experiment. All participants had the same amount of time available - Still those delivering 10 pots outperformed those only delivering 1 pot (in the same amount of time) on neutral quality metrics ...

Basically, their last 2 pots were significantly higher quality than those only delivering one pot ...

And yes, I know it totally doesn't sound logical or reasonable, but it's proven over and over again ...

Collapse
 
decker67 profile image
decker

Clickbate + Advertising