Skip to content

Yusuf Aytas Posts

Addressing Technical Debt

Tech debt occurs when we solve a software problem with our limited understanding of the business at the time. We start building a solution to get feedback as early as possible. By the time we deliver the software, we might have accumulated some burden. The debt metaphor comes into play. Instead of spending additional time on business requirements, we prefer to deliver software early. Hence, we borrow…

3 Comments

Building a Technical Vision

A technical vision is a plan to reveal long-term technical goals for a team, organization, or company. The technical vision outlines goals like high availability of services, reducing toil for the team/s, large-scale changes to make further changes easier. A goal should specify a concrete outcome, time boundary, and relevant action. The outcome would translate into key results. The time boundary establishes the time to reach the…

Leave a Comment

Manager as a Service

What would a manager as a service look like? What kind of systems a manager would resemble? How can you describe a manager’s responsibility through various systems? Here’s my take. A good engineering manager is like An integrated development environment (Idea, Visual Studio, Xcode). S/he helps to maximize engineer productivity. S/he is highly technical and provides guidance where the engineer needs. S/he gives relevant suggestions based on…

Leave a Comment

Service Overload Strategies

A service overload happens when a service receives more incoming requests than it can reasonably respond to. There are many reasons that service can get overloaded. A few examples are a sudden surge in traffic, a change in the service configuration, attacks by malign actors, and more. In the event of a service overload, the service starts to behave differently. It starts returning HTTP error codes, responds…

Leave a Comment

Promoting Learnings in Incidents

Incidents are used for the negative consequences of an action. The incident comes from an action that fails to result in the expected outcome. For instance, deploying a code to production to add a new feature to improve performance. It then takes down the whole service. This is an unexpected outcome. The incident learning is the part where we uncover underlying problems that lead to the incident.…

Leave a Comment

Oh hi there 👋 It’s nice to meet you.

Sign up to receive awesome content in your inbox, every month.

We don’t spam!