Last month I started this experiment as a way to pull the things Omedians actually share into something more permanent than the Slack scroll. I'm doing it again.
Agents Become a Discipline
Thoughtworks' Structured Prompt-Driven Development, published on Martin Fowler's website at the very end of the month. I also shared it on LinkedIn and I'll repeat that here. It is how a serious engineering team moves past "vibing" with an assistant and starts treating prompts as governed, version-controlled, integrated artifacts of the source.
The companion reads from April reinforce the same idea — that an "agent" is a buildable, inspectable thing, not a magic box. Giorgi Gagoshidze shared two of the most useful pieces:
- How to Build an Agent on ampcode. If you've never sat down and written your own coding agent loop end-to-end, this is the cleanest walkthrough.
- The companion piece Building Syntaqlite AI, which lands on a line worth printing out: "If you rely on it for the 'soul' of your software, you'll just end up hitting a wall faster than you ever have before."
Around the same axis: open-agents.dev, Anthropic's new Claude Code Routines docs, Cloudflare's Artifacts: Git for Agents (beta), the visual decoder Claude Code Unpacked, and Alejandro Balderas' fantastic claude-code-from-source — a reverse-engineered annotated read of how Claude Code actually works. As a sanity check on the broader ecosystem, Mateu Aguiló-Bosch's note on the two pillars of code generation, and the cheeky isitagentready.com, which you should bookmark and check when a vendor swears their API is "agent ready".
For balance, Adam Jacob's You Still Have to Refactor Even With AI is a gentle reminder that none of this exempts you from the engineering you were avoiding before.
Wired reported that Mozilla used Anthropic's Mythos to find 271 bugs in Firefox 🎉🦊
But, April was also the month Anthropic published their April 23 postmortem. Worth reading in full. Everyone has a bad day; the difference is whether you publish your wiring diagram afterwards. Apple's research team contributed Embarrassingly Simple Self-Distillation Improves Code Generation, IBM dropped Granite 4.1 — an 8B model holding its own against 32B MoE, and Anthropic's research on emotion concepts and function in language models generated the funniest #feed thread of the month — Ilya proposed that the new official guideline for the start of every workday should be "Good morning, GPT… I appreciate everything you do for us…" :))
The Claude Code "leak", incidentally, caused more shrugs than panic among us. The magic isn't in any single piece of source.
The Slow Exodus from US Big Tech
For a long time the conversation around "leaving GitHub" was theoretical. April made it specific. The bookend was Mitchell Hashimoto's Ghostty Leaving GitHub. The post is calm, well-argued, and treats the move as engineering rather than protest.
Around the same axis:
- France's government Linux desktop plan as the Windows exit officially begins.
- The Netherlands' soft launch of a government open-source code platform.
- only-eu.eu — a Show HN-style index of European alternatives to Google, Apple, Dropbox and 120 other US apps.
- And, as a striking counter-emotional beat, Apple's "Community Letter from Tim", which got the rare ❤️ + 🥺 reaction combo. Whatever else is happening, the center of gravity in this conversation is shifting.
Read together, these are not isolated stories. They are a market signal: enough teams now believe the cost of staying on a single American hyperscaler ecosystem exceeds the cost of leaving it.
A Fresh WordPress Fight
In the middle of all this, Cloudflare quietly dropped Emdash, positioned as "the next WordPress." It's an aggressive opening shot — a fully serverless, edge-native CMS, with all the obvious Cloudflare integrations baked in — and the first credible challenger to the WP/Drupal/Sanity tier in some time.
Matt Mullenweg's response was calm and adequate. Matt's core point still rings true: you can run WordPress on a Raspberry Pi, and a serverless stack isn't always the answer to a problem you don't have. WordPress's gravity comes from how cheap and forgiving it is at the bottom of the market, and Emdash isn't going to compete there. It's a different argument — about whether the top of the WP market still has a defensible story.
Read alongside Marcin Dudek's pointed WordPress Manifesto and the picture for the WP ecosystem is the most interesting it has been in years. Whoever wins the argument, it's good for everyone in the CMS world that the argument is back.
Two Pieces From Omedians
We had two of our own articles published this month.
Temuri Takalandze wrote Nginx Ingress Is Dead: Your Complete Guide to What Comes Next. The standard ingress-nginx controller has reached end-of-life, and Temo's piece is exactly the migration roadmap you want — why this happened, how the modern Gateway API differs, and which controllers are actually production-grade replacements. If you operate Kubernetes anywhere, this is required reading.
Nikoloz Gagua followed with Angular Signals: The Complete Guide to Modern Reactive State Management. A clear walkthrough of signal(), computed(), effect(), modern component communication patterns, and the practical bridges (and tensions) with RxJS. If you've been postponing the move to signals, this is a good push.
Also on Our Radar
A grab bag of links that did not warrant a section but earned their place this month.
- mherchel/ddev-drupal-admin-vrt — a clean DDEV add-on for visual-regression-testing the Drupal admin UI. The kind of small, sharp tool that pays for itself the first time it catches a regression.
- camoa/claude-skills — a starter set of skills, components and agents for Drupal (and beyond). Worth a fork.
- Mitchell Hashimoto: The Building Block Economy — the second-best Mitchell post of the month.
- @cloudflare on agentic crawl + Code Mode — an extension of the trajectory we covered in March.
- Statecharts.dev — hierarchical state machines, the proper way.
- Category Theory Illustrated – Orders — patient, beautifully explained.
- Laws of Software Engineering — appeared twice in #feed in three days, which is how you know it landed.
- Rob Pike-flavoured PSA from Mikheil Tchelidze: YouTube finally added a Short feed limit under Settings → Time Management. He recommends 0 minutes. So do I.
- Filing the corners off my MacBooks — April's most aggressively un-AI link, and a delight.
- Socket Security on a fresh npm malware wave — and Kapo's reply that Deno's permission system is starting to look attractive, immediately countered by the inevitable "yes, but a Deno project once hung 25 minutes on
install." - GitHub fake-stars investigation — an industry we did not need but now have.
- The threat is comfortable drift toward not understanding what you're doing — a line that should be on a poster.
- Pgbackrest is no longer being maintained — if you rely on it, plan accordingly.
- DaVinci Resolve – Photo — Blackmagic taking a swing at Lightroom. Reasonable opening offer.
- Localsend — open-source AirDrop. We use it.
- Archive of Byte magazine, issue #1 from 1975 — go forth and enjoy.
- @claudeai on a new design model — which produced a fourteen-reply thread in #feed that ended, perfectly, with Tekla's demoing before/after of an Angular UI rebuilt entirely from a screenshot. RIP designers? Probably not. RIP design fees? Maybe.
This is what Omedians actually read, watched, shared and discussed in April. Not everything that happened. Just what made it through our prism.