<?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: Isaiah</title>
    <description>The latest articles on DEV Community by Isaiah (@zipqt).</description>
    <link>https://dev.to/zipqt</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%2F2593085%2F622c8cba-cbef-47ce-bb6b-6559252b03ac.png</url>
      <title>DEV Community: Isaiah</title>
      <link>https://dev.to/zipqt</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/zipqt"/>
    <language>en</language>
    <item>
      <title>Escape Solo Project Purgatory with Crux</title>
      <dc:creator>Isaiah</dc:creator>
      <pubDate>Tue, 21 Jan 2025 21:05:32 +0000</pubDate>
      <link>https://dev.to/zipqt/escape-solo-project-purgatory-with-crux-1iba</link>
      <guid>https://dev.to/zipqt/escape-solo-project-purgatory-with-crux-1iba</guid>
      <description>&lt;h2&gt;
  
  
  Problem
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;80% of side projects die in isolation&lt;/li&gt;
&lt;li&gt;"Help wanted" GitHub issues go stale&lt;/li&gt;
&lt;li&gt;Tutorial hell traps developers in loops&lt;/li&gt;
&lt;li&gt;Portfolio gaps persist, despite effort&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Solution: Crux
&lt;/h2&gt;

&lt;p&gt;Crux connects developers globally to build, learn, and ship real projects together.&lt;/p&gt;

&lt;h2&gt;
  
  
  Core
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;GitHub Integration: One-click repo import&lt;/li&gt;
&lt;li&gt;Advanced Project Discovery: Multi-parameter filtering + sorting engine&lt;/li&gt;
&lt;li&gt;Real-time Collab: In-platform chat + GitHub issue sync&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Flow
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Create profile&lt;/li&gt;
&lt;li&gt;Set tech preferences&lt;/li&gt;
&lt;li&gt;Discover projects&lt;/li&gt;
&lt;li&gt;Ship together&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Anti-Patterns We Kill
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Abandoned GitHub issues (active, engaged community)&lt;/li&gt;
&lt;li&gt;Project discovery friction (comprehensive filtering)&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Stack
&lt;/h2&gt;

&lt;p&gt;Frontend: Vue 3&lt;br&gt;
Backend: Go + Fiber + PostgreSQL&lt;/p&gt;

&lt;h2&gt;
  
  
  Traction
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;130+ active developers&lt;/li&gt;
&lt;li&gt;Growing daily community&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Benefits
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Ship real products&lt;/li&gt;
&lt;li&gt;Build portfolio proof&lt;/li&gt;
&lt;li&gt;Learn from peers&lt;/li&gt;
&lt;li&gt;Scale beyond tutorials&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;👉 &lt;a href="https://cruxapp.org" rel="noopener noreferrer"&gt;Ship your next project at Crux&lt;/a&gt; | 130+ devs already building&lt;/p&gt;

</description>
      <category>programming</category>
      <category>community</category>
      <category>sideprojects</category>
      <category>beginners</category>
    </item>
    <item>
      <title>Breaking Portfolio Paralysis: Why You Should Ship Your Side Projects</title>
      <dc:creator>Isaiah</dc:creator>
      <pubDate>Sun, 12 Jan 2025 04:38:43 +0000</pubDate>
      <link>https://dev.to/zipqt/breaking-portfolio-paralysis-why-most-developers-never-ship-their-best-ideas-4bb3</link>
      <guid>https://dev.to/zipqt/breaking-portfolio-paralysis-why-most-developers-never-ship-their-best-ideas-4bb3</guid>
      <description>&lt;p&gt;Every engineer has a hefty backlog of projects that will never see the light of day. It's normal. The problem isn't building - it's shipping. I recently launched my side project (shameless plug: &lt;a href="https://cruxapp.xyz/" rel="noopener noreferrer"&gt;crux&lt;/a&gt;) and the learning curve was astonishing.&lt;br&gt;
'Works on my machine' became my first lesson. Day one post-launch exposed critical mistakes: failing reactive components, UX friction points, and user interaction patterns I'd never encounter in localhost. Each user session generated more valuable debugging data than months of local testing.&lt;/p&gt;

&lt;p&gt;The accountability shifted everything. User feedback created immediate development priorities. Burnout resistance increased - user needs became a stronger motivator than personal development goals. The scope expanded beyond pure development: SEO optimization, user acquisition strategies, production secrets management, deployment pipelines.&lt;/p&gt;

&lt;p&gt;Core lesson: SHIP YOUR IDEAS. No project will ever be perfect. Launch with your MVP. Real users generate real engineering problems - and real engineering growth. The technical feedback loop with active users accelerates learning exponentially compared to private testing.&lt;br&gt;
Even failed launches are valuable data points. They expose architectural weaknesses, highlight scaling challenges, and force practical solutions to real problems. If you're building in localhost, you're optimizing for the wrong environment.&lt;/p&gt;

&lt;p&gt;Ship it. Debug in production. Learn as you go.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>programming</category>
      <category>productivity</category>
      <category>softwaredevelopment</category>
    </item>
    <item>
      <title>The Right Way to Use LLMs as a Developer</title>
      <dc:creator>Isaiah</dc:creator>
      <pubDate>Mon, 06 Jan 2025 03:28:44 +0000</pubDate>
      <link>https://dev.to/zipqt/the-right-way-to-use-llms-as-a-developer-1iob</link>
      <guid>https://dev.to/zipqt/the-right-way-to-use-llms-as-a-developer-1iob</guid>
      <description>&lt;p&gt;The rise of AI has been exciting to witness, especially as a developer. It's extremely tempting to pass off all my work to ChatGPT and Copilot and act as a sort of product manager instead of a developer. While this may seem nice in theory, it is actually quite destructive. &lt;/p&gt;

&lt;h2&gt;
  
  
  The Problem
&lt;/h2&gt;

&lt;p&gt;While AI is constantly evolving, and getting smarter, it's still nowhere near perfect. It is prone to mistakes, which you might miss if you don't properly understand the code, or worse yet if you blindly copy and paste. &lt;br&gt;
Aside from the obvious pitfall of AI making mistakes, it also negatively impacts your cognitive ability. Knowing how to quickly gather relevant information is an important skill for a developer. Overly relying on AI causes you to neglect this skill, as well as other essential skills for developers like problem-solving and in-depth thinking capabilities. You see it everywhere today, beginner developers are relying more and more on AI to write their code, and the quality of the programs they produce shows it (no offense).&lt;/p&gt;

&lt;h2&gt;
  
  
  Why it Matters
&lt;/h2&gt;

&lt;p&gt;Technically, it doesn't. If your goal is to show off the amount of LeetCode problems you've solved or push out side projects consisting of messy, unmaintainable code, then AI is the only tool you need! With that being said if you want to deepen your understanding of software development and hone your craft to a point you're proud of, you need to take a step back from the AI.&lt;/p&gt;

&lt;h2&gt;
  
  
  Take it From Me
&lt;/h2&gt;

&lt;p&gt;I'll admit, I was very excited to have my own personal coding assistant. Something I could ask every little question I had, and it wouldn't get annoyed or take forever to respond. But this was the beginning of something very detrimental to my growth. I stopped thinking for myself. When faced with an issue, I didn't even stop and think, I just pasted the code into whatever LLM I had open in the other tab, and let it do all the heavy lifting for me. My productivity skyrocketed of course, but I could genuinely feel myself getting dumber, and my code getting worse. It was harder to refactor, I didn't understand where bugs were happening, everything was so sloppy and my skills were at an all-time low.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Solution
&lt;/h2&gt;

&lt;p&gt;My approach has been to use LLMs as a way to deepen my understanding, rather than replace my ability to think. I disabled the copilot, closed the tab with Claude or GPT open, and focused on staying within vscode. When a problem arose, I stopped and thought about it, the way I used to. I quickly found myself getting sharper, and producing higher quality code again. That's not to say I never use LLMs, I use them very often! If I'm researching a problem, and someone mentions an approach I'm not familiar with, I use the LLM to help explain to me what the solution is, and why it works. This is where LLMs shine. Don't understand why code works? Have AI explain to you exactly what each line is doing. Need a better understanding of the difference between two solutions to a problem? Ask AI! The value of having something you can ask these sorts of questions to especially as a beginner is huge. This is how you should focus on making use of the LLMs, not just getting your work done for you.&lt;/p&gt;

&lt;h2&gt;
  
  
  TL;DR
&lt;/h2&gt;

&lt;p&gt;Use LLMs as your programming tutor. Don't let it replace your thinking - use it to enhance your understanding! To succeed as a developer you need to stay curious, don't let LLMs dull your curiosity. Stay curious, keep building, keep growing :)&lt;/p&gt;

&lt;p&gt;If you're interested in breaking your bad habits, and learning by building something real, check out this free platform I made for finding projects and teammates: &lt;a href="https://cruxapp.xyz/" rel="noopener noreferrer"&gt;https://cruxapp.xyz/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>beginners</category>
      <category>softwaredevelopment</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>Stop Coding Alone: A Wake-up Call.</title>
      <dc:creator>Isaiah</dc:creator>
      <pubDate>Sun, 05 Jan 2025 04:53:43 +0000</pubDate>
      <link>https://dev.to/zipqt/stop-coding-alone-a-wake-up-call-16p5</link>
      <guid>https://dev.to/zipqt/stop-coding-alone-a-wake-up-call-16p5</guid>
      <description>&lt;p&gt;If you're anything like me, you dreaded group projects in college. The awkward communication, stepping on each other's toes, and dealing with skill gaps – it felt like a mess. This is where my bad habit began.&lt;/p&gt;

&lt;p&gt;I'd rush through my portion of projects, completely missing the learning opportunity. I was the 'solo developer' – building websites and solving LeetCode problems in isolation. I convinced myself I was too skilled to 'waste time' collaborating with others.&lt;/p&gt;

&lt;p&gt;Then I met someone who shattered my ego.&lt;/p&gt;

&lt;p&gt;This developer was leagues ahead: Git mastery, production-ready projects, advanced design patterns – they had it all. I lucked into a group project with them, and it was a wake-up call. The gap between us wasn't just skill – it was perspective.&lt;/p&gt;

&lt;p&gt;Working alongside them transformed my development:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;My PRs needed fewer revisions&lt;/li&gt;
&lt;li&gt;My architectural decisions became more thoughtful&lt;/li&gt;
&lt;li&gt;My code grew more maintainable&lt;/li&gt;
&lt;li&gt;My Git workflow became cleaner&lt;/li&gt;
&lt;li&gt;My understanding of real-world development deepened&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Had I clung to my ego and kept coding alone, I'd still be writing mediocre code and using my LeetCode success as a coping mechanism.&lt;/p&gt;

&lt;p&gt;The truth? Being the antisocial developer is a huge blunder to your potential.&lt;/p&gt;

&lt;p&gt;Even if your technical skills surpass your teammates', there's always something to learn:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Different approaches to problem-solving&lt;/li&gt;
&lt;li&gt;New tools and workflows&lt;/li&gt;
&lt;li&gt;Better ways to structure code&lt;/li&gt;
&lt;li&gt;Improved communication skills&lt;/li&gt;
&lt;li&gt;Real-world project management&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Today, I'm building Crux to help developers avoid my mistakes. It's a platform where developers at all levels can find teammates and build together because the best growth happens through collaboration, not isolation.&lt;/p&gt;

&lt;p&gt;Ready to break out of the solo developer mindset?&lt;/p&gt;

&lt;p&gt;Here's my challenge to you: Post a project on Crux this week. Find a teammate or two who'll push your skills further, just like I did.&lt;/p&gt;

&lt;p&gt;Break the solo habit: &lt;a href="https://cruxapp.xyz/" rel="noopener noreferrer"&gt;https://cruxapp.xyz/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>programming</category>
      <category>beginners</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
