What I learned as a Development Director Shadow at GitLab

Photo by Avel Chuklanov on Unsplash

Starting the program

I learned about the program by posts on the slack channel for the Secure stage development team. My experience started with an introduction call the week before, where I prepared for the program by:

  • Obtaining access to Wayne’s calendar
  • Going over what is expected of the program
  • Discuss what Wayne is currently working on

Notable Meetings

As an engineering manager shadow I attended many of Wayne’s zoom meetings in order to gain perspective of his day-to-day.

Photo by Campaign Creators on Unsplash

Notable Merge Requests (MRs)

I assisted with reviewing a number of merge requests and issues. Wayne would send me a few each day to show what he has been working on, so that I can provide feedback.

Photo by Desola Lanre-Ologun on Unsplash

Conclusion

On the last day of the shadow program, I met with Wayne to discuss what I have learned and ways we can improve the program. I went ahead and suggested the following:

  • Director should continue to report a list of merge requests and issues of interest daily — This provides the shadow with something to work on and look into each day aside from meetings

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Fernando Diaz

Fernando Diaz

198 Followers

Senior Technical Marketing @ GitLab 🦊, Developer 👨🏻‍💻, Alien 👽