<?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 It Might be Working</title><link>https://iguessthatworks.com/tags/ai/</link><description>Recent content in AI on It Might be Working</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Jeff Mayeur</copyright><lastBuildDate>Wed, 29 Apr 2026 07:00:00 -0700</lastBuildDate><atom:link href="https://iguessthatworks.com/tags/ai/index.xml" rel="self" type="application/rss+xml"/><item><title>Day 2 of What's Next</title><link>https://iguessthatworks.com/posts/04-2026/day-2-whats-next/</link><pubDate>Wed, 29 Apr 2026 07:00:00 -0700</pubDate><guid>https://iguessthatworks.com/posts/04-2026/day-2-whats-next/</guid><description>
&lt;p&gt;Day 2 of what's next. Gratitude is the word of the day, but there's also some career stew steeping today. Like everyone in technology I'm continually re-learning my job as Agentic swarms have shifted the way we work. At base I think software engineering is still the codification of a process. It's taking decision trees, or actions and creating digital stand-ins that allow us to work faster and broader.&lt;/p&gt;
&lt;p&gt;Agents have shifted the way we understand the problem, accelerate the definition of the landscape and ultimately commodify&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt; the encoding of a solution, but the fundamental flow is still the same. Agents exist as both toys and tools. The name Cronagotchi — that I really want to stick — is what I call scheduled atomic agents that require a steady diet of tokens to thrive. These Cronagotchi are only a tool if they can be connected back to a fundamental problem or opportunity, otherwise they're fun pets that entertain but don't create measurable value.&lt;/p&gt;</description></item></channel></rss>