Build Software Teams That Actually Work Together
Most development teams fall apart because people don't know how to collaborate. We teach experienced developers the practical skills they need to build real products with real teams. Our autumn 2025 program focuses on what matters most when multiple people touch the same codebase.
Learn About Our Approach
Why Most Dev Teams Struggle
You've probably seen this before. Someone writes decent code, but when it comes time to integrate their work with three other developers, everything breaks. That's what we address here.
Git Beyond the Basics
Merge conflicts happen. Rebasing gets messy. Branch strategies confuse people. We spend real time on the git workflows that actually matter when five developers are working on interconnected features.
Code Review Culture
Giving feedback without creating team tension is a skill. So is receiving criticism about code you spent days writing. These conversations make or break projects, yet nobody teaches them properly.
Architecture Decisions
When do you refactor versus push forward? How do you convince your team that technical debt needs addressing? Real projects demand these judgment calls constantly.
Communication Patterns
Most developers communicate fine in chat. But explaining technical decisions in writing, documenting assumptions, or arguing for an approach in a design review requires different skills entirely.
How This Program Actually Works
Project Selection Phase
First month involves choosing what you'll build. Not a toy project. Something with real complexity that requires multiple developers and genuine architectural decisions. Past groups have built deployment pipelines, API gateways, and monitoring systems.
Team Formation
We group people based on complementary skills and working styles. Teams of four developers work best for this format. You'll be working with the same people for months, so personality fit matters as much as technical background.
Development Cycles
Three-month build phase with weekly check-ins. Each team works through planning, implementation, integration, and deployment. You'll hit merge conflicts, design disagreements, and scope creep. That's when the learning happens.
Review and Reflection
Final month focuses on what worked and what didn't. Teams present their projects, discuss technical decisions, and analyze their collaboration process. The retrospectives often teach more than the coding itself.
Who Guides These Teams
Our mentors have spent years dealing with the messy reality of team development. They know what happens when codebases grow, teams change, and deadlines press. Here's someone who's been through it.
Linh Nguyen
Technical Collaboration Lead
Spent eight years working on distributed systems where communication failures caused more outages than bad code. Now helps development teams figure out their workflow problems before they ship broken integrations. Previously led teams at two startups in Hanoi that actually survived past Series A.
Multiple Ways to Participate
People have different schedules and learning preferences. Some work better in structured sessions. Others need flexibility to work during their own productive hours. We've built options that accommodate both.
- Weekend Intensive Track: Saturday morning sessions from September through December 2025. Works well if you're currently employed and can dedicate weekend time to focused learning.
- Evening Cohort Format: Tuesday and Thursday evenings starting October 2025. Three-hour sessions that let you maintain your day job while building collaborative skills.
- Async Team Option: Monthly in-person check-ins combined with remote collaboration. Best for people who travel frequently or have unpredictable schedules but still want the team project experience.
- Mentor-Guided Independent: Work with an assigned mentor on your own timeline. Requires more self-direction but offers maximum flexibility for people juggling multiple commitments.
Where Teams Actually Meet
Our space in Vĩnh Phúc handles the technical setup developers need. Reliable network, multiple monitors available, whiteboard walls for architecture discussions. But more importantly, it's set up for the kind of conversations that happen when people are debugging integration problems together.
The room layout supports pair programming naturally. Tables move around easily when teams need to reconfigure for different work styles. Coffee machine gets heavy use during late-night deployment sessions. Previous cohorts have mentioned the space feels more like a working studio than a classroom.
Practical Details
- Located at 201 Quốc Lộ 2 in Vĩnh Tường district, about 45 minutes from central Hanoi
- Open access seven days per week for enrolled participants
- Project teams can reserve the space for focused work sessions
- Equipment includes adjustable desks, external displays, and testing devices
- Kitchen area for long coding sessions when teams are pushing toward milestones