I used to write code. Now I write about marketing.

If you had told the version of me writing his first production code that he would one day spend his week thinking about distribution, hooks, and how people discover things on the internet, he would not have believed you.

I started as a developer. Now I mostly think about marketing.

That shift did not happen in one jump. It happened in four steps, and each one quietly changed what I paid attention to.

Step one: code meets customers

My first job was as a junior developer at ServerAvatar.

The biggest lesson was not technical. It was that code is only half the product. The other half is the person on the other side of the screen, trying to get something done and not caring at all how elegant your solution is.

When your work touches real customers early, you learn fast that “it works” and “people use it” are two very different sentences.

Step two: what users ignore

As a software developer at Perrian, I shipped production software and learned the uncomfortable part: users ignore a lot.

Features you were proud of go untouched. Settings you thought were essential never get opened. Meanwhile one small thing you built in an afternoon becomes the reason people stay.

That was the first time I started wondering about the space between building something and people actually finding value in it.

Step three: output vs outcomes

Moving into product management at Wizcoder forced a bigger change in how I thought.

As a developer, success looked like output. Tickets closed, features shipped, bugs fixed. As a PM, success had to be outcomes. Did the thing we shipped change anything for the people using it?

That question is uncomfortable because output is easy to count and outcomes are not. But once you start asking it, you cannot stop. And it pulls you, almost automatically, toward marketing questions:

• Who is this for?
• How will they hear about it?
• Why would they care right now?

Those are product questions. They are also marketing questions. The line between the two is much thinner than most job titles suggest.

Step four: the founder seat

Then I started linkutm.

As a founder, nobody hands you the distribution. There is no marketing team waiting for the launch. If you build something and nobody hears about it, that is your problem now.

So I became the marketer. Not because I planned to, but because the job required it. And somewhere along the way, I realized I enjoyed it more than I expected.

What carried over

People sometimes assume a developer moving into marketing is starting from zero. I do not think that is true. A few things carried over directly:

1. Systems thinking. Marketing is full of systems: funnels, loops, habits, feedback. Developers are trained to see them.
2. Debugging. When a campaign fails, the question is the same as when code fails. What changed, and where exactly did it break?
3. Respect for the boring parts. Good engineering is mostly unglamorous discipline. So is good marketing.

What I had to unlearn

Some things did not carry over at all.

The biggest one: believing the best product wins on its own. It does not. The best product people know about wins. A developer instinct says “just make it better.” A founder has to say “make it better and make sure people hear about it.”

The second one: hiding behind the work. Code can speak for itself in a pull request. A founder has to speak for the work in public, which feels strange at first. I am still getting used to it.

Where this leaves me

I still think like a builder. I just point that thinking at a different problem now.

Instead of asking “how do I build this?”, I ask “how do people find this, trust it, and come back?” Same curiosity. Different layer of the stack.

---

Post eight of writing in public. If you have made a similar jump from building to selling, I would love to compare notes: email me.