How does it work?

My Comprehensive Go Code Audit is a fixed-length engagement that takes place initially over a 2- to 3-week time period, with ongoing support for 3 months. I will audit a single code repository^* worked on by a single team of up to 10 engineers^*. Here's how it works:

• Step 0. Prerequisites. As soon as payment is received, I will:
  • Send you a signed copy of my standard NDA, so you can rest assured that your code is safe in my hands.
  • Add your team to my private Slack group, for communication for the duration of the engagement
  • Work with you to schedule the two interactive workshops (see below)
• Step 1. Share the Source Code. Before beginning, I will need access to your source code. Ideally, this is via GitHub, GitLab, BitBucket, or whatever online version control you currently use, but I can also audit a zip file of your Git repository. When sending a zip file, you are encouraged to encrypt it (PGP public key available upon request).
• Step 2. Workshop 1 (1-2 weeks after payment) During the first interactive workshop, I will:
  • Present high-level findings on the health of your Go code base
  • Identify the five highest-impact areas I see where your team can improve the code, its design, or structure
  • Provide suggested action steps to implement these changes, and where appropriate, discuss any design trade-offs that may need to be considered
  • Send you the "laundry list" of lower-impact items I discovered during my audit, which may be worth adding to your longer-term, lower-priority improvement backlog
  • Take questions from the team, and requests for topics for the second work shop. Usually after the first workshop, the team has identified one to three areas for a deep dive during the second work shop
• Step 3. Workshop 2 (1-2 weeks after first) The agenda for the second workshop is mostly up to your individual team. Common topics include deep-dives into specific areas of concern such as error handling in Go, how to write Go middleware, or anything of particular relevance to the team. This session often includes mob programming, where we implement a feature togethr as a team.
• Step 4. Ongoing Support It's my goal to help your team succeed and achieve its goals with Go. As such, every code audit includes a minimum of three months of ongoing support (via Slack). Any time anyone on your team has a question for a Go expert, just ask me on the designated team Slack room, and I'll answer within one normal work day. If you would like more than three months of support, that is of course an option. Let's chat about what your team needs to succeed!