Skip to content

The rebuild stayedwith the team.

Turkish Airlines was preparing to rewrite a large web application. Through workshops on its own code and architecture, we helped the frontend team develop the technical foundations to take responsibility for the work.

Client
Turkish Airlines
Sector
Aviation and enterprise web applications
Our role
Architecture workshops, Vue.js training, and code review practices
Today
Implementation kept with the internal frontend team

A major rewrite, with ownership still in question.

The team wanted to replace a large existing web application. An earlier external rewrite had not reached completion, and management was considering outsourcing the work again.

The internal frontend team needed to prepare for both the technical demands of the rebuild and a move to Vue.js. Understanding the existing application’s problems was an essential starting point.

An internal team prepared to lead implementation.

The company kept implementation with its own frontend team, supported by experienced external architects. The workshops helped the team make a case for owning the work and provided shared architecture and review guidance.

The outcome of the engagement was a team better prepared to take on the rebuild, with a common technical foundation and practical ways to work together.

How it went

Use the real codebase as the classroom.

  1. Codebase

    Learn from the existing architecture

    We began with a full-day analysis of the codebase. Engineers identified problems module by module, turning their experience of the existing system into lessons for the next architecture.

  2. Proposals

    Have every engineer propose a design

    Engineers at different experience levels developed their own architecture proposals. We compared the approaches together and combined their strongest elements, giving the team a shared basis for the rebuild.

  3. Vue.js

    Develop framework knowledge in context

    Vue.js training covered the framework’s practices and the choices involved in applying it to a large application. The learning was connected to the team’s own architecture and delivery needs.

  4. Practice

    Agree on everyday engineering practice

    We worked through coding conventions and pull request review. Those practices, together with architecture guidance, formed a handbook the team could use as development continued.

The result

An internal team prepared to lead implementation.

The company kept implementation with its own frontend team, supported by experienced external architects.
In-house
Shared architecture and review guidance the team could use as development continued.
One handbook

More work

More work.

Contact

Book a call.

Free, 30 minutes, with an engineer. Tell us what you are working on.

  • StartupsFree architecture review
  • EnterprisesAI review
  • SchoolApply for the next cohort
hello@coyotiv.com
What brings you here?
How did you hear about us? Optional

An engineer replies by email.