[HN Gopher] Advice I Wish I Knew as a Junior Developer
___________________________________________________________________
Advice I Wish I Knew as a Junior Developer
Author : raheelrjunaid
Score : 20 points
Date : 2025-09-28 15:36 UTC (7 hours ago)
(HTM) web link (raheeljunaid.com)
(TXT) w3m dump (raheeljunaid.com)
| AznHisoka wrote:
| I echo the importance on working on legacy code. I think the
| ability to work on legacy code, and figuring out how to make
| changes to or refactor it is one of the hallmarks of an excellent
| developer in my eyes. It shows they're resilient enough to not
| get discouraged easily.
|
| If a junior developer complains about legacy code, or just gives
| up, it shows they're resilient enough just won't put the work in
| when things get hard
| raheelrjunaid wrote:
| I agree! Your sentiment reminds me of ThePrimegean's time at
| Netflix and how he said he got good at the stuff nobody wanted
| to get good at.
| vman512 wrote:
| my advice: treat debugging as your core competency. When you get
| stuck, avoid asking for help until you've tried pretty hard to
| solve it yourself. If your any of your peers gets stuck with an
| interesting problem, go help if you have spare time
| raheelrjunaid wrote:
| Yep, it would be annoying if every junior/intern I was
| mentoring asked for help without attempting to at least Google
| it first.
|
| Although, on the other end is people that spend way too much
| time attacking the problem with limited context, and then
| asking for help after the day is almost done.
| crossroadsguy wrote:
| I wish someone had told me: "Work just for money. Everything else
| is hogwash. Period."
| horns4lyfe wrote:
| Write LinkedIn style slop posts I guess
___________________________________________________________________
(page generated 2025-09-28 23:01 UTC)