<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Coding on Lorbic</title><link>http://localhost:1313/tags/coding/</link><description>Recent content in Coding on Lorbic</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 29 Mar 2026 23:55:00 +0530</lastBuildDate><atom:link href="http://localhost:1313/tags/coding/index.xml" rel="self" type="application/rss+xml"/><item><title>AI Coding in 2026: Productivity Multipliers vs. Skill Replacements</title><link>http://localhost:1313/ai-coding-productivity-vs-skill/</link><pubDate>Sat, 28 Mar 2026 23:00:00 +0530</pubDate><guid>http://localhost:1313/ai-coding-productivity-vs-skill/</guid><description>&lt;p>&amp;ldquo;Write a REST API with authentication&amp;rdquo;.&lt;/p>
&lt;p>I hit enter. Thirty seconds later, Claude spat out 400 lines of perfectly formatted Go code. JWT middleware, password hashing, error handling, even rate limiting. It looked professional. It looked production-ready.&lt;/p>
&lt;p>It took me three hours to figure out why the token refresh logic had a race condition.&lt;/p>
&lt;p>This is AI-assisted coding in 2026. It&amp;rsquo;s not magic. It&amp;rsquo;s not a replacement. It&amp;rsquo;s a very fast junior developer that never gets tired, never complains, and confidently makes mistakes you won&amp;rsquo;t catch unless you actually understand the &lt;strong>architectural nuances&lt;/strong> of what you&amp;rsquo;re building.&lt;/p></description></item></channel></rss>