Summary
Keeping a fast-growing product organisation's engineering foundation current, without disrupting the teams building on top of it, requires more than adopting new frameworks. Three of the architects behind twimbit's technology modernisation discuss the principles guiding their decisions, including the shift to Next.js and the reasoning behind consolidating projects into a monorepo structure.
What automating continuous integration and deployment pipelines has meant for a small, fast-moving engineering team comes up, along with where friction has shown up most during the transition. Participants also reflect on how a young technology team builds the habits, documentation practices and decision-making processes needed to keep pace as both the codebase and the wider organisation continue to scale, including how ownership is distributed once a monolith gives way to a more modular structure.
An honest look at the mistakes teams commonly make when modernising legacy systems closes things out, offering practical lessons rather than a polished account of a finished architecture, along with a candid take on what they would do differently with hindsight.
- How a monorepo structure and CI/CD automation support a scaling engineering team
- Common pitfalls to avoid when modernising a technology stack
What does it take to modernise a technology stack in a way that actually holds up as an organisation scales?
Schedule a call with Twimbit analyst to learn how we can help you.
Already a Twimbit client? Log in