<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Communication on Mikolaj Karebski - Engineering Notes</title><link>https://blog.karebski.dev/tags/communication/</link><description>Recent content in Communication 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/communication/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></channel></rss>