Summary
Modernising a technology stack while keeping a growing product organisation moving is one of the harder balancing acts a company faces, and three of the engineers leading that effort at twimbit share how they approached it. Guiding principles shaping the team's technology choices come into focus, including the move to Next.js and the adoption of a monorepo structure for managing shared code across projects.
Participants discuss what automating continuous integration and continuous deployment has meant in practice for a team balancing speed with reliability, and where the biggest obstacles have surfaced during the modernisation process. Building the habits and processes a relatively young engineering team needs to thrive as both the codebase and the organisation scale also comes up, from documentation discipline to how decisions get made without a large legacy hierarchy to lean on.
The panel closes by reflecting on the mistakes teams commonly make when modernising legacy systems, offering a candid look at lessons learned rather than just the finished architecture, including where the temptation to over-engineer a rebuild tends to creep in.
- Perspectives from three engineers on monorepo structure and CI/CD automation
- Lessons on avoiding common pitfalls during a technology stack modernisation
What separates a technology modernisation effort that sticks from one that quietly reverts under pressure?
Schedule a call with Twimbit analyst to learn how we can help you.
Already a Twimbit client? Log in