<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Software on Yonk-Labs</title><link>https://yonk.dev/tags/software/</link><description>Recent content in Software on Yonk-Labs</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Yonk-Labs</copyright><lastBuildDate>Mon, 18 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://yonk.dev/tags/software/index.xml" rel="self" type="application/rss+xml"/><item><title>The Ugly Baby Method: Vibe, Reverse Engineer, Rebuild</title><link>https://yonk.dev/blog/ugly-baby-method/</link><pubDate>Mon, 18 May 2026 00:00:00 +0000</pubDate><guid>https://yonk.dev/blog/ugly-baby-method/</guid><description>Every project I&amp;rsquo;ve shipped in the last six months has been an ugly baby at some point — dead code, 11pm ideas that look stupid at 8am, three abstractions doing the same thing. That&amp;rsquo;s not failure, it&amp;rsquo;s the artifact you need. Put the ugly baby in a glass case, learn from it, then rebuild from zero.</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://yonk.dev/blog/ugly-baby-method/feature.jpg"/></item><item><title>Vibe Coding Isn't the Problem. Stopping at Vibe Coding Is.</title><link>https://yonk.dev/blog/beyond-vibe-coding/</link><pubDate>Sun, 17 May 2026 00:00:00 +0000</pubDate><guid>https://yonk.dev/blog/beyond-vibe-coding/</guid><description>Vibe coding is a real and useful phase — the problem is people stop there. The space between &amp;lsquo;I had an idea on a plane&amp;rsquo; and &amp;rsquo;this runs in an air-gapped Kubernetes cluster&amp;rsquo; is where the actual work happens. A generalizable playbook for the middle, starting with: treat the LLM like a very literal child.</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://yonk.dev/blog/beyond-vibe-coding/feature.jpg"/></item></channel></rss>