2024 Retrospective of a 9-Year Developer

Hi, I'm Lovefield.

This article is a retrospective of 2024—a year full of events and significant personal growth. Not only did I reach my ninth year as a developer, but I also took on the role of a team leader, which brought about major changes. I started managing team members and their tasks while focusing on effective communication within the team. It was no longer just about my own development; I now had to lead the team effectively.

The Positive Impact of 1-on-1 Meetings

The first initiative I introduced as a team leader was 1-on-1 meetings. As someone who prefers purpose-driven organizations, I saw this as a way to address individual goals and desires while aligning them with the company’s objectives. The results were better than expected. I witnessed team members recognizing and working toward the company’s goals while striving to achieve their personal aspirations. Additionally, I was able to better convey team members' concerns and expectations to the company.

A Team that Operates as One

This is the direction I envision for the team. A development organization should not have critical gaps if one member is absent. My goal is to ensure everyone follows the same conventions and writes consistent code. This way, as long as someone has domain knowledge, they can quickly understand and modify the code. With the premise that teammates can step in for one another, everyone readily accepted this direction. I personally don’t favor being the only high performer because it’s exhausting. Instead, I believe everyone should excel together so that everyone can work more comfortably. Guided by this perspective, I’ve been leading the team and achieving greater growth.

Nuxt.js vs Next.js

Choosing the right tech stack was also a significant concern. At my current company, there was always a dilemma about which technology to adopt. I had to compare the needs of the company with the pros and cons of various technologies to select the most suitable one. The consistent choice was Nuxt.js. The reason was straightforward. Next.js structures varied greatly between companies and teams, and the modules in use required developers to have different levels of expertise. This lack of uniformity made it challenging to maintain consistency, even within the same organization. Since we had junior-level team members who required training, Nuxt.js, with its predefined structure, became the preferred choice. Additionally, its developer-friendly nature reduced the time needed to onboard new team members.

The End of a Side Project

After six long years, I decided to end a side project and disband the team. Although it was a sad decision, the lack of progress during those six years was largely my responsibility. I trusted my team members, didn’t set deadlines, and failed to provide a clear roadmap, which led to delays spanning years. As a side project, it was often overshadowed by the team members’ main jobs. In the end, I decided to discontinue the project and dissolve the team. This experience prompted me to deeply reflect on how leaders should communicate direction and objectives.

Starting a New Side Project

My ambition to create a service didn’t fade easily. I began to notice other domains and saw new opportunities and needs. This renewed my desire to create a service. Fortunately, a former colleague showed interest in my project. After discussing it during a gathering, the colleague joined my side project, forming a new team. The current side project is progressing rapidly. Unlike before, I provided a roadmap and set quarterly goals, sharing them with the team. The feedback has been positive. Although we don’t have tangible results yet, I believe we are progressing faster than before.

Lessons Learned and Future Plans

2024 has been a year of immense learning. Taking on the role of a team leader allowed me to deeply understand team communication and project management. Moving forward, I will continue striving to become a better team leader. My goal remains to ensure that everyone grows together. This concludes my retrospective as a nine-year developer. Thank you for reading.