0
AxSch
6y

Recently started a new role as a junior dev(second role). Three weeks in and I'm already starting to loathe the work setup & process.

Last week I was asked to fix a bug due to them not having anything in the pipeline for me(I had finished my allocated tasks for the sprint). There was no spec to this, no visible steps to replicate the error & no tests in place to validate it was working... I thought I had fixed it, even had one of the seniors reviewed it on my PR but also I walked him through my possible solution resulting in us moving forward with the "improved" solution.

After a bank holiday, I've come back to find that the "fix" I had deployed doesn't solve the problem at all. So here I am after 3.5hours of flying blind with a bug that I'm still not able to reproduce, bored and frustrated asf. Not to mention, that the codebase has little to no consistency, a lot of legacy and almost no form of tests.

Am I overreacting to this as junior?

Comments
  • 0
    @Edwin88 Hmm I don't know though, the industry isn't really flourishing with junior roles... And I'd feel a bit out of sorts suggesting ways if improving things since I'm only a junior...
Add Comment