Live data from Hacker News

Ask HN: What is your best advice for a junior software developer?

news.ycombinator.com

31–40 of 460 posts

Re: Ask HN: What is your best advice for a junior software developer?

#31
1) If you're not a native English speaker, always improve your English. 2) Start your open source side project and work on it in your spare time. 3) Improve your skills by reading books and attending online courses. 4) Change your job/project every year.

Re: Ask HN: What is your best advice for a junior software developer?

#34

If you’re the smartest person in the room then you’re in the wrong room.

This quote is so silly, and misused. It’s like one of those facts about Einstein that you’ll see on Facebook.

For one, in this context, a junior developer will rarely be the smartest person in the room. So it’s really terrible advice for the context.

I think it’s really terrible advice in general though, the places I’ve learned the most is exactly when I’m the smartest person in the room, doing stuff like mentoring or teaching.

In fact I do part time work as an external examiner at IT educations in my country, exactly because they teach me a lot. I’m almost always the smartest person in those rooms, but by evaluating i relearn/refresh things that I haven’t touched in a while.

Aside from that, you’re almost never in a room where there isn’t an opportunity to learn. Maybe you’re the best programmer in the room, maybe you’re the best architect, but you’re very rarely the best at everything, and the modern workplaces thrives the most from teams, in which everyone is the best at something, because they become more than their individual sums by cooperating.

Re: Ask HN: What is your best advice for a junior software developer?

#35
Learning how to write decent software just takes time and comes with a lot of failures in between. Good peers know that and you should too. But they will often leave you with some easy stuff to get you productive and it is very easy just bury yourself in this work. Try to observe what your seasoned peers a doing, listen to conversations between them, ask questions if possible. Things that happen away from keyboard is nothing someone teaches you in school, but there is a lot to learn from that.

Re: Ask HN: What is your best advice for a junior software developer?

#36
post #3

Never call yourself a junior software developer - fight to keep “junior” out of any title. Read books/practice software design patterns and learn how to write tests. (Unit, integration, end to end)

>Never call yourself a junior software developer - fight to keep “junior” out of any title.

I'd second this. "Junior developer" is generally just used to pay developers less.

Re: Ask HN: What is your best advice for a junior software developer?

#37
post #26

try to be autosufficient. if you have a problem, try to fix it yourself. try googling, reading source codes if you have to. it's very annoying when people come to me with questions that could have been resolved by doing 5 minutes of research online.

Inversely – and I've seen loads of people, myself included, with this problem — learn when to quit and ask for help.

Re: Ask HN: What is your best advice for a junior software developer?

#39
I had written this before [0] in a very different context but still relevant to your question.

1. Think Big. I have seen many people who aimed higher from the beginning and did manage their way up (e.g., becoming a VP in just ten years, that too in a large company).

2. People skills is a must. You should be thinking of people or organizational challenges all the time, or you'll miss the mindset to rise significantly up.

3. Many people complain about their team leads, managers or senior leaders. This usually happens because these senior are working at a higher level of responsibility and ambiguity than you are. You should rather be thinking what would you have done if you were in their position. Understand the challenges they have, by directly asking if needed. This will not only help develop your relationship with them, but also position you to develop the skills needed faster, without yet being in the position of responsibility that they are in!

4. There is a lot of entropy in any team/organization, and unfortunately also a lot of people who are increasing it. Be the one who reduces the risks and brings order to the chaos, whose judgment can be trusted. Keep in mind for this that the real challenges are often not on technology side (in other words, if you think technology challenges are more critical, you are perhaps missing the big picture).

5. Try to become irreplaceable for the team/company in your project and beyond. In my experience, this will not come in your way as [6] suggests. You must however not get limited to the tools and technologies specific to the company, or else your market value will suffer within a few years.

6. Never say (or even feel) anything bad about anyone ever, keeping Hanlon's razor in mind [1]. But then, how do you deal with the stupidity? Well, their stupidity is your opportunity. (I created this out of Jeff Bezos' famous quote, "Your margin is my opportunity." [4])

7. Do not let yourself be masked from political issues around. A good manager would aim to mask you [5], but that can curb your growth since you won't develop the skills needed to master and survive corporate politics while being masked.

8. There are books available today that teach you corporate politics [2-3], showing how easy it is for anyone to do it, and how difficult it is to counter. Reading these books should be a required reading for anyone aiming to go significantly high. And trust me, it's better to learn this from books or from other people's experience than learning this stuff the hard way. (The latter would be painful for one, and second, you may never actually learn.) I have read [2] and felt that I should have read it earlier.

9. Ask questions whenever you do not understand something or if your own thoughts do not align with the decisions being made. Of course, be polite in this (e.g., "I was wondering if option X also has been considered" instead of "why are we not going for option X"). People around would be happy to explain to you while also developing trust in you, and often would take the suggestion if it will actually reduce their mental burden. The sooner the better in asking questions.

[0] https://news.ycombinator.com/item?id=16490323

[1] https://en.wikipedia.org/wiki/Hanlon%27s_razor

[2] https://www.amazon.com/dp/0743262549/

[3] https://www.amazon.com/dp/0312332181/

[4] https://www.inc.com/jessica-stillman/7-jeff-bezos-quotes-tha...

[5] https://news.ycombinator.com/item?id=16488447

[6] https://news.ycombinator.com/item?id=16489904

Re: Ask HN: What is your best advice for a junior software developer?

#40

If you’re the smartest person in the room then you’re in the wrong room.

This quote is so silly, and misused. It’s like one of those facts about Einstein that you’ll see on Facebook. For one, in this context, a junior developer will rarely be the smartest person in the room. So it’s really terrible advice for the context. I think it’s really terrible advice in general though, the places I’ve learned the most is exactly when I’m the smartest person in the room, doing stuff like mentoring o…

The advice is for the long haul and if you work out side of v high end RnD which you may have to do in order to get a decent salary its quite common.

Also just because your the teacher doesn't mean your smarter than all your students you may know more.

Post reply on HN