<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Writing on Jakub Wolynko</title><link>https://jakubwolynko.eu/tags/writing/</link><description>Recent content in Writing on Jakub Wolynko</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Jakub Wołynko and the Hugo Authors</copyright><lastBuildDate>Thu, 15 Jan 2026 10:00:00 +0100</lastBuildDate><atom:link href="https://jakubwolynko.eu/tags/writing/index.xml" rel="self" type="application/rss+xml"/><item><title>Why I'm Back</title><link>https://jakubwolynko.eu/blog/202601-why-im-back/</link><pubDate>Thu, 15 Jan 2026 10:00:00 +0100</pubDate><guid>https://jakubwolynko.eu/blog/202601-why-im-back/</guid><description>
&lt;p>It's been a while. More than a year, actually.&lt;/p>
&lt;p>If you've been reading this blog for some time — and I genuinely appreciate
it if you have — you probably noticed that posts became regular, and then quietly stopped.
No goodbye post, no announcement. Just silence. So here's the honest version of what happened.&lt;/p>
&lt;h2 id="the-ai-problem">The AI problem&lt;/h2>
&lt;p>At some point in 2025, every time I sat down to write a &amp;quot;how to deploy X on Y&amp;quot; post, I felt a strange friction.
Not exactly writer's block. Something more like — &lt;em>what's the point?&lt;/em> ChatGPT, Claude, Gemini — pick one.
They can answer most how-to questions faster and more accurately than a blog post written months earlier.
If you need to set up K3s on Hetzner or wire up &lt;code>ExternalSecrets&lt;/code> with Doppler, you'll get better, more current guidance
by just asking an AI than by landing on some tutorial that is already half-outdated before it was even published.&lt;/p></description></item></channel></rss>