I’m well aware this post has been asked to death on Reddit, but I couldn’t find anything relevant on Lemmy so I thought I’d give it a shot.

I’m starting my first SDE job next week, and to be honest I’ve never really been a dev in a professional environment before. I’ve had an internship where the bar was very low so I did decently, and a part-time gig where I just assigned myself tickets. Either way I’ve never worked on a larger team or in a specific org before.

Apart from the usual like “ask questions when you’re stuck”, “write proper documentation”, “be proactive”, and “communicate well”, what are some technical things I should be familiar with to make sure I’m not bogging anyone down?

More specifically, are there concepts I should know/I am expected to know of that I might not have learned in university?

  • tiredofsametab
    11•1 year ago

    I’d add things like

    • plan before you act (be that design before code, or something else of the sort)
    • avoid asking the same question multiple times (take notes, study up on things, and try to not ask the same question or make the same mistake over and over)
    • write useful tests and have good test coverage