Code Review Mastery Program

Learn to analyse, critique, and improve software with systematic review techniques that work across languages and frameworks. Our autumn 2025 cohort starts in March.

Register Your Interest

Three Paths, One Outcome

We built this around how people actually learn. Some need structure. Others want flexibility. A few thrive in group settings. Pick the format that fits your life.

Intensive Track

Twelve weeks of focused learning with structured milestones. You'll work through progressively complex codebases, spending evenings on practical reviews.

  • Twice-weekly live sessions with industry practitioners
  • Review assignments based on real commercial projects
  • Peer feedback loops with cohort members
  • Direct mentor access via dedicated channels

Self-Paced Track

Same content, your timeline. Complete modules when it suits you over six months. Perfect if you're balancing work commitments or unpredictable schedules.

  • All course materials accessible immediately
  • Monthly check-in sessions with mentors
  • Community forum for questions and discussions
  • Extension options if life gets complicated

Team Track

Designed for development teams wanting consistent review standards. We adapt the curriculum to your tech stack and company context.

  • Customised content matching your codebase
  • On-site or remote delivery options
  • Group workshops with your actual projects
  • Post-program support for implementation
Senior code review instructor Freya Lindquist teaching systematic analysis techniques Code quality specialist Petra Kovačević discussing review methodologies

Who Teaches This

Freya spent eight years doing code reviews at Australian fintech companies. She's seen everything from brilliant architecture to absolute disasters. Now she teaches others how to spot issues before they become expensive problems.

Petra comes from the open-source world where peer review isn't optional. She'll show you techniques that scale from small teams to massive distributed projects.

Both instructors still work on commercial projects. They're not teaching theory they learned years ago.

"The best code reviews don't just catch bugs. They transfer knowledge, establish patterns, and build shared understanding across the team. That's what we teach people to do."

When Things Happen

We run two main intakes each year. Autumn programs start in March. Spring sessions begin in September. Team tracks can start anytime with enough notice.

Autumn 2025

March 17 – June 6

Our next intensive cohort. Applications close February 28. We cap enrollment at twenty people to keep sessions productive.

  • Evening sessions Tuesday and Thursday
  • Weekend workshops in weeks 4, 8, and 11
  • Final project presentations early June
  • Certificate issued upon completion
Spring 2025

September 8 – November 28

Second annual intake with identical curriculum. Good timing if you need winter to prepare or prefer learning when weather improves.

  • Same structure as autumn program
  • Applications open in July
  • Early bird pricing until August 15
  • Option to defer to 2026 if needed

What You Actually Do

People learn review skills by reviewing code. Sounds obvious, but you'd be surprised how many programs skip the practical bit.

Students collaboratively reviewing code during practical workshop session

Real Projects, Real Feedback

Each week you'll receive codebases with deliberate issues ranging from subtle to catastrophic. Some are security vulnerabilities. Others are performance problems waiting to happen. A few are just badly structured but technically functional.

You submit your review. Then you see what others caught. Sometimes you spot things everyone else missed. Other times you wonder how you overlooked something obvious. Both teach you something.

By week eight, most students report they're reviewing code differently at their day jobs. They notice patterns they previously ignored and ask better questions during pull requests.

Building Your Review Process

Everyone develops their own approach over time. We give you frameworks to start with, then help you adapt them as you gain experience.

You'll learn systematic techniques for reading unfamiliar code quickly, identifying architectural concerns before diving into details, and communicating findings without sounding like a jerk.

The final project involves reviewing a significant codebase and presenting your findings to the group. It's nerve-wracking and valuable in equal measure.

Code review documentation and systematic analysis methodology materials