Watch your coding agents the way you watch your application logs: look for repeated work, hidden friction, and patterns you can turn into better tools.

LazyPi annoyed minimalists because it packages Pi with opinions, but that same convenience may help newcomers see the point faster.

Claude Code’s `/insights` command is not magic; it is a pipeline of session filtering, metadata extraction, LLM analysis, and HTML reporting.

Anthropic’s subscription rules are confusing enough that developers need a map of where Claude can and cannot be used.

A month inside Fizzy turned open source code, APIs, webhooks, and AI agents into a whole toolbox of experiments.

Fizzy’s PRs reveal the architecture lessons, code review habits, and contributor specialties hidden behind the final product.

Booting old Fizzy commits one day at a time turns 18 months of interface decisions into a literal design flipbook.

Campfire, Writebook, and Fizzy show that modern vanilla CSS can power serious apps without Sass, PostCSS, or a build step.

Fizzy’s 8,152 commits read like a product documentary, from Splats on a windshield to a finished 37signals issue tracker.

Fizzy’s webhooks unlock dashboards, digests, SLA alerts, stakeholder reports, and plenty of useful automation around your cards.

A tiny Claude Code skill makes Mermaid diagrams prove they render before the agent calls the docs done.

Sonic felt like Sonnet at triple speed, with a huge context window and enough Rails competence to demand attention.

A day on Opus and a day on Sonnet suggested the cheaper model may be good enough for most hands-on Claude Code work.

Claude Code’s in-session survey interruption is a reminder that paid developer tools should ask for feedback without hijacking flow.

A $200 coding assistant only has to save two developer hours a month before the economics get awkward for skeptics.

Context7 gives coding agents fresh, version-specific docs before they hallucinate yesterday’s API into your app.

A CleanShot-style Omarchy recording setup with region capture, audio, compression, clipboard copy, and a red recording dot.

Let the AI crows eat the CRUD work so humans can chase the harder, stranger, more valuable problems.

Mac switchers can make Omarchy render Apple-style system fonts with a few copied files and fontconfig aliases.

A custom Claude Code `/quiz` command turns each coding session into a quick check that you actually learned something.

A clean codebase turns AI agents into multipliers; a tangled one turns them into very fast guessers.

The danger is not using AI; it is using AI with so little friction that your brain quietly leaves the room.

AI workflow experiments deserve curiosity before dunking, because today’s weird loop might be tomorrow’s normal development practice.

A 60-second PR screencast proves the feature works and often reveals the rough edges tests did not catch.

The Rails path to Tailwind 4 is mostly smooth, but the upgrade tool leaves a few package-manager footprints behind.

If your brand color is `green-500`, every Tailwind palette change can redesign your button without asking.

Solid Queue can replace Redis cleanly if Capistrano and systemd know how to restart it during deploys.

A private GitHub Action can turn ONCE Campfire’s source ZIP into daily commits and readable diffs.

Rails browser guards are useful until your own mobile emulator gets blocked by the default modern-browser rules.

A Rails 7.1 upgrade quadrupled Heroku memory because Puma quietly started using every reported core.

Production-only Action Mailbox failures are easier to fix when you replay the raw email locally and reroute the broken ones.

For developers, writing is not content marketing; it is thinking, persuading, documenting, and working better asynchronously.

Raycast becomes a developer superpower when it can search Tailwind and DevDocs without breaking flow.

The Rails links worth keeping close because they answer questions faster than memory does.

A short screencast walkthrough for installing Ruby 3.1 with asdf.

Rails 7 dropped the old webpacker clue Heroku used, so Yarn only appears if you add the Node buildpack yourself.

A `.railsrc` file turns every new Rails app into your preferred stack before you write a line of code.

The tiny command-line incantation that gets Ruby 2.6.7 compiling on macOS Big Sur with asdf.

One `setup-node` setting can save a legacy GitHub Actions build from using the wrong Node version.

Chrome DevTools can catch the exact JavaScript line that secretly mutates your DOM.

Rails runs `after_commit` and `after_rollback` callbacks in reverse order, which is exactly the kind of detail that bites later.

A five-minute morning huddle can do more for a team than another strategy deck ever will.

Every “we might need this later” line of code is a tiny tax on today’s feature.

The next feature should not be the easiest one; it should be the one that moves the business goal.

A stubborn bug became a lesson in pairing, documentation, onboarding, and why pride is expensive.

Your business looks more alive with an imperfect post than with a perfect draft nobody ever sees.

The inbox wins when it controls your attention, so this is a simple system for taking that control back.

Leaving a good career for the work you cannot stop thinking about is terrifying—and sometimes exactly right.

Print design only has to look good; web and product design have to survive contact with actual use.

Market share can tell you what sold, but it cannot tell you what is actually better to use.

Testing feels slow at first, right up until it becomes the thing that stops every change from feeling dangerous.

One broken IE7 login proved the hard way that your test suite is only as good as your knowledge of real customers.

A website is never really finished; launch-and-leave is how your online storefront turns into a digital wasteland.