<?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: Rirash</title>
    <description>The latest articles on DEV Community by Rirash (@codesavvy_labs_fb381b820c).</description>
    <link>https://dev.to/codesavvy_labs_fb381b820c</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%2F2432396%2F2bd48880-e9a2-41bc-b3de-84cb1f9cd450.jpg</url>
      <title>DEV Community: Rirash</title>
      <link>https://dev.to/codesavvy_labs_fb381b820c</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/codesavvy_labs_fb381b820c"/>
    <language>en</language>
    <item>
      <title>You’re Doing It Wrong The Wake-Up Call That Changed Everything</title>
      <dc:creator>Rirash</dc:creator>
      <pubDate>Wed, 09 Apr 2025 07:17:37 +0000</pubDate>
      <link>https://dev.to/codesavvy_labs_fb381b820c/youre-doing-it-wrong-the-wake-up-call-that-changed-everything-2gfd</link>
      <guid>https://dev.to/codesavvy_labs_fb381b820c/youre-doing-it-wrong-the-wake-up-call-that-changed-everything-2gfd</guid>
      <description>&lt;h2&gt;
  
  
  The Stuck Developer
&lt;/h2&gt;

&lt;p&gt;My friend—let’s call him Hamza—was trapped.&lt;/p&gt;

&lt;p&gt;Not in a dramatic, cinematic way, but in the slow, soul-crushing grind of job applications, unanswered emails, and projects that vanished into the void. Every day, he sat in the same dimly lit café, headphones on, fingers flying over his keyboard, eyes hollow. His laptop hummed with life; he did not.&lt;/p&gt;

&lt;p&gt;I slid into the seat across from him, asking the same question I had for months: “Any responses?”&lt;/p&gt;

&lt;p&gt;A slow shake of his head. His gaze stayed locked on the screen, as if staring harder might summon an opportunity.&lt;/p&gt;

&lt;p&gt;Then—intervention.&lt;/p&gt;

&lt;p&gt;A man at the next table—mid-30s, beard, hoodie that read “Backend Never Dies”—turned toward us and said:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;“You’re doing it wrong.”&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Hamza and I froze. The stranger didn’t apologize. He stood, grabbed his coffee, and joined our table like he’d been invited.&lt;/p&gt;

&lt;p&gt;“Not trying to be rude,” he said. “But I’ve been where you are. And I see this every day.”&lt;/p&gt;

&lt;p&gt;His name was Alex.as he introduced, No last name, no LinkedIn plug—just Alex. A former telco engineer turned backend developer who’d helped a dozen juniors land jobs. Not by teaching them to code better, but by showing them what nobody else would.&lt;/p&gt;

&lt;p&gt;Hamza leaned in. So did I.&lt;br&gt;
The Hard Truths&lt;/p&gt;

&lt;p&gt;Alex asked what Hamza had built.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;“A blog API, a to-do app, some microservices…”&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;A knowing smile.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;“Let me guess—FastAPI, PostgreSQL, maybe Docker, but nothing actually deployed? No README, no architecture diagrams, no proof of how you think?”&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Silence.&lt;/p&gt;

&lt;p&gt;Alex leaned back, locking eyes with Hamza.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;“Here’s your first truth: You’re not being ignored because you’re bad. You’re being ignored because you’re invisible.”&lt;/p&gt;

&lt;p&gt;“You’re solving problems no one sees. Building things that don’t break. No logs, no tests, no real-world mess. That’s not backend engineering—that’s just coding.”&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Then, the gut punch:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;“Have you ever debugged someone else’s broken code?”&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Hamza admitted he hadn’t.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;“Second truth: If you can’t navigate chaos, you’re not ready. Most juniors think the job is building. It’s not. It’s fixing.”&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Alex pulled out his phone, opened GitHub, and showed a repo—messy, imperfect, but alive. Daily commits. Failure logs. Diagrams. Notes on what went wrong.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;“Hard truth number three: Nobody cares what you can do in theory. They care what you’ve done when everything exploded.”&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Hamza swallowed. “Then… what do I change?”&lt;/p&gt;

&lt;p&gt;Alex didn’t hesitate.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;“Build ugly. Build broken. Deploy something that crashes—then show how you fixed it. Write logs. Document failures. Make your GitHub a war story, not a tutorial graveyard.”&lt;/p&gt;

&lt;p&gt;“Don’t apply to 100 jobs. Apply to 20—but make sure your work screams, ‘I solve real problems.’”&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Then, the final blow:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;“Stop calling yourself a ‘junior.’ Say you’re a backend developer. Act like one. Nobody hires people who look unsure. They hire people who ship.”&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;With that, he stood, leaving one last piece of wisdom hanging in the air:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;“You don’t need permission. You need proof. Stack rejections like XP. At 50, you’ll be unstoppable.”&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;And just like that—he was gone.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Turnaround
&lt;/h2&gt;

&lt;p&gt;That night, Hamsa deleted every half-finished project. He picked one idea—a Quran recitation tracker—and rebuilt it, differently.&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;- Schema first. He mapped the database on paper before writing a single line.

- Tests, logs, edge cases. He hunted for bugs instead of avoiding them.

- Public deployment. He put it on Railway, documenting every failure.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;p&gt;Six weeks later, a DM:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;“Saw your repo. We’ve got a junior backend role. You game?”&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;He started two months ago.&lt;/p&gt;

&lt;p&gt;Now? When he sees stuck developers, he tells them what Alex told us.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Takeaway
&lt;/h2&gt;

&lt;p&gt;This isn’t about luck or genius. It’s about shifting your mindset:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;From “Please hire me” to “Here’s what I can do.”&lt;/li&gt;
&lt;li&gt;From “I need more tutorials” to “I need a messy project to fix.”&lt;/li&gt;
&lt;li&gt;From “I’m invisible” to “I’ll make you see me.”&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Being ignored isn’t rejection—it’s feedback. “You’re not visible yet.”&lt;/p&gt;

&lt;p&gt;You already know enough to build something real. The question is:&lt;/p&gt;

&lt;p&gt;Will it be another perfect, forgettable project—or something ugly, broken, and impossible to ignore?&lt;/p&gt;

&lt;h2&gt;
  
  
  The Backend Growth Roadmap (Do This Now)
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Pick one real-world problem&lt;/strong&gt; (e.g., Quran tracker, budget app, reminder system).&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Design your database first&lt;/strong&gt; (think relationships, constraints, scale).&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Build → Break → Fix&lt;/strong&gt; (embrace the mess).&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Add logs, tests, error handling&lt;/strong&gt; (simulate production chaos).&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Deploy publicly&lt;/strong&gt; (Railway, Render, Fly.io).&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Document everything&lt;/strong&gt; (README, failure logs, architecture diagrams).&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Share with proof&lt;/strong&gt; (Post it. Tag devs. Ask for brutal feedback.)&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Stop waiting for permission. Start building proof.&lt;/p&gt;

&lt;p&gt;Inspired? Tag a developer who needs this. Or better yet—open your IDE and build like it’s the project that gets you hired.&lt;/p&gt;

</description>
      <category>backenddev</category>
      <category>career</category>
      <category>programming</category>
      <category>beginners</category>
    </item>
    <item>
      <title>Why You’re Not Making Money or Tangible Progress</title>
      <dc:creator>Rirash</dc:creator>
      <pubDate>Tue, 11 Mar 2025 06:42:10 +0000</pubDate>
      <link>https://dev.to/codesavvy_labs_fb381b820c/why-youre-not-making-money-or-tangible-progress-j21</link>
      <guid>https://dev.to/codesavvy_labs_fb381b820c/why-youre-not-making-money-or-tangible-progress-j21</guid>
      <description>&lt;p&gt;&lt;strong&gt;The Painful Reality of Hard Work Without Results&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F6ac1ytcwkvp2wxj3w7hu.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F6ac1ytcwkvp2wxj3w7hu.jpg" alt="pain" width="800" height="572"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Imagine working or studying for more than 10 hours every day, yet feeling like you’re stuck in the same place. No real progress, no financial breakthrough—just endless effort with nothing to show for it.&lt;/p&gt;

&lt;p&gt;I know that feeling because I was once there. For five years, I worked tirelessly, believing I was a professional, yet I had no clients, no major achievements, and no financial growth. It was frustrating. I started questioning everything: Was I not skilled enough? Was I missing something?&lt;/p&gt;

&lt;p&gt;But then, I discovered the real reasons behind my stagnation, and everything changed. Today, I want to share with you why this happens, what causes it, and most importantly, how you can break free and start making real progress.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The Trap of "Feeling Busy" Without Moving Forward&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F53b5fb9qt1qxl3n4zu59.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F53b5fb9qt1qxl3n4zu59.jpg" alt="trap" width="800" height="532"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Many people believe that working long hours is the key to success. You might think, If I just keep pushing, things will eventually fall into place. But here’s the hard truth: being busy doesn’t mean being productive.&lt;/p&gt;

&lt;p&gt;For years, I woke up early, stayed up late, and filled my days with endless work. I convinced myself that I was making progress. But one day, I looked back and realized that despite all my effort, I had nothing to show for it.&lt;/p&gt;

&lt;p&gt;I was caught in a cycle of:&lt;br&gt;
✔️ Learning more instead of applying what I knew.&lt;br&gt;
✔️ Working without a clear direction or strategy.&lt;br&gt;
✔️ Avoiding the uncomfortable tasks that actually move the needle.&lt;/p&gt;

&lt;p&gt;The solution? Stop focusing on doing more and start focusing on doing the right things. Ask yourself:&lt;/p&gt;

&lt;p&gt;Am I just learning and working, or am I applying and executing?&lt;/p&gt;

&lt;p&gt;Am I focusing on what truly brings results, or just staying busy?&lt;/p&gt;

&lt;p&gt;If you feel stuck, it’s time to shift your mindset from "hard work" to "impactful work."&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The Skill vs. Business Gap: Why Being "Good" Isn't Enough&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fde2vxzl1k3t95r2wb84q.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fde2vxzl1k3t95r2wb84q.jpg" alt="skilled" width="800" height="533"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Have you ever seen someone with less skill than you making more money? It’s frustrating, right? But the truth is, being good at something is not enough.&lt;/p&gt;

&lt;p&gt;For years, I thought my skills would naturally attract clients and opportunities. But then I saw people who weren’t as talented as me landing high-paying projects. That’s when I realized: success isn’t just about skill—it’s about visibility and positioning.&lt;/p&gt;

&lt;p&gt;If people don’t know you exist, they won’t hire you. If you don’t market yourself, no one will see your value. That’s why you need to:&lt;/p&gt;

&lt;p&gt;Build a personal brand. Show your work, share your knowledge, and let people know what you do.&lt;/p&gt;

&lt;p&gt;Network and connect. Opportunities come from people, not just skills.&lt;/p&gt;

&lt;p&gt;Solve real problems. People don’t pay for talent; they pay for solutions.&lt;/p&gt;

&lt;p&gt;If you’re not making progress, don’t just focus on getting better—focus on getting seen and selling your value.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The Fear That’s Secretly Holding You Back&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F2mnh4czhnmsg08rnix76.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F2mnh4czhnmsg08rnix76.jpg" alt="feer" width="800" height="533"&gt;&lt;/a&gt;&lt;br&gt;
Many times, the biggest thing stopping us isn’t a lack of skills or opportunities—it’s fear.&lt;/p&gt;

&lt;p&gt;I spent years avoiding the things that could actually change my situation. I didn’t share my work because I was afraid of judgment. I didn’t reach out to clients because I feared rejection. I told myself, I just need more time to improve, when in reality, I was just scared to take action.&lt;/p&gt;

&lt;p&gt;Fear keeps us in our comfort zones, convincing us to delay the very things that could lead to progress. But here’s the truth: success is on the other side of discomfort.&lt;/p&gt;

&lt;p&gt;If you feel stuck, ask yourself:&lt;/p&gt;

&lt;p&gt;What am I avoiding that could change my situation?&lt;/p&gt;

&lt;p&gt;What’s one uncomfortable step I can take today?&lt;/p&gt;

&lt;p&gt;Growth happens when you stop waiting and start doing—even when it’s scary.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Final Words: Take Control of Your Progress&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;If you’ve been stuck, it’s time to make a change. Stop believing that just working hard is enough. Instead:&lt;br&gt;
✅ Work on what truly matters, not just what keeps you busy.&lt;br&gt;
✅ Focus on visibility and marketing, not just skill.&lt;br&gt;
✅ Stop letting fear hold you back—take bold action.&lt;/p&gt;

</description>
      <category>codenewbie</category>
      <category>beginners</category>
      <category>productivity</category>
      <category>career</category>
    </item>
  </channel>
</rss>
