Ask Experienced Devs

21 readers

1 users here now

Icon base by Delapouite under CC BY 3.0 with modifications to add a gradient

founded 1 year ago

MODERATORS

Ategon@programming.dev

What makes a new grad developer look competent to senior devs and managers? (lemmy.ml)

submitted 1 year ago by randromeda@lemmy.ml to c/ask_experienced_devs@programming.dev

8 comments fedilink hide all child comments

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?

you are viewing a single comment's thread
view the rest of the comments

[–] balder1993@programming.dev 2 points 1 year ago* (last edited 1 year ago) (1 children)

Paying attention and caring about the quality of your output go great lengths. I’ve seen even supposedly senior devs doing a shitty job out of laziness to check what they’re doing.
Getting proficient with git and it’s usefulness. It is one of the single tools that can make you incredibly more productive.

[–] randromeda@lemmy.ml 1 points 1 year ago

I have commitment issues and git doesn't let me push without commits. Am I not cut out to be a developer? /s