<?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: John Nguyen</title>
    <description>The latest articles on DEV Community by John Nguyen (@hoangsondeveloper).</description>
    <link>https://dev.to/hoangsondeveloper</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%2F3883854%2F8239f751-b529-42e6-bf3e-2543a9fb7ba9.png</url>
      <title>DEV Community: John Nguyen</title>
      <link>https://dev.to/hoangsondeveloper</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/hoangsondeveloper"/>
    <language>en</language>
    <item>
      <title>Vibe coding feels great… until debugging</title>
      <dc:creator>John Nguyen</dc:creator>
      <pubDate>Fri, 17 Apr 2026 08:55:51 +0000</pubDate>
      <link>https://dev.to/hoangsondeveloper/vibe-coding-feels-great-until-debugging-pao</link>
      <guid>https://dev.to/hoangsondeveloper/vibe-coding-feels-great-until-debugging-pao</guid>
      <description>&lt;h2&gt;
  
  
  The hidden problem with fast-growing codebases (and why debugging gets harder over time)
&lt;/h2&gt;

&lt;blockquote&gt;
&lt;p&gt;Lately, I’ve been doing a lot of “vibe coding” 😄&lt;br&gt;
(build fast, ship fast, iterate fast)&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;At the beginning, everything feels great:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Features ship quickly&lt;/li&gt;
&lt;li&gt;The app works&lt;/li&gt;
&lt;li&gt;You feel productive&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  But as the codebase grows…
&lt;/h2&gt;

&lt;p&gt;Something starts to change.&lt;/p&gt;

&lt;p&gt;Not suddenly, but gradually:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Code becomes harder to review deeply&lt;/li&gt;
&lt;li&gt;Bugs take longer to understand&lt;/li&gt;
&lt;li&gt;Bad performance&lt;/li&gt;
&lt;li&gt;And most importantly… &lt;strong&gt;it becomes harder to trace the root cause&lt;/strong&gt;
&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  It’s not about bad code
&lt;/h2&gt;

&lt;p&gt;At first, I thought:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;“Maybe the code quality isn’t good enough”&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;But that wasn’t really the problem.&lt;/p&gt;

&lt;p&gt;The real issue was:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;I was losing the ability to &lt;strong&gt;reason about the system&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  The real pain: losing traceability
&lt;/h2&gt;

&lt;p&gt;When the system is small:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;You know where state comes from&lt;/li&gt;
&lt;li&gt;You know what triggers what&lt;/li&gt;
&lt;li&gt;You can mentally simulate the flow&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;But when it grows:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;State updates happen across many places&lt;/li&gt;
&lt;li&gt;Transitions become implicit&lt;/li&gt;
&lt;li&gt;Logic is distributed and harder to follow&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;And then:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;You can no longer reconstruct &lt;em&gt;what actually happened&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  What happens when you lose traceability?
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Debugging becomes guesswork&lt;/li&gt;
&lt;li&gt;Fixes feel uncertain&lt;/li&gt;
&lt;li&gt;Performance issues are treated at the symptom level&lt;/li&gt;
&lt;li&gt;You lose confidence in the system&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  A simple idea: what if state had a clear flow?
&lt;/h2&gt;

&lt;p&gt;This led me to a simple question:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;What if we could &lt;strong&gt;see how state moves through the system?&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Instead of scattered updates, think in terms of:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;state → action → next state
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Where every transition is explicit and traceable.&lt;/p&gt;




&lt;h2&gt;
  
  
  I built a small experiment
&lt;/h2&gt;

&lt;p&gt;I turned this idea into a small library:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;react-state-flow&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;NPM: &lt;a href="https://www.npmjs.com/package/react-state-flow/v/0.4.1" rel="noopener noreferrer"&gt;https://www.npmjs.com/package/react-state-flow/v/0.4.1&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;GitHub: &lt;a href="https://github.com/HoangSonDeveloper/React-State-Flow" rel="noopener noreferrer"&gt;https://github.com/HoangSonDeveloper/React-State-Flow&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&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%2Fs05ebqptli20mrxe669q.gif" 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%2Fs05ebqptli20mrxe669q.gif" alt="Demo gif" width="760" height="390"&gt;&lt;/a&gt;&lt;br&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%2Fkjuyat8jq4q893miytmt.png" 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%2Fkjuyat8jq4q893miytmt.png" alt="Demo image" width="800" height="820"&gt;&lt;/a&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  What improved (for me)
&lt;/h2&gt;

&lt;p&gt;After trying this approach:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;I could trace what happened more easily&lt;/li&gt;
&lt;li&gt;State changes became predictable&lt;/li&gt;
&lt;li&gt;Debugging had a clear direction instead of guessing&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Open questions
&lt;/h2&gt;

&lt;p&gt;I’d really love feedback from others:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Do you face similar issues in large codebases?&lt;/li&gt;
&lt;li&gt;Does this approach make sense, or is it over-engineering?&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;If you read this far — thank you 🙏 &lt;br&gt;
If you find this useful, feel free to give it a ⭐ on GitHub!&lt;br&gt;
Would love to hear your thoughts.&lt;/p&gt;




</description>
      <category>react</category>
      <category>reactnative</category>
      <category>redux</category>
      <category>zustand</category>
    </item>
  </channel>
</rss>
