3

I’m the only junior software engineer at a small startup where I do mostly web development, as well as other bits and pieces (automation, ci/cd, etc)

Our software team is extremely small so we do not have anyone dedicated to QA. I usually just ask a team members with related experience to review my merge requests. So if I have a merge request for our ci/cd, I ask the software engineer with the most ci/cd experience to review the MR.

Recently I realized that my MRs will usually sit for days, and sometimes weeks without the reviewers taking a look. And when they eventually do, they don’t even run the code. It seems like they just gloss over it and look for obvious syntax or logic errors.

It makes me feel as if my code and efforts do not have much value to our team.

It also pisses me off because whenever a issue happens in our codebase, me and my code is the first thing blamed even if my code is not the issue

Is this typical in other companies? Or is this something I should speak to my boss about?

Comments
  • 2
    Testing isn't usually part of code review.
  • 1
    I think it's also possible that people are just busy with their own work.

    When I was a junior. I didn't even have a chance for code review. We were a month behind the day we started on a project lol
  • 0
    @electrineer I did not know that lol thanks for informing me

    @iceb yea I think you are right. I just wasn’t sure if this is typically how things are or if something is wrong that I should fix
  • 0
    In small companies you do not really have the time to do anything but quick checks to make sure the guy didn’t delete the entire db by accident.
Add Comment