<?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: lui were</title>
    <description>The latest articles on DEV Community by lui were (@lui_were).</description>
    <link>https://dev.to/lui_were</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3876890%2Fbdcf1c3d-39cc-489b-b8c2-fa28ecb050a4.png</url>
      <title>DEV Community: lui were</title>
      <link>https://dev.to/lui_were</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/lui_were"/>
    <language>en</language>
    <item>
      <title>WHAT I'M LEARNING BUILDING MY FIRST REAL PROJECT</title>
      <dc:creator>lui were</dc:creator>
      <pubDate>Mon, 04 May 2026 11:09:58 +0000</pubDate>
      <link>https://dev.to/lui_were/what-im-learning-building-my-first-real-project-31el</link>
      <guid>https://dev.to/lui_were/what-im-learning-building-my-first-real-project-31el</guid>
      <description>&lt;p&gt;&lt;strong&gt;What I Learned Building My First Real Project&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;There’s a big difference between following tutorials and actually building something on your own. Tutorials feel smooth—you follow steps, things work, and you move on. But the moment you start a real project from scratch, everything changes. Suddenly, you’re making decisions, facing errors you’ve never seen before, and realizing how much you &lt;em&gt;don’t&lt;/em&gt; know.&lt;/p&gt;

&lt;p&gt;This is what I learned building my first real project.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The Idea&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I didn’t start with something revolutionary. I picked a simple, practical idea: build something that solves a small problem or demonstrates a concept I had been learning.&lt;/p&gt;

&lt;p&gt;The goal wasn’t to impress anyone—it was to &lt;strong&gt;finish something real&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;That decision alone made a huge difference. Instead of jumping between ideas, I committed to one and pushed it until it worked.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The Problems I Faced&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The biggest surprise wasn’t coding—it was everything &lt;em&gt;around&lt;/em&gt; coding.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. Not Knowing Where to Start&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;At first, I had the idea but no structure.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;What files do I create?&lt;/li&gt;
&lt;li&gt;How do I organize the logic?&lt;/li&gt;
&lt;li&gt;What comes first?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I realized that building a project is less about writing code and more about &lt;strong&gt;breaking a problem into smaller parts&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Debugging Took Longer Than Writing Code&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I would write 10 lines of code and spend an hour fixing one bug.&lt;br&gt;
Sometimes the issue was:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A small typo&lt;/li&gt;
&lt;li&gt;A wrong assumption&lt;/li&gt;
&lt;li&gt;Misunderstanding how something works&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This taught me that debugging is not a side skill—it’s a &lt;strong&gt;core skill&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Tutorials Didn’t Prepare Me Enough&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;In tutorials, everything is structured. In real projects:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;There’s no step-by-step guide&lt;/li&gt;
&lt;li&gt;Errors don’t come with explanations&lt;/li&gt;
&lt;li&gt;You have to search, test, and think&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I had to learn how to &lt;strong&gt;figure things out independently&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. Overcomplicating Simple Things&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I often tried to make things “perfect”:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Writing complex logic for simple tasks&lt;/li&gt;
&lt;li&gt;Trying to optimize too early&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;In reality, simple solutions worked better.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The Mistakes I Made&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;This is where most of the learning happened.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. Waiting Too Long to Start&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I spent too much time “preparing” instead of building.&lt;/p&gt;

&lt;p&gt;Lesson: You learn faster by doing, not planning endlessly.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Trying to Understand Everything First&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I thought I needed to fully understand every concept before using it.&lt;/p&gt;

&lt;p&gt;Lesson: Use things first, understand them deeper over time.&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;3. Ignoring Errors Instead of Understanding Them&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Sometimes I just “fixed” errors without knowing why they happened.&lt;/p&gt;

&lt;p&gt;Lesson: Every error is a learning opportunity—don’t waste it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. Comparing My Work to Others&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I felt like my project wasn’t “good enough.”&lt;/p&gt;

&lt;p&gt;Lesson: Progress matters more than perfection.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I’d Do Differently
&lt;/h2&gt;

&lt;p&gt;If I were to start again, I’d change my approach:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Start smaller and build gradually&lt;/li&gt;
&lt;li&gt;Focus on finishing rather than perfecting&lt;/li&gt;
&lt;li&gt;Spend more time understanding errors&lt;/li&gt;
&lt;li&gt;Plan just enough, then start coding&lt;/li&gt;
&lt;li&gt;Track progress instead of chasing perfection&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Final Thoughts
&lt;/h2&gt;

&lt;p&gt;Building my first real project isn’t clean or easy—but that’s exactly why it matters.&lt;/p&gt;

&lt;p&gt;It has forced me to:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Think like a developer&lt;/li&gt;
&lt;li&gt;Solve real problems&lt;/li&gt;
&lt;li&gt;Deal with uncertainty&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Start small. Start messy. Just start.&lt;/p&gt;

</description>
      <category>programming</category>
      <category>ai</category>
      <category>webdev</category>
      <category>productivity</category>
    </item>
    <item>
      <title>The New Age of Developers: Building the Future One Line at a Time</title>
      <dc:creator>lui were</dc:creator>
      <pubDate>Mon, 20 Apr 2026 07:05:17 +0000</pubDate>
      <link>https://dev.to/lui_were/the-new-age-of-developers-building-the-future-one-line-at-a-time-4hof</link>
      <guid>https://dev.to/lui_were/the-new-age-of-developers-building-the-future-one-line-at-a-time-4hof</guid>
      <description>&lt;p&gt;Developers are no longer just problem solvers—they shape how the modern world works, from everyday apps to global systems.&lt;/p&gt;

&lt;p&gt;Tech is now more accessible than ever, with open-source tools and online learning allowing anyone to enter the field. Success depends on adaptability, as developers must continuously learn and think beyond code to solve real-world problems.&lt;/p&gt;

&lt;p&gt;Remote work has made development a global opportunity, though challenges like burnout remain. As AI and other technologies grow, developers have a unique chance to build solutions that are ethical and impactful.&lt;/p&gt;

&lt;p&gt;Being a developer is more than a job it’s a mindset that drives the future forward.&lt;/p&gt;

</description>
      <category>programming</category>
    </item>
  </channel>
</rss>
