Career

The senior frontend map did not get a new section called “AI.” The tools did. The roadmaps did. Job posts did. None of that changed what senior means: you make decisions the team will live with, and you own the result. What changed is how cheap it became to produce something that looks like that work. A first draft used to cost enough that it carried some thought. Now it does not. Fluent, compiling, plausible code is the default output of a short prompt. The scarce work moved up: deciding whether that draft should exist, whether it is working-but-wrong, and whether this was a place generation should have been invited at all. ...

Partner companies ask me to help hire their frontend developers. Not “sit in on the final call.” The work starts in a room with their CTO, someone from HR, and whoever currently leads the development team. I listen to what they think they need. Then I tell them who they can actually use, read the incoming resumes, choose who is worth an interview, and run the loop. I follow the same path for my own team. The difference is who lives with the result. When I hire badly for myself, I absorb it — I mentor the person, or I carry the gap in the sprint. When I hire badly for a partner, they keep the person and I keep the reputation. ...

Cross-team trust is one of the strongest assets a senior developer can build. People tell you what is not working before it becomes an escalation. Designers invite you into early conversations. Product asks whether an idea is feasible. Support sends you the user complaint that explains a confusing metric. You see the product beyond the boundary of your team’s backlog. Then the strength turns. Another team believes you promised a fix. Your lead learns about new work after you have started it. Your teammates feel that your review comments carry an unofficial veto. You still think you are helping, but the organization has begun treating you as the owner. ...

On a small development team, one senior developer often becomes the person everyone else knows. People in product, design, support, and adjacent engineering teams message them directly. They listen well. They notice the rough edge that never became a ticket. They understand why a technically correct interaction still feels wrong to the person using it. When another team is frustrated, they do not reply with a Jira link and disappear. ...

In The Zoom-Out, I wrote about the moment a senior developer realizes they don’t know what they don’t know — Corepack, Yarn, Orval, the whole peripheral toolchain that matured while we were busy shipping. That post was about naming the feeling and regaining perspective. Plenty of readers wrote back with the natural next question: “Okay, I get it — the map is huge and I can’t know everything. But how do I actually find the important stuff before I’ve been doing it wrong for five years?” ...

It happened to me this morning. After 15 years in the trenches—building frontend architectures, dipping into the backend, leading teams, and surviving countless framework wars—I hit a wall. Not a technical wall, but a conceptual one. I realized I didn’t know what Corepack was. I’ve never actually used Yarn. I’ve heard of modern test runners like Playwright and code‑generation tools like Orval, but I’ve never managed to actually run one in a production pipeline. ...

You have a startup idea, and you have the skills to build it. As a senior developer, you’ve likely spent years mastering the art of turning requirements into robust, scalable systems. But when you decide to build your own company, you realize that the code is the easy part. The hard part is everything around the code: validation, prioritization, distribution, operations, and leadership. This post is a deep dive into the “Execution Gap.” It’s designed for the developer who can build anything but doesn’t know how to make it a reality in the market. We’re going to move past the clichés and look at the gritty details of startup execution, including the legal and management hurdles that often trip up technical founders. ...

Mentorship is a cornerstone of professional growth and development, particularly in the fast-paced and ever-evolving tech industry. Whether you’re a seasoned professional or just starting your career, engaging in a mentor-mentee relationship can provide invaluable insights, support, and opportunities for both personal and professional advancement. This blog post explores the benefits of mentorship in tech and offers practical guidelines for both mentors and mentees to maximize their relationships. The Importance of Mentorship in Tech Accelerated Learning and Skill Development One of the most significant benefits of mentorship is the accelerated learning curve it provides. Mentors can share their knowledge, experience, and insights, helping mentees navigate complex technical concepts and industry trends more quickly than they might on their own. This hands-on guidance can be particularly valuable in the tech industry, where new technologies and methodologies emerge rapidly. ...

Career dissatisfaction among developers is a common issue that can arise from various factors, including stagnation, lack of recognition, or misalignment with personal goals. Understanding the root causes and taking proactive steps to address them can help navigate these challenges effectively. This comprehensive guide will explore what developers should do for personal development, what they should expect from their employers, and how to foster a satisfying career. Identifying the Problem Signs of career dissatisfaction can include a lack of motivation, decreased productivity, and a sense of disengagement from work. If you find yourself questioning your career choices, it’s essential to reflect on your feelings and identify whether your dissatisfaction stems from personal issues, workplace environment, or a combination of both. Differentiating between these factors can help you take the appropriate steps toward resolution. ...

Launching a tech startup is an exhilarating journey, filled with moments of inspiration, innovation, and challenge. In 2024, the landscape of entrepreneurship is as dynamic and promising as ever, offering vast opportunities for those willing to dive in and create something remarkable. This comprehensive guide aims to provide aspiring tech entrepreneurs with a roadmap from ideation to scaling their startup. We’ll cover essential steps such as ideation, market research, MVP development, securing funding, and scaling your business. ...

In the modern workplace, developers often find themselves at the intersection of technology and business. While the technical prowess required to build and maintain software systems is crucial, the ability to communicate effectively with non-technical stakeholders is equally important. This blog post aims to provide developers with tips and strategies to bridge the communication gap between technical and non-technical teams, ensuring smoother collaborations and more successful projects. Understanding the Importance of Effective Communication Effective communication is the backbone of any successful project. When developers can clearly convey their ideas, challenges, and progress to non-technical stakeholders, it fosters a collaborative environment where everyone is aligned towards common goals. Here are some key reasons why effective communication is vital: ...

In the tech world, it’s not uncommon to hear stories of talented developers struggling to land a job, despite their evident skills and passion. Whether you’re a junior developer fresh out of a coding bootcamp or a senior developer with years of experience, the job market can be daunting. Let’s delve into some reasons why good developers sometimes can’t find jobs and explore strategies and tools to help them secure their dream roles. ...

The senior frontend map is still the floor. You do not get to stop being able to do the work. What changes is what a good week looks like, and which skills you now practice on purpose. A senior IC owns outcomes they can still mostly touch. A frontend team leader owns outcomes that only happen if other people succeed. That sounds obvious until you are the strongest engineer in the room and the fastest path to “done” is still you. Then the job quietly turns back into an IC role with extra meetings. ...

As an experienced Angular developer, you might be considering expanding your skill set by learning Java. This transition can be both challenging and rewarding, offering you a broader perspective on software development. In this blog post, we’ll explore how your Angular background can aid your journey into Java, and provide you with a detailed roadmap to get started. Leveraging Your Angular Experience Your background in Angular provides a solid foundation for learning Java. Here’s how your existing skills will help: ...

The senior frontend map is the baseline. You still need that list. This post is the rest of the slice: the names you will meet on the other side of the contract, and what changes when you own both sides of a bug at 2 a.m. I am a frontend-shaped senior who has crossed that line more than once. Years ago that looked like leaving a Laravel API and an AngularJS client for Spring Boot and Angular. The useful lesson was not “learn Java.” It was how much of the job lives in the seam. ...