What Else Can Programmers Do Besides Writing Code?

I’m 32 years old, and I’ve been working as a front-end developer for nearly eight years.

Eight years is enough time for a baby to learn to speak, walk, and start school.

It’s also enough time for a programmer to go from writing “Hello, World!” to “mastering the React source code”—from idolizing framework creators to questioning what they actually know.

During a meeting one day, the product manager asked:

“Roughly how long will this requirement take?”

“Two days,” I said.

What I was really thinking was: two days to write the code, then another three days to debug it, fix bugs, and deal with all kinds of unexpected issues.

But I didn’t dare say that. I was afraid people would think I was “inefficient.”

That evening, I came home, lay on the sofa, and scrolled through my social feed.

I saw a college classmate posting pictures of his child. I saw a former colleague who had switched to sales showing off his commission. I saw a friend who had entered the industry alongside me sharing photos of the new online store he had opened.

Suddenly, I asked myself a question:

“If I couldn’t write code tomorrow, what else could I do to make a living?”

Once that thought appeared, I couldn’t suppress it anymore.

01. I Took Stock of Myself—and Started to Panic

I tried to make a list of my skills:

• I can write React and Vue applications, set up project scaffolding, and optimize performance.
• I can debug CSS and know how to center a box—although I still forget sometimes.
• I can use Git and follow a code review process.
• I can find answers to most problems on Stack Overflow.

That sounds like quite a lot, doesn’t it?

But then I thought a little deeper.

Could I handle an entire commercial project—from finding and negotiating with a client to delivering the work and collecting payment?

No.

Could I write a business plan and clearly calculate the costs and returns?

No.

Could I lead a team, communicate with people, and manage expectations?

Maybe—but not confidently.

Could I use any skill outside technology to earn even a single cent?

I couldn’t think of anything.

Then I realized something frightening:

In eight years, I had learned only one thing—how to write code.

No, to be more precise, I had learned only how to write code inside a company, according to requirements given to me by someone else.

I was trapped inside a transparent “coding cocoon.”

The walls of that cocoon were the technology stacks I knew so well. Its roof was the salary deposited into my bank account on time every month.

I had stayed inside it for so long that I had forgotten what the outside world looked like.

02. I Started Observing the People Around Me

I have a friend who works in sales.

He often tells me:

“There’s no barrier to entry in this industry. Anyone can do it.”

Once, I accompanied him to meet a client.

Within five minutes, he could tell what kind of person the client was—whether they were the decision-maker or merely gathering information, and whether they should be persuaded with data or approached through emotional connection.

I said:

“That’s an impressive skill.”

He replied:

“It’s nothing. Anyone can do it after being in the business long enough.”

At that moment, I suddenly understood:

What people call “having no barrier to entry” is often the highest barrier of all.

His insight into human nature, his control over the rhythm of a conversation, and his resilience in the face of rejection—these were things I simply didn’t have.

I had always hidden behind a screen, dealing with code governed by clear and predictable logic.

I have another friend who runs an online store.

He once asked me to make a few simple design changes to his shop. I finished them in half an hour.

He thought I was a genius.

“You programmers are incredible. I could study this for the rest of my life and still never learn it.”

I said, “It’s nothing,” but inside, I wondered:

Were the things I knew really more “impressive” than the things he knew?

He knew how to choose products, negotiate with suppliers, calculate the return on advertising spend, deal with negative reviews, and maintain a good relationship with the courier so that he would take extra care of his packages.

I knew none of those things.

We had simply invested our skill points in different trees.

03. I Tried Asking Myself: What Do I Actually Have?

That night, I lay in bed and forced myself to list the things I could do without writing code.

After thinking for a long time, I wrote down three.

Logical Thinking

Whenever I encounter a problem, my instinct is to break it down, identify the cause, and look for a solution.

This ability feels ordinary in my line of work, but I later realized that not everyone thinks this way.

The Persistence to Finish What I Start

Writing code rarely works perfectly on the first attempt.

Most of the time, there’s an error here and a bug there. You break down, pull yourself together, keep searching, find the problem, and fix it.

That ability to keep going in the face of frustration is also something I’ve accumulated over the years.

The Ability to Learn Quickly

Anyone who has survived the speed at which front-end frameworks evolve is probably a reasonably fast learner.

Whenever something new appears, we complain that we “can’t keep up anymore,” but we still open the documentation and start experimenting.

After writing down those three things, I paused.

These abilities didn’t seem to have anything directly to do with writing code.

04. I Started Asking My Friends How They Saw Me

I asked a friend who works in operations:

“What do you think my strengths are?”

She said:

“You’re incredibly reliable. If you say you can do something, you always get it done. That’s nothing like the contractors we hire—they make grand promises, but the final delivery is a complete mess.”

I asked another friend who was building a startup:

“What do you think programmers can do if they change careers?”

He thought for a moment and said:

“Honestly, people like you can do a lot—as long as you’re willing to step outside your comfort zone. You understand logic, products, and the internet. That gives you an advantage over people from purely traditional industries. Your weakness is that you’re too accustomed to working alone and don’t always know how to collaborate with others.”

Those words affected me deeply.

I suddenly realized that believing I “only knew how to write code” might have been the greatest misunderstanding I had about myself.

I didn’t “only know how to write code.”

I had simply placed myself exclusively in the role of someone who writes code.

Code was only my tool. It wasn’t who I was.

Using that tool had trained my logic, patience, and problem-solving abilities.

Those abilities weren’t tied to any particular framework or programming language.

They belonged to me.

I just hadn’t taken them seriously all these years.

05. I Started Rethinking the Idea of a Side Hustle

I used to believe that a side hustle meant “using my spare time to make money by writing code.”

Taking freelance projects, doing private contract work, or building mini-apps to sell—it was all essentially the same thing: selling code.

But now I’ve started wondering whether a side hustle could take a different form.

If I don’t sell code, what could I sell?

Could I sell the experience I’ve gained over the past several years?

For example, I could offer guidance to newcomers in the industry and help them avoid some of the mistakes I made.

Could I sell my ability to think logically?

Perhaps I could help small-business owners analyze their data and organize their processes—even if all it required was Excel.

Could I sell my sensitivity to tools?

Perhaps I could help people in traditional industries find the right software, teach them how to use it, and save them time and effort.

None of these things requires writing code.

And I might even be better at them than many other people—because I understand logic, efficiency, and how to bring clarity to complicated situations.

06. I Still Haven’t Figured Out the Road Ahead After 30

As I write this, it’s already dark outside.

I haven’t eaten dinner yet, but somehow, I don’t feel quite as anxious anymore.

I still don’t know exactly what my path after 30 should look like.

I still feel anxious and lost. I still lie awake late at night and ask myself:

“What do I actually know how to do?”

But at least I’ve started looking at the question from a different angle.

I’m not someone who “only knows how to write code.”

I simply haven’t learned how to see the parts of myself that exist beyond code.

The road ahead may be long.

But fortunately, 32 isn’t too old.

There’s still time.

I can take it one step at a time.