
Working Together
The Code Belongs to Everyone
Inner sourcing only works when making changes is easy. Standards make that possible.
Architecture is more than code. Teams form patterns too, and those patterns shape behaviour. These pieces look at silos, habits and collaboration through the lens of product engineering.
Working Together
Inner sourcing only works when making changes is easy. Standards make that possible.
Working Together
The chart is not the system. The system is what teams make visible.
Working Together
How AI shifts the balance between improving and starting over.
Working Together
A healthy system creates space to rise, and has the strength to let go.
Working Together
Choice beats compromise.
Working Together
Most people hear “monorepo” and think only of code. In reality, a monorepo is as much about people as it is about software - breaking down silos, unifying standards, and giving teams the context to build faster, smarter, and together.
Working Together
The backlog whispers, source control mumbles. Somewhere in between, the product gets built.
Working Together
An orchestra can rehearse in separate rooms. Each section sounds fine to itself. Strings keep time, brass hit their notes. But the first time they come together the rhythms do not match. What was music alone becomes noise together. The only way to avoid it is to rehearse in the
Working Together
Shouting across the office would be unthinkable. Online, we do it every day. Goodbye Deep Work.
Working Together
We’ve hit a recurring pain point: delivering features often requires coordination across multiple frontend and backend teams, leading to delays, misalignment, and frustration. Here's what we're doing.
Working Together
From six fragmented frontends to one seamless domain - this is how we cut complexity and sped up delivery. The payoff: faster changes, stronger SEO, and a smoother experience for players and developers alike.