|
Firstly, you got your _first_ swe job in August. Companies that hire juniors for first jobs shouldn't expect to have fully formed contributors from the gate. It's probably a year or two before you should be expected to be a reliable contributor. I know with todays inflation in "senior" titles, it comes earlier, but personally, I have low trust in anyone who hasn't done the job for 10+ years. As more concrete advice:
Own the fact that you are green & new. Ask the "dumb" questions. If you are unsure on how to start something, ask "what would be a sensible, concrete first outcome on the way?". Ask, ask, ask. Also, as a junior, it is immensely valuable to pair on problems and code with more senior members. So if it's not a thing, maybe suggest if you could try pair programming from time to time in the team. It reduces bugs and errors even for very senior people. Finally, mistakes happen. Sure, try to avoid them, but don't freak out when they happen, just find a solution to correct it. Every mistake you make is a mistake you are less likely to make again (but some of them, you will make again, and that's fine).
If you are able to do expensive mistakes on production systems, I'd suggest it's more of a process problem than a people one. |