Dax's Blog

F2E, Full-Stack To Indie Hacker

Why I'm Sticking with Front-End Development

I. The Trigger for Rethinking

I worked as a Front-End Developer in a corporate setting for many years, but it wasn’t until I resigned that I truly found the opportunity to re-examine the question: “What is actually suitable for me going forward?” Many questions don’t have immediate answers; they require time and experience to settle.

In the first few months after leaving, I felt a distinct discomfort from the sudden loss of life’s momentum. This was accompanied by anxiety—anxiety about the pause in income, and anxiety about having idle time. So, out of habit, I began polishing my resume, grinding algorithms, and memorizing standardized interview trivia.

However, I ultimately chose not to continue down the path of job hunting.

Part of this decision stemmed from the internal conflict I felt during the interview prep. While a job provides stable income, the process felt like selling practically all my time as a commodity, where my technical skills were merely quality-control checklists used to filter me. It felt heavily objectifying.

But the primary reason was family. I need to take on the responsibility of childcare. In the internet industry, leaving early and returning late is the norm; balancing that schedule with taking care of a child is next to impossible.

II. Why Stick with Front-End?

Despite not seeking a corporate job, I decided to continue working in Front-End Development as a freelancer. This is based on two main reasons.

The first is a direct, pragmatic reason: within the context of the social division of labor, it makes the most sense to do what I am experienced in. As a profession, Front-End provides value just like many other service roles. It is neither lowly nor something to show off about. If it provides value, it exists; if there is a market, there is an industry scale. Furthermore, every industry is stratified. You don’t have to be in the top 1% to survive; you can find a niche and a position that suits you.

The second reason is a “cognitive sourcing” of what it means to be a programmer. I’ve been reading some books, and the one that impacted me most was “Hackers: Heroes of the Computer Revolution”.

We are born into an environment where we are conditioned to absorb information from our surroundings. We have formed a consensus on the stereotypes of programmers: the rigid personality, the high-intensity overtime, and the idea that this is a “young person’s game” with an expiration date at age 35.

But in reality, this is not the case. By using books to transcend time and look at the origins of programming—the development of the internet and computers, and the people behind these advancements—you see their cultural identity, their pursuits, their values, and their personalities. You discover that the reality differs vastly from the rigid stereotypes most people hold today.

It reminds me of the movie “The Truman Show”. When Truman rows his boat and pierces the sky, he realizes it is actually the backdrop of a studio set. He has to tear open that curtain to find real information and seek the truth.

You could say that most programmers, from their education to their employment, are molded as products of an industrial assembly line. But that is not the correct truth. The true history of computing is full of diverse individuals and heroism, encompassing their unique personalities and pursuits. Front-End is not just a solidified role in the division of labor; it is a technical product and a branch of technology. For personal development, becoming a Front-End developer to meet social needs is the starting point, not the end point. Only with a clearer cognition and a sense of identity can one walk steadier and further in this field.

III. The Challenge of Starting Over

The first challenge I faced was the technology itself. Although it is all “Front-End,” the tech stack in the open-source community is completely different from what is used inside companies. Leaving the corporate ecosystem meant almost relearning everything from scratch.

However, after a few weeks of exploration, I found that community technology is actually more flexible and mature. The possibility of becoming a “Super Individual” is greater now. In the past, developing and deploying a simple app required coordinating various links and people; now, it can be done very quickly.

The second challenge is the impact of AI. AI-generated content is everywhere now. My view is that, first and foremost, one must solidify the fundamentals. If you don’t understand the principles, you will be hollowed out and easily replaced. But if you understand the principles, AI becomes an efficiency booster—we cannot put the cart before the horse.

Furthermore, rather than worrying, “if you can’t beat them, join them.” I should use AI to strengthen my own capabilities.

IV. The Ultimate Question of Continuous Reflection

Inscribed on the Temple of Apollo at Delphi is a maxim: “Know Thyself.”

In this vast world, everyone’s life is vastly different. But as individuals, we face a choice: either drift with the current, or from the “boundless ocean, take only one ladle of water.” Making that choice—that trade-off—is what defines your own life.

Life is short. How do we spend it so it doesn’t feel wasted? How do we find meaning?

Perhaps continuously doing things that you find valuable and interesting is enough.