<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ai on Mikolaj Karebski - Engineering Notes</title><link>https://blog.karebski.dev/tags/ai/</link><description>Recent content in Ai on Mikolaj Karebski - Engineering Notes</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Fri, 29 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.karebski.dev/tags/ai/index.xml" rel="self" type="application/rss+xml"/><item><title>Please Do Not Send AI Slop To Your Coworkers</title><link>https://blog.karebski.dev/posts/please-do-not-send-ai-slop-to-your-coworkers/</link><pubDate>Fri, 29 May 2026 00:00:00 +0000</pubDate><guid>https://blog.karebski.dev/posts/please-do-not-send-ai-slop-to-your-coworkers/</guid><description>On our helpdesk, we recently received a message like this. I obfuscated the details from the original message, but the structure is unchanged.
Message from the developer &amp;mdash;&amp;mdash; START OF THE MESSAGE &amp;mdash;&amp;ndash;
Summary
The @acme/ui CDN buckets serve manifest.json without an Access-Control-Allow-Origin header, so the @acme/ui dev harness cannot read it cross-origin and shows every environment as &amp;ldquo;unreachable&amp;rdquo;. We need CORS enabled on the buckets cdnstaging (staging) and cdnprod (production).</description></item><item><title>How I use AI</title><link>https://blog.karebski.dev/posts/how-i-use-ai/</link><pubDate>Mon, 11 May 2026 00:00:00 +0000</pubDate><guid>https://blog.karebski.dev/posts/how-i-use-ai/</guid><description>Colleagues often ask me if I&amp;rsquo;m worried about the growth of AI and if it will take my job away. Honestly, not really. What worries me is not that AI is capable of writing code or even complete solutions, but how quickly people are willing to hand over responsibility to it.
I&amp;rsquo;ve worked with people who treat AI agents like servants that do everything for them. One agent writes code, another reviews it, then yet another posts on Slack that it&amp;rsquo;s done, so the first one can deploy the change to production.</description></item></channel></rss>