Urgent.News

What's breaking now, across thousands of outlets.

Tech

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.…

I once thought that crafting websites centered solely around writing proficient code. I spent countless hours honing my skills, experimenting with new frameworks, and constructing projects. Every finished product seemed like tangible evidence of my growth as a developer. However, a surprising revelation altered my perspective.

Upon viewing someone else's portfolio, I was struck by its simplicity. Far from boasting flashy animations or innovative effects, the focus was on the person behind it. This experience made me question a fundamental belief – was a website merely a piece of software? As developers, we're accustomed to thinking in terms of technology, such as React, Node.js, MongoDB, REST APIs, authentication, deployment, and performance.

Clearly, these elements are crucial; without them, the product fails to function. Consequently, I assumed building websites primarily involved writing code. Yet, I was only seeing a fraction of the bigger picture.

When a visitor lands on a website, their experience isn't dictated by React or the intricacies of the database schema. Instead, they encounter clarity or confusion, trust or skepticism, and most importantly, whether the task feels effortless. Thus, my viewpoint underwent a significant shift. A website isn't just a collection of components; it's a conversation.

Every color, sentence, interaction, delay, and even empty space communicates something. Whether consciously or not, we're constantly shaping the user's feelings during their interaction with what we create.

A personal revelation came to light as I refined my own portfolio. Despite redesigning it, improving its UI, updating my résumé, polishing my LinkedIn profile, and refining every project description, something still felt amiss. Upon reflection, I realized why. My portfolio showcased what I had built, yet it never revealed who I am.

It listed technologies, described features, and listed bullet points, but it failed to communicate my thought process, explain why those problems resonated with me, or truly embody my unique identity. It resembled a standard developer's portfolio, devoid of authenticity.

Accepting this truth proved challenging, yet liberating. The issue wasn't my technical skills; it was my storytelling. Coding builds software. Experience shapes meaning. Today, I contemplate web development differently. Backend engineering integrates logic, architecture, security, and business rules, while frontend engineering focuses on how users engage with that logic.

However, the product transcends either – it's the experience forged when engineering, design, psychology, communication, branding, and trust converge. Users rarely recall the authentication flow, but they remember feeling confident while using the product. Recruiters seldom focus on the bullet points on your résumé; they remember if they grasped your true self.

Reflecting on this new understanding, I continue to be a full-stack developer. I appreciate solving backend problems and crafting frontend interfaces. Nevertheless, I'm no longer solely focused on building websites; I aspire to construct experiences.

These experiences encompass not just the technical aspects but also trust, clarity, reduced confusion, seamless problem-solving, and most crucially, an authentic reflection of the person behind the code. This realization has led me to contemplate what personal branding truly entails. It's not about pretending to be someone impressive.

Instead, it's about ensuring the experience users have aligns with who we genuinely are. This perspective has fundamentally changed how I approach development, aiming to become a developer who not only builds products but also cultivates meaningful experiences.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

More from Friday 20 November →