The latest articles on DEV Community by smith yok (@smith_yok_2f3b43d85b50bfa). https://dev.to/smith_yok_2f3b43d85b50bfa https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4108539%2Fa654301b-992c-4b67-b367-072a0ba19e0f.png https://dev.to/smith_yok_2f3b43d85b50bfa en smith yok Thu, 03 Sep 2026 17:58:12 +0000 https://dev.to/smith_yok_2f3b43d85b50bfa/i-vibe-coded-a-numerology-calculator-with-ai-heres-what-actually-worked-5c81 https://dev.to/smith_yok_2f3b43d85b50bfa/i-vibe-coded-a-numerology-calculator-with-ai-heres-what-actually-worked-5c81 <p>I've been experimenting with AI-assisted development lately — mostly "vibe coding," where you describe what you want and iterate through conversation rather than writing every line yourself. Wanted to share what that process actually looked like on a real project.</p> <h2> The Project </h2> <p>A free numerology calculator called Destiny Matrix Chart — it takes a birth date and generates a visual chart (SVG-based octagram) with calculated positions, all client-side, no backend.</p> <h2> What "Vibe Coding" Actually Looked Like </h2> <ul> <li>Described the core calculation logic (digit-reduction algorithms) in plain language, iterated on edge cases together</li> <li>Built the SVG chart generation through back-and-forth — describing the visual layout, adjusting positions, colors, and spacing conversationally</li> <li>Debugged a genuinely annoying WordPress content-filter issue where <code>&lt;script&gt;</code> tags kept getting mangled on paste (wpautop stripping things it shouldn't). Ended up base64-encoding the payload and decoding it at runtime to sidestep it entirely — not something I would've thought to try without talking through the problem out loud first.</li> </ul> <h2> What Surprised Me </h2> <p>The bottleneck wasn't writing code, it was describing intent clearly enough. Vague requests got vague results. Being specific about edge cases, data structures, and constraints upfront saved a lot of back-and-forth.</p> <h2> The Result </h2> <p>Everything runs client-side — vanilla JS, SVG generation, no dependencies. You can see it live here:<a href="https://destinymatrixchart.co/" rel="noopener noreferrer">https://destinymatrixchart.co/</a></p> <p>Curious if others have run into similar friction points with AI-assisted builds, especially around CMS quirks like the one above. What's tripped you up?</p> ai programming webdev javascript