---
title: "The rebuild stayed with the team."
description: "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."
url: https://coyotiv.com/work/turkish-airlines/
---

1. [Work](https://coyotiv.com/work/)
2. [Turkish Airlines](https://coyotiv.com/work/turkish-airlines/)

# The rebuild stayed with 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.

[Book a call](https://coyotiv.com/work/turkish-airlines/#book) [See all work](https://coyotiv.com/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

The story

1. [A major rewrite, with ownership still in question.](https://coyotiv.com/work/turkish-airlines/#a-major-rewrite-with-ownership-still-in-question)
2. [An internal team prepared to lead implementation.](https://coyotiv.com/work/turkish-airlines/#an-internal-team-prepared-to-lead-implementation)

## 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.

[See all work](https://coyotiv.com/work/)

Personalized products and fulfillment

### [A critical application, ready to run the business.](https://coyotiv.com/work/thefreshener/)

Months of continued development added features and integrations, allowing the company to expand its operations to new product types.

TheFreshener

HR technology and hiring

### [A hiring workflow that had outgrown a single agent.](https://coyotiv.com/work/klareda/)

Klareda could take on larger hiring use cases, with the work divided across agents and their steps available for review.

Contact

## Book a call.

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

- Startups Free architecture review
- Enterprises AI review
- School Apply for the next cohort
[hello@coyotiv.com](mailto:hello@coyotiv.com)