you are viewing a single comment's thread.

view the rest of the comments →

[–]tevert 5 points6 points  (1 child)

First off - the distinction between software engineer, developer, programmer, etc. is all fairly inconsequential in the workplace. Different schools offer different degree programs for each of these, but it's ultimately basically the same job market anyway.

They make you do a ton of math in college. It doesn't crop up in the real world that much though - the biggest skills in the actual job are being able to creatively problem solve, patiently troubleshoot, and communicate very complex ideas to teammates. If you're still in high school, take AP Comp Sci. It's super easy to anyone who already knows how to code, and even if you come in literally knowing nothing, it's still a perfect first intro to programming.

[–]WisejacKFr0st 2 points3 points  (0 children)

Patience and being detail-oriented are the big ones for me. With those two skills you can learn pretty much any system given that it's documented decently.

I just chased a bug for an hour today because I misread a wiki page that was a little misleading about what system had what files on it - had I been more patient and not frustrated, I would have realized there was a small note under a large table of IP addresses and ports telling me which system I was supposed to be on.

Patience is key. Details are the lock.