<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Flutter Desktop Apps on Mike CK - Electrical Engineer and Developer</title><link>https://www.drmhse.com/series/flutter-desktop-apps/</link><description>Recent content in Flutter Desktop Apps on Mike CK - Electrical Engineer and Developer</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 24 May 2026 20:44:57 +0300</lastBuildDate><atom:link href="https://www.drmhse.com/series/flutter-desktop-apps/index.xml" rel="self" type="application/rss+xml"/><item><title>Bringing a Face to the Buzz: Why I Built a UI for Perplexity’s Bumblebee Scanner</title><link>https://www.drmhse.com/posts/bringing-a-face-to-the-buzz-why-i-built-a-ui-for-perplexity-bumblebee-scanner/</link><pubDate>Sun, 24 May 2026 19:36:43 +0300</pubDate><guid>https://www.drmhse.com/posts/bringing-a-face-to-the-buzz-why-i-built-a-ui-for-perplexity-bumblebee-scanner/</guid><description>&lt;p>AI coding agents and package managers are incredibly convenient, but they also introduce massive new vectors for supply-chain attacks. Earlier this week, the security and AI engineering teams at Perplexity open-sourced a fantastic new internal tool called &lt;strong>Bumblebee&lt;/strong>. If you missed the announcement, Bumblebee is a wildly fast, read-only supply-chain scanner for developer endpoints.&lt;/p>
&lt;p>Unlike traditional vulnerability scanners that run in your CI/CD pipeline, Bumblebee runs locally. It sweeps your local cache (npm, Go modules, PyPI, etc.), editor extensions, and even AI agent configs to see if you have any compromised packages sitting on your machine. And crucially, it&amp;rsquo;s strictly read-only—it parses lockfiles and manifests without ever executing sketchy &lt;code>postinstall&lt;/code> scripts that could trigger a dormant payload.&lt;/p></description></item><item><title>Your AI Coding Agent Deserves a Real Review Desk</title><link>https://www.drmhse.com/posts/building-jules-flutter-client/</link><pubDate>Sun, 10 May 2026 09:00:00 +0300</pubDate><guid>https://www.drmhse.com/posts/building-jules-flutter-client/</guid><description>&lt;p>We&amp;rsquo;ve all been there: you ask an AI coding agent to write a complex feature, and it spits back a massive wall of code in a tiny chat window. Sure, it can write code—but how do you actually review what changed? How do you keep track of the work without losing your mind?&lt;/p>
&lt;p>An agent workflow quickly falls apart if the client feels like just another thin chat box. What you really need is a dedicated workbench.&lt;/p></description></item></channel></rss>