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

Post by _fs » Wed, Oct 03, 2018, 5:11 PM UTC

niroast wrote: post #140

rkangel wrote: post #127

Read at least HackerNews and possibly some other tech news site regularly. And then make sure to not get too caught up in the hype for new stuff. As someone working in technology, you are going to be learning new stuff continually (or your usefulness is going to diminish over time). By keeping up to date with tech news, you get a lot of context for what people are using, what's coming down the pipe etc. You may end u…

Do you have any recommendations for news sites that focus on embedded software? I've recently started a career focusing on embedded tech but most of the interesting stuff I've come across online seems to be confined to blogs from the 90's/00's

Post by Alfwich » Wed, Oct 03, 2018, 5:15 PM UTC

Post by kickopotomus » Wed, Oct 03, 2018, 5:16 PM UTC

eitland wrote: post #247

fhood wrote: post #215

Earlier quoted context omitted.

It isn't just a huge hint, most of the time it tells you exactly what the damn issue is. This discussion is blowing my mind. I am honestly speechless. IT GIVES YOU THE LINE NUMBER AND THE FUNCTION CALL AND THE REASON! Why would you ever even attempt to debug without parsing it?

Wait wait wait. Not so fast. i'm one of those programmers who read manuals and stack traces but I have to admit that I've seen my share of both manuals as well as stack traces that didn't make much sense.

Post by scarface74 » Wed, Oct 03, 2018, 5:18 PM UTC

fhood wrote: post #215

andy_wrote wrote: post #203

Earlier quoted context omitted.

I really like your last point "whatever the computer is telling is true from the computer point of view". In a surprising number of coding interviews that I've conducted, I've seen a candidate write an incorrect solution that generates an exception and then attempt to figure out the error almost on first principles, rather than actually reading the exception carefully and thinking about what coding errors could have…

It isn't just a huge hint, most of the time it tells you exactly what the damn issue is. This discussion is blowing my mind. I am honestly speechless. IT GIVES YOU THE LINE NUMBER AND THE FUNCTION CALL AND THE REASON! Why would you ever even attempt to debug without parsing it?

   throw new MyCustomException(“Something Bad happened”);

  //do stuff

   throw;

}

Post by dkersten » Wed, Oct 03, 2018, 5:21 PM UTC

Bahamut wrote: post #99

XorNot wrote: post #49

On the slightly more negative side: everything management tells you that's not in an email will have "never happened" when it's convenient. When you have a conversation with anyone where you think a plan was verbally agreed on, before doing anything your first action is to go back to your desk, write it in an email, send it to them as confirmation and find at least 1 other person, ideally in your reporting line, whic…

I have never had to do this nor seen anything like this behavior in my 6 years of work in the industry. This sounds incredibly in bad faith, and I would probably take it as a signal to go job search for a better work environment if I witnessed this in my day to day.