<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Shahanaz </title>
    <description>The latest articles on DEV Community by Shahanaz  (@shahanaz).</description>
    <link>https://dev.to/shahanaz</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2785031%2F39a8f2a7-f214-4e7b-8051-f79e20ed5df0.jpg</url>
      <title>DEV Community: Shahanaz </title>
      <link>https://dev.to/shahanaz</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/shahanaz"/>
    <language>en</language>
    <item>
      <title>I Thought Building Websites Was About Coding. I Was Wrong.</title>
      <dc:creator>Shahanaz </dc:creator>
      <pubDate>Fri, 20 Nov 2026 07:57:46 +0000</pubDate>
      <link>https://dev.to/shahanaz/i-thought-building-websites-was-about-coding-i-was-wrong-3a7n</link>
      <guid>https://dev.to/shahanaz/i-thought-building-websites-was-about-coding-i-was-wrong-3a7n</guid>
      <description>&lt;h1&gt;
  
  
  I Thought Building Websites Was About Coding. I Was Wrong.
&lt;/h1&gt;

&lt;p&gt;For almost two years, I believed becoming a better developer meant writing better code.&lt;/p&gt;

&lt;p&gt;I chased new frameworks, watched tutorials, built projects, deployed applications, fixed bugs, and learned how frontend, backend, and databases fit together.&lt;/p&gt;

&lt;p&gt;Every finished project felt like proof that I had become a better engineer.&lt;/p&gt;

&lt;p&gt;Or so I thought.&lt;/p&gt;

&lt;p&gt;Then something unexpected happened.&lt;/p&gt;

&lt;p&gt;I opened someone else's portfolio.&lt;/p&gt;

&lt;p&gt;It wasn't packed with fancy animations or cutting-edge effects. In fact, it was surprisingly simple.&lt;/p&gt;

&lt;p&gt;Yet after only a few minutes, I closed the tab remembering one thing:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The person behind it.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Not their tech stack.&lt;/p&gt;

&lt;p&gt;Not their projects.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The person.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;That moment made me question something I'd never questioned before.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;What if a website isn't just software?&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  The misunderstanding
&lt;/h2&gt;

&lt;p&gt;As developers, we're trained to think in terms of technology.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;React&lt;/li&gt;
&lt;li&gt;Node.js&lt;/li&gt;
&lt;li&gt;MongoDB&lt;/li&gt;
&lt;li&gt;REST APIs&lt;/li&gt;
&lt;li&gt;Authentication&lt;/li&gt;
&lt;li&gt;Deployment&lt;/li&gt;
&lt;li&gt;Performance&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;These things matter.&lt;/p&gt;

&lt;p&gt;Without them, the product doesn't work.&lt;/p&gt;

&lt;p&gt;So naturally, I assumed building websites was mostly about writing code.&lt;/p&gt;

&lt;p&gt;Looking back, I wasn't wrong.&lt;/p&gt;

&lt;p&gt;I was just seeing only half of the picture.&lt;/p&gt;




&lt;h2&gt;
  
  
  The other half
&lt;/h2&gt;

&lt;p&gt;When someone visits your website, they don't experience React.&lt;/p&gt;

&lt;p&gt;They experience &lt;strong&gt;clarity&lt;/strong&gt; or &lt;strong&gt;confusion&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;They don't notice your database schema.&lt;/p&gt;

&lt;p&gt;They notice whether they trust your product.&lt;/p&gt;

&lt;p&gt;They don't care how elegant your API is.&lt;/p&gt;

&lt;p&gt;They care whether accomplishing a task feels effortless.&lt;/p&gt;

&lt;p&gt;That's when my perspective changed.&lt;/p&gt;

&lt;p&gt;A website isn't simply a collection of components.&lt;/p&gt;

&lt;p&gt;It's a conversation.&lt;/p&gt;

&lt;p&gt;Every colour communicates something.&lt;/p&gt;

&lt;p&gt;Every sentence communicates something.&lt;/p&gt;

&lt;p&gt;Every interaction communicates something.&lt;/p&gt;

&lt;p&gt;Every delay communicates something.&lt;/p&gt;

&lt;p&gt;Even empty space communicates something.&lt;/p&gt;

&lt;p&gt;Whether we realise it or not, we're constantly shaping how someone feels while using what we build.&lt;/p&gt;




&lt;h2&gt;
  
  
  Then I realised I was making the same mistake with myself
&lt;/h2&gt;

&lt;p&gt;I spent months improving my portfolio.&lt;/p&gt;

&lt;p&gt;I redesigned it.&lt;/p&gt;

&lt;p&gt;Improved the UI.&lt;/p&gt;

&lt;p&gt;Updated my résumé.&lt;/p&gt;

&lt;p&gt;Refined my LinkedIn profile.&lt;/p&gt;

&lt;p&gt;Polished every project description.&lt;/p&gt;

&lt;p&gt;Everything looked more professional.&lt;/p&gt;

&lt;p&gt;Yet something still felt missing.&lt;/p&gt;

&lt;p&gt;Eventually, I realised why.&lt;/p&gt;

&lt;p&gt;My portfolio showed &lt;strong&gt;what I had built.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;It never showed &lt;strong&gt;who I am.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;It listed technologies.&lt;/p&gt;

&lt;p&gt;It didn't communicate how I think.&lt;/p&gt;

&lt;p&gt;It described features.&lt;/p&gt;

&lt;p&gt;It didn't explain why those problems mattered to me.&lt;/p&gt;

&lt;p&gt;It looked like a developer's portfolio.&lt;/p&gt;

&lt;p&gt;It didn't feel like &lt;strong&gt;my&lt;/strong&gt; portfolio.&lt;/p&gt;

&lt;p&gt;If someone removed my name, it could have belonged to hundreds of other MERN developers.&lt;/p&gt;

&lt;p&gt;That was difficult to accept.&lt;/p&gt;

&lt;p&gt;But it was also liberating.&lt;/p&gt;

&lt;p&gt;Because the problem wasn't my technical skills.&lt;/p&gt;

&lt;p&gt;The problem was my story.&lt;/p&gt;




&lt;h2&gt;
  
  
  Coding creates software. Experience creates meaning.
&lt;/h2&gt;

&lt;p&gt;Today, I think about web development differently.&lt;/p&gt;

&lt;p&gt;Backend engineering is where logic, architecture, security, and business rules come together.&lt;/p&gt;

&lt;p&gt;Frontend engineering is where people interact with that logic.&lt;/p&gt;

&lt;p&gt;But the product itself is something bigger than either.&lt;/p&gt;

&lt;p&gt;It's the experience created when engineering, design, psychology, communication, branding, and trust work together.&lt;/p&gt;

&lt;p&gt;Users rarely remember your authentication flow.&lt;/p&gt;

&lt;p&gt;They remember how confident they felt using your product.&lt;/p&gt;

&lt;p&gt;Recruiters rarely remember every bullet point on your résumé.&lt;/p&gt;

&lt;p&gt;They remember whether they understood who you are.&lt;/p&gt;




&lt;h2&gt;
  
  
  What I'm learning now
&lt;/h2&gt;

&lt;p&gt;I'm still a full-stack developer.&lt;/p&gt;

&lt;p&gt;I still enjoy solving backend problems.&lt;/p&gt;

&lt;p&gt;I still enjoy designing frontend interfaces.&lt;/p&gt;

&lt;p&gt;But I'm no longer trying to build websites.&lt;/p&gt;

&lt;p&gt;I'm trying to build experiences.&lt;/p&gt;

&lt;p&gt;Not experiences filled with unnecessary animations.&lt;/p&gt;

&lt;p&gt;Experiences that communicate trust.&lt;/p&gt;

&lt;p&gt;Experiences that reduce confusion.&lt;/p&gt;

&lt;p&gt;Experiences that quietly solve real problems.&lt;/p&gt;

&lt;p&gt;Most importantly, experiences that reflect the person behind the code.&lt;/p&gt;

&lt;p&gt;Maybe that's what personal branding really is.&lt;/p&gt;

&lt;p&gt;Not pretending to be someone impressive.&lt;/p&gt;

&lt;p&gt;But making sure the experience people have matches who you actually are.&lt;/p&gt;

&lt;p&gt;I think that's the kind of developer I want to become.&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;What changed your perspective on software development?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I'd genuinely love to hear the moment that shifted how you think about building products.&lt;/p&gt;

</description>
      <category>career</category>
      <category>softwaredevelopment</category>
      <category>softwareengineering</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
