Tag · 6 posts
open-source
-
Engineering 5 min
Paid For, Then Published: How We Release Open SourceMost of the open source we release starts as a feature a client project needed and paid for. We ship it in small, frequent releases under semantic versioning, so older projects stay on the version they were built on and upgrade when they choose. Why that works, and where it bends.
-
FlowDrop 12 min
FlowDrop Workflow Specification 1.0: Why a Workflow Engine Needs a SpecFlowDrop now has a published, implementation-independent workflow specification: 386 rules with permanent identifiers, conformance fixtures, and a clear answer to absent versus null in JSON. Why we pulled the rules out of the Drupal module, and what a written spec fixes that a test suite cannot.
-
Engineering 14 min
The Upgrade Path Is a Product DecisionAtelier is built for people who have never heard of Drupal and will never open a terminal. That single fact turns 'it upgrades itself' into a veto over the dependency list — and a refactor where I had to say no to modules we wanted, delete code we were proud of, and start reading other people's roadmaps.
-
Musing 1 min
The Bet Ships: Atelier Is LiveA few weeks ago I wrote that I was betting a new product on an unfashionable foundation. It just launched. This is the short, happy note before the longer ones.
-
Musing 5 min
Am I Building on Sand? Betting a New Product on an Unfashionable FoundationA reflection on whether it makes sense to build a brand-new product on a mature platform the hype cycle has moved past – and why the answer depends entirely on whether that platform is your audience or your engine.
-
Musing 2 min
Are Micro PHP Packages Becoming Obsolete in the AI Era?A reflection on how AI code generation is changing the value proposition of small, single-purpose open-source packages, and what that means for the future of the PHP ecosystem.