Not sure if this is the right subreddit, but here goes:

I’m a project manager in a with 2 full-time developers and two engineers who work on smaller software projects from time to time in case its needed, e.g. test tools and such.

Now, my full time devs are both working on different (Embedded C and Android), while the test tools are developed on various depending on what is needed.

How would I with a team where developers reviewing the of another developer may not be able to understand anything other than on a very surface level? Currently, our most senior developer acts as a sort of gatekeeper for software releases, where he goes through all the committed before it is pushed to master. This approach removes the learning effect from reviews and only one developer’s eyes read the bits of .

I would like to have a simple, yet efficient setup that doesn’t waste the developers’ time so they can focus on the important bits. I would also like to be a part of the process to have a better insight into what goes on “under the hood”, as I have a fair bit of experience in development myself.



Source link

LEAVE A REPLY

Please enter your comment!
Please enter your name here