<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AI Case Lib – What Are the Best AI Use Cases in 2026?</title><link>/authors/jeff/</link><description>Recent content on AI Case Lib – What Are the Best AI Use Cases in 2026?</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 11 Sep 2026 10:53:00 +0800</lastBuildDate><atom:link href="/authors/jeff/index.xml" rel="self" type="application/rss+xml"/><item><title>Automated Lead Scoring with AI - Letting the System Decide Who's Worth Calling</title><link>/automation/lead-scoring-with-ai/</link><pubDate>Fri, 11 Sep 2026 10:53:00 +0800</pubDate><guid>/automation/lead-scoring-with-ai/</guid><description>&lt;h1 id="automated-lead-scoring-with-ai-letting-the-system-decide-whos-worth-calling"&gt;Automated Lead Scoring with AI: Letting the System Decide Who&amp;rsquo;s Worth Calling&lt;/h1&gt;&#10;&lt;p&gt;Every sales team eventually runs into the same problem: leads come in faster than reps can meaningfully follow up on them, and not all leads are created equal. A demo request from a Fortune 500 procurement director and a newsletter sign-up from a curious student both land in the same CRM queue, and someone — usually a rep working off gut instinct and a half-remembered pattern from last quarter — has to decide which one gets a phone call today. Automated lead scoring exists to take that decision out of gut instinct and put it into a system.&lt;/p&gt;</description></item><item><title>Move Over, Smart Glasses — Your Phone Case Wants to Talk</title><link>/marketing/move-over-smart-glasses-your-phone-case-wants-to-talk/</link><pubDate>Thu, 10 Sep 2026 10:01:35 +0800</pubDate><guid>/marketing/move-over-smart-glasses-your-phone-case-wants-to-talk/</guid><description>&lt;h1 id="move-over-smart-glasses--your-phone-case-wants-to-talk"&gt;Move Over, Smart Glasses — Your Phone Case Wants to Talk&lt;/h1&gt;&#10;&lt;p&gt;AI hardware has had a rough couple of years trying to figure out where on the human body it&amp;rsquo;s allowed to live. Smart glasses perch on your nose like a very expensive, very needy houseguest. AI pendants dangle around your neck, silently judging your conversations. Earbuds burrow into your ear canal. Smart rings and bands cling to your skin like tiny clingy robots. Every single one of these asks you to adopt a new habit, wear something extra, remember to charge yet another gadget.&lt;/p&gt;</description></item><item><title>Coding Was Never the Moat, Why Industry Insight Still Wins in the Age of AI</title><link>/engineering/coding-not-the-moat-industry-insight/</link><pubDate>Wed, 09 Sep 2026 10:30:00 +0800</pubDate><guid>/engineering/coding-not-the-moat-industry-insight/</guid><description>&lt;h1 id="coding-was-never-the-moat-why-industry-insight-still-wins-in-the-age-of-ai"&gt;Coding Was Never the Moat: Why Industry Insight Still Wins in the Age of AI&lt;/h1&gt;&#10;&lt;p&gt;There&amp;rsquo;s a line that&amp;rsquo;s been circulating that captures something important about where we actually stand with AI right now:&lt;/p&gt;&#10;&lt;blockquote&gt;&#10;&lt;p&gt;(&amp;ldquo;Coding was never the core competitive advantage — your industry insight, product sense, and overall capability are. Speed was never the advantage either — creating value is. If you have an idea, AI can help you build it fast. So AI is a tool for boosting productivity. But once AI develops something like autonomous judgment and can outthink 99% of humans, the question shifts entirely to whether people can master it skillfully. Being able to control AI the way you control a car — that&amp;rsquo;s the real core skill.&amp;rdquo;)&lt;/p&gt;</description></item><item><title>Drowning in Repetition: How AI Is Quietly Rewiring the Job of "Operations"</title><link>/operations/drowning-in-repetition-how-ai-is-rewiring-operations/</link><pubDate>Tue, 08 Sep 2026 12:06:00 +0800</pubDate><guid>/operations/drowning-in-repetition-how-ai-is-rewiring-operations/</guid><description>&lt;h1 id="drowning-in-repetition-how-ai-is-quietly-rewiring-the-job-of-operations"&gt;Drowning in Repetition: How AI Is Quietly Rewiring the Job of &amp;ldquo;Operations&amp;rdquo;&lt;/h1&gt;&#10;&lt;h2 id="the-problem-a-job-built-on-repetition"&gt;The Problem: A Job Built on Repetition&lt;/h2&gt;&#10;&lt;p&gt;Anyone who has worked in operations knows the feeling: more than half of the job is mechanical. The same piece of content has to be reshaped for five different platforms — each with its own tone, length, and format — and by the third rewrite, motivation is already gone. Add in weekly reports, livestream scripts, and vague requirements that need to be broken down into actionable checklists, and it&amp;rsquo;s clear why so much of operations work feels less like strategy and more like manual labor.&lt;/p&gt;</description></item><item><title>Building a GORM CRUD Module with Codex A Golang Engineer's Workflow</title><link>/engineering/codex-gorm-crud/</link><pubDate>Sat, 05 Sep 2026 12:30:00 +0800</pubDate><guid>/engineering/codex-gorm-crud/</guid><description>&lt;h1 id="building-a-gorm-crud-module-with-codex-a-golang-engineers-workflow"&gt;Building a GORM CRUD Module with Codex: A Golang Engineer&amp;rsquo;s Workflow&lt;/h1&gt;&#10;&lt;p&gt;As a Golang backend engineer, I spend a fair amount of my time writing repetitive boilerplate: struct definitions, GORM model tags, CRUD handlers, request validation, and the wiring that connects them all to an HTTP router. It&amp;rsquo;s the kind of work that isn&amp;rsquo;t hard, but it&amp;rsquo;s tedious enough to be a good candidate for AI-assisted development. Recently I used Codex to scaffold and refine a full CRUD management module for a single database table, and the experience taught me a few things about how to work effectively with an AI coding agent on a real Go project. This post walks through that workflow.&lt;/p&gt;</description></item></channel></rss>