<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Developer Productivity on Rik Kisnah - Blog</title><link>https://rikkisnah.github.io/tags/developer-productivity/</link><description>Recent content in Developer Productivity on Rik Kisnah - Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 19 Apr 2026 10:00:00 -0700</lastBuildDate><atom:link href="https://rikkisnah.github.io/tags/developer-productivity/feed.xml" rel="self" type="application/rss+xml"/><item><title>Vibe Coding Is Making Engineers Lazy Where It Counts</title><link>https://rikkisnah.github.io/posts/vibe-coding-is-making-engineers-lazy-where-it-counts/</link><pubDate>Sun, 19 Apr 2026 10:00:00 -0700</pubDate><guid>https://rikkisnah.github.io/posts/vibe-coding-is-making-engineers-lazy-where-it-counts/</guid><description>1,658 words · 8 min read
Disclaimer: This post reflects my personal views and does not represent the views of my employer.
Caveat: This was written with research assistance from AI tools, but I curated the content, edited the draft, and cross-checked the references.
Image: The illustration above was generated with xAI Grok.
The Moment I Keep Having I keep having the same moment (deja vu over deja-vus) with vibe coding.</description></item></channel></rss>