Yesterday, I helped two people vibe-code solutions. Both were non-expert IT pros who can code but aren’t fluent. Person Alpha and I were on a call in the morning. Alpha needed to OCR PDF pages. I bragged, “Ten minutes. Let’s do it now!” But I was on a train with only my phone, so Alpha had to code. Vibe-coding was the only option. ...
I use Codex and Jules to code while I walk. I’ve merged several PRs without careful review. This added technical debt. This weekend, I spent four hours fixing the AI generated tests and code. What mistakes did it make? Inconsistency. It flips between execCommand("copy") and clipboard.writeText(). It wavers on timeouts (50 ms vs 100 ms). It doesn’t always run/fix test cases. Missed edge cases. I switched <div> to <form>. My earlier code didn’t have a type="button", so clicks reloaded the page. It missed that. It also left scripts as plain <script> instead of <script type="module"> which was required. ...
Is your code built to last? Mohammed Niyas P shares a developer war story. His shortcut worked. It delivered working code. But 5 years later, when it failed, he didn’t expect he’d still be around to clean it up. https://gramener.com/developerwarstories/this-tech-debt-made-me-humble Found this tale on technical debt interesting? Gramener is #hiring #developers for a technical lead role. See https://gramener.com/job/?id=90520 Nikhil Kabbin – your story’s up next 😉 LinkedIn