After a Year of Indie Hacking, What's My Biggest Takeaway?

One late night last winter, I was crouching in my rented apartment staring at error logs, my coffee long cold. The first paying user of Flash Warehouse had just signed up, and the next morning they told me the data didn't match—the purchase order and inventory were off by 50 units. I spent three hours debugging and finally found a missing transaction annotation causing concurrent write inconsistency. I slumped in my chair, thinking: What am I even doing? How can a developer who can't handle transactions think they can start a business?

TL;DR A year ago I quit my job to build a SaaS, thinking tech was everything. I later realized tech is just the foundation, business is the house, and personal growth is the decoration. You need all three, but in the right order. Today I share my real struggles on the path of a tech person's cultivation.

Why Did I Only Focus on Tech at First?

Because tech is a comfort zone, and business is a fear zone.

I studied computer science in college, wrote Java, Vue, Three.js—I had a broad stack. But after starting my business, I found that even the best code is useless if nobody uses it.

When I started Flash Warehouse, I spent three months polishing the tech architecture: multi-tenant SaaS, RSA encryption, AI assistant integration. I thought if the tech was awesome, users would flock to me. Result? After launch, only 5 registered users—3 were friends, 2 clicked by accident.

I was forced to learn product, operations, SEO. Honestly, that period was more painful than coding. Coding has right answers; business doesn't. You never know which feature users will pay for or which channel brings traffic. The uncertainty made me want to quit.

But after stepping in that pit, you understand: Tech is just a tool, business is the goal. It's like an RPG—you can't just level one skill tree; you need all-round development to beat the game.^[1]

How Does Business Thinking Drive Tech Growth?

When users start paying, your code is no longer just code.

In the third month, I got my first paying customer—a small foreign trade boss. He paid and then threw a bunch of requirements: connect Taobao API, support multi-language, add mobile scanning.

My first reaction: I've never done any of these. The Taobao API docs were overwhelming, the i18n solution had to be built from scratch, and mobile was a new frontier. But I took the money, so I gritted my teeth and did it.

Result? To connect Taobao API, I learned OAuth 2.0 and async task queues; for multi-language, I refactored the whole frontend i18n; for mobile, I learned uni-app and scanning SDKs. Three months later, these became my tech moat.

I realized that business needs are the best learning drivers. I used to learn new tech for trendiness; now I learn to solve problems. The motivation is completely different. GitHub's 2024 report says AI-assisted coding tools boost efficiency by 30-55%^[2], but my own experience is that real efficiency comes from real user needs.

What Does Personal Growth Really Mean?

Growth isn't about learning more things; it's about learning to face uncertainty.

I used to be a perfectionist in college: elegant code, advanced architecture, agonizing over variable names. But after a year of entrepreneurship, I changed.

One night a customer called saying the system crashed. I got up, checked logs, found MySQL connection pool exhausted. I temporarily changed configs and restarted to restore service, then investigated the root cause the next day. Before, I would have written a perfect plan first. That time I learned: Stop the bleeding first, treat the disease later.

This mindset shift also affected my fitness habit. I used to follow a strict workout plan and get anxious if I missed a set. Now I adjust based on my daily state—go heavy if feeling good, do cardio if tired. The principle of progressive overload in strength training is like tech growth—you can't improve every day, but looking back after six months, the change is remarkable.

Speaking of philosophy, I love the Stoic saying: Control what you can control, accept what you can't. In entrepreneurship, so many things are uncontrollable: market changes, competitors, user preferences. But code quality, product experience, service attitude—these I can control. Focus on what you can control, and anxiety fades.

How Are Tech, Business, and Personal Growth Related?

They're not three separate stages; they're three strands of a rope twisted together.

I drew a diagram: tech is the base, business is the superstructure, personal growth is the cement connecting them. Without tech, business is a castle in the air; without business, tech is self-indulgence; without personal growth, both collapse.

Stack Overflow's 2024 developer survey says full-stack is the most popular role^[3]. But I think true 'full-stack' means more than frontend and backend—it's about switching between tech, business, and life.

For example, Flash Warehouse's architecture now has three layers: infrastructure (Spring Boot + MySQL), business logic (multi-tenant, permissions), user interaction (PC, mobile, AI assistant). This layering not only makes code maintainable but also clarifies my thinking—when a problem arises, first locate which layer it belongs to: tech issues go to the bottom, business issues to the middle, personal issues to my own state.

After a Year, What's My Biggest Takeaway?

A tech person's cultivation is not about leveling up from noob to pro, but about transforming from a 'code writer' to a 'problem solver.'

This year I learned:

Great code is worthless if nobody uses it.

Business needs are the best teachers, better than any tutorial.

Growth isn't linear; it's spiral—you think you're circling, but you've already risen a level.

Control what you can, accept what you can't, and focus on building the product.

Looking back at that transaction bug, I'm actually grateful. It taught me that tech is just the starting point, not the destination. The real cultivation has only just begun.

References

Stack Overflow 2024 Developer Survey — Developer roles and tech stack trends
GitHub 2024 Octoverse Report — Data on AI-assisted coding efficiency gains
Stack Overflow 2024 Developer Survey — Full-stack developer is the most popular role