DEV Community

Shahanaz
Shahanaz

Posted on

I Thought Building Websites Was About Coding. I Was Wrong.

I Thought Building Websites Was About Coding. I Was Wrong.

For almost two years, I believed becoming a better developer meant writing better code.

I chased new frameworks, watched tutorials, built projects, deployed applications, fixed bugs, and learned how frontend, backend, and databases fit together.

Every finished project felt like proof that I had become a better engineer.

Or so I thought.

Then something unexpected happened.

I opened someone else's portfolio.

It wasn't packed with fancy animations or cutting-edge effects. In fact, it was surprisingly simple.

Yet after only a few minutes, I closed the tab remembering one thing:

The person behind it.

Not their tech stack.

Not their projects.

The person.

That moment made me question something I'd never questioned before.

What if a website isn't just software?


The misunderstanding

As developers, we're trained to think in terms of technology.

  • React
  • Node.js
  • MongoDB
  • REST APIs
  • Authentication
  • Deployment
  • Performance

These things matter.

Without them, the product doesn't work.

So naturally, I assumed building websites was mostly about writing code.

Looking back, I wasn't wrong.

I was just seeing only half of the picture.


The other half

When someone visits your website, they don't experience React.

They experience clarity or confusion.

They don't notice your database schema.

They notice whether they trust your product.

They don't care how elegant your API is.

They care whether accomplishing a task feels effortless.

That's when my perspective changed.

A website isn't simply a collection of components.

It's a conversation.

Every colour communicates something.

Every sentence communicates something.

Every interaction communicates something.

Every delay communicates something.

Even empty space communicates something.

Whether we realise it or not, we're constantly shaping how someone feels while using what we build.


Then I realised I was making the same mistake with myself

I spent months improving my portfolio.

I redesigned it.

Improved the UI.

Updated my résumé.

Refined my LinkedIn profile.

Polished every project description.

Everything looked more professional.

Yet something still felt missing.

Eventually, I realised why.

My portfolio showed what I had built.

It never showed who I am.

It listed technologies.

It didn't communicate how I think.

It described features.

It didn't explain why those problems mattered to me.

It looked like a developer's portfolio.

It didn't feel like my portfolio.

If someone removed my name, it could have belonged to hundreds of other MERN developers.

That was difficult to accept.

But it was also liberating.

Because the problem wasn't my technical skills.

The problem was my story.


Coding creates software. Experience creates meaning.

Today, I think about web development differently.

Backend engineering is where logic, architecture, security, and business rules come together.

Frontend engineering is where people interact with that logic.

But the product itself is something bigger than either.

It's the experience created when engineering, design, psychology, communication, branding, and trust work together.

Users rarely remember your authentication flow.

They remember how confident they felt using your product.

Recruiters rarely remember every bullet point on your résumé.

They remember whether they understood who you are.


What I'm learning now

I'm still a full-stack developer.

I still enjoy solving backend problems.

I still enjoy designing frontend interfaces.

But I'm no longer trying to build websites.

I'm trying to build experiences.

Not experiences filled with unnecessary animations.

Experiences that communicate trust.

Experiences that reduce confusion.

Experiences that quietly solve real problems.

Most importantly, experiences that reflect the person behind the code.

Maybe that's what personal branding really is.

Not pretending to be someone impressive.

But making sure the experience people have matches who you actually are.

I think that's the kind of developer I want to become.


What changed your perspective on software development?

I'd genuinely love to hear the moment that shifted how you think about building products.

Top comments (0)