That one senior dev in the office told me to stop copying code from Stack Overflow and actually read the error messages first

Dude just handed me a printout of my terminal with the errors highlighted in yellow and said 'the computer is literally telling you what's broken' - took me 2 hours to realize I was just ignoring half the output. Has anyone else had that moment where someone points out you're skipping the obvious fix?

3 comments

3 Comments

the_alex16d ago

That's a solid point, but older devs usually know exactly where beginners get stuck. They've seen the same patterns over and over. Ignoring the error output is probably the biggest time waster for new coders.

brooke_jones17d ago

Yo, for real though - did the advice actually stick or did you slip back into old habits once he wasn't watching?

young.thomas16d ago

Aw man, I gotta push back on that a little. Good advice sticks because you see the results yourself, not because someone's watching you. Once you make a change and actually feel the difference, you don't really want to go back.