Live data from Hacker News

Stop Being a Junior

kentcdodds.com

11–20 of 27 posts

Re: Stop Being a Junior

#11
I feel this article is not very good. It focuses too much on externalities.

One thing that I often find is that there is too much self doubt and impostor syndrome in the modern generation of kids and I think that is warranted.

A big part of why they feel that way is because they haven't really thought how a computer works, haven't build large enough systems, haven't written enough code to understand why Uncle Bob and Clean Code are bad solutions.

Once they start looking at hard skills instead of managing up or other things at the office, that's when I feel they will think and act like a senior.

There is no way of shortcutting it. You have to pay your dues in terms of understanding why certain code is bad and certain code is good and that only comes with writing largish systems and testing your theories. Also build stuff outside of web dev.

If you feel like a junior or have impostor syndrome, it might well be because you are one.

Re: Stop Being a Junior

#12
Alright this is an OK-ish motivational piece to never let anyone put you in a box I guess...

> In fact, I was just a step below architect in a quarter-billion dollar organization only 4 months after graduating from university.

Oh, come on, Kent. Really? Can we qualify this guy's blog as spam yet?

Re: Stop Being a Junior

#13
> Welcome to the software development world" only to find out they've been working as a software developer for over a year and a half already.

Ugh, you think 18 months is a long time? Programming is hard, just the technical part takes a lot of reps, but navigating the long term implications and social/business interfaces are what make the difference between an effective tech lead and an NNPP.

Here’s a tip: stop worrying about labels. Spend a decade obsessively honing your craft. Think from first principles. Ask difficult questions. Move around and find the smartest programmers you can to learn from. Confidence comes from hard-won abilities, not playing mind games with yourself about titles.

Re: Stop Being a Junior

#14

I feel this article is not very good. It focuses too much on externalities. One thing that I often find is that there is too much self doubt and impostor syndrome in the modern generation of kids and I think that is warranted. A big part of why they feel that way is because they haven't really thought how a computer works, haven't build large enough systems, haven't written enough code to understand why Uncle Bob and…

Why are uncle Bob and clean code bad solutions?

Re: Stop Being a Junior

#16

Alright this is an OK-ish motivational piece to never let anyone put you in a box I guess... > In fact, I was just a step below architect in a quarter-billion dollar organization only 4 months after graduating from university. Oh, come on, Kent. Really? Can we qualify this guy's blog as spam yet?

[deleted]

Re: Stop Being a Junior

#17

> Welcome to the software development world" only to find out they've been working as a software developer for over a year and a half already. Ugh, you think 18 months is a long time? Programming is hard, just the technical part takes a lot of reps, but navigating the long term implications and social/business interfaces are what make the difference between an effective tech lead and an NNPP. Here’s a tip: stop worry…

I'm glad I wasn't alone in feeling frustrated while reading this article. I just passed the year mark after switching careers; the clouds are parting and I'm beginning to tackle more complex tasks with my ever-growing experience and wisdom, but "What do senior developers do in your company? Do that instead of the things junior developers do. That's it." is absurd.

If you're getting bored with the menial tasks that you're being given, ask your boss if they think you're ready to handle more complex work -- jumping in the middle of projects way over your head in an effort to pretend you aren't a junior dev is foolish.

Re: Stop Being a Junior

#18

> Welcome to the software development world" only to find out they've been working as a software developer for over a year and a half already. Ugh, you think 18 months is a long time? Programming is hard, just the technical part takes a lot of reps, but navigating the long term implications and social/business interfaces are what make the difference between an effective tech lead and an NNPP. Here’s a tip: stop worry…

[dead]

Re: Stop Being a Junior

#19
This is just like, my opinion, man but I think titles are just food for our egos. I think developers should focus on two things: 1) doing work that you enjoy. 2) take a good long hard honest look at yourself and determine your value, then find an employer that agrees.

The only advice from the article I liked was:

> Even if it's just "hey, can I come sit in on that meeting?" Take notes for yourself of anything you're unfamiliar with and ask about those things later.

I love sitting in on meetings just to take notes. Recently some Sr Developers and our DBA set up a weekly meeting to discuss overhauling our database schema and I asked to sit in. Even though most of what I heard aligned with what I already knew I still got a lot of value in just listening to other people's opinions. The DBA was a fountain of knowledge when it came to the nuances of using SQL Server.

Re: Stop Being a Junior

#20
post #19

This is just like, my opinion, man but I think titles are just food for our egos. I think developers should focus on two things: 1) doing work that you enjoy. 2) take a good long hard honest look at yourself and determine your value, then find an employer that agrees. The only advice from the article I liked was: > Even if it's just "hey, can I come sit in on that meeting?" Take notes for yourself of anything you're…

> This is just like, my opinion, man but I think titles are just food for our egos.

Yes, but that doesn’t mean that we should ignore the importance of what the title signifies. Titles may not be so important to you, but they are to others and they also help signify how others should treat you. If you were a very senior engineer, I would expect that you act very differently than a junior engineer, and the easiest way to understand what expectations I should have for you is your title.

Post reply on HN