Modern CSS • Web Platform APIs • Rails + SQLite
Berlin, Germany
Joined March 2013
- Tweets8.3K
- Following1.4K
- Followers4.6K
- Likes15.8K
Stephen Margheim retweeted
We wondered if handing over stablecoins could feel as elegant as handing over cash.
It now happens ~4,000 times per week on ZAR.
Type the amount, digital cash appears on screen, receiver scans to claim it.
The merchant never needed to know your account number.
Stephen Margheim retweeted
Inspired by @fractaledmind’s berlin.rb talk, I wrote judgelint, a tool that lets you express nuanced project rules, and have a system one model (like Jev) judge whether your code complies with it. The goal was something fast and cheap enough to run as part of CI, and integrate nicely into GitHub.
Give it a try! github.com/jpcamara/judgelin…
Jev is the default, but it supports lots of others (like clef and the OpenAI decisions api). Doesn’t support local models atm, but happy to take a PR for it!
Stephen Margheim retweeted
In the year 2000 I joined the original eXtreme Programming (XP) mailing list. At work we had pairing stations and we wrote our tests first. I founded the Atlanta XP User Group. And I've never stopped being a fan, even over 25 years later.
Coding agents broke most of XP's assumptions, but a few of its rules matter more than ever.
Impatient Programming is XP fully revisited: 29 guidelines for building software with agents, each set next to the XP rule it replaces, based on how we build software at ZAR, where I serve as CTO.
Learn more here: impatientprogramming.org
What else is there:
- essays from people who disagree with some of the rules
- the guardrail tools we built to enforce them
- a directory of 539 more tools, sorted by tech stack
Think a rule is wrong? Write up your opinion and we'll publish it.
Stephen Margheim retweeted
Hello, Ruby world! 👋💎
New account, new city, same Ruby spirit!
After five editions in Poland, Ruby Community Conference is heading to Berlin! 🇩🇪
📅 March 12, 2027
Follow us for all things RCC 2027. This is just the beginning! 🚀
rubycommunityconference.com/
Stephen Margheim retweeted
If you're a software engineer, this is a MUST watch. @fractaledmind, Leading all Product Engineering at @zardotapp, gives the best articulation of how to reasonably apply AI to software development that I've heard yet. I've seen first hand how incredibly well this all works in practice 👏
youtu.be/OmrdvAzCSIc?si=L5Sp…
Stephen Margheim retweeted
Dang, this is _really_ good. Great job @fractaledmind. Required watching!
If you're a software engineer, this is a MUST watch. @fractaledmind, Leading all Product Engineering at @zardotapp, gives the best articulation of how to reasonably apply AI to software development that I've heard yet. I've seen first hand how incredibly well this all works in practice 👏
youtu.be/OmrdvAzCSIc?si=L5Sp…
Agents are better than us at rolling out changes slowly and safely. They don't get bored, don't get impatient, and don't skip the check on a Friday afternoon.
What's stopping you from letting them?
The three layers I want every change to climb:
1. A preview environment of its own
2. Pre-production: a full mirror of prod, employees only
3. Production for everyone
An agent watches each step and promotes the change or pulls it back.
When teams get nervous about AI-written code, they add gates to the rollout: more approvals, more manual QA, more humans holding the switch.
That buys a little safety at the cost of exactly the speed you were after.
Guard the code, not the rollout.
Keep the codebase coherent with deterministic checks. Then let agents roll changes out slowly, watch everything, and promote or pull back on their own.
Reading code used to be how we gained confidence in it. I barely read the code I ship now, and I'm more confident than ever.
If confidence doesn't come from reading code anymore, where does yours come from?
Everyone's racing to build a software factory. I'm building a software foreman.
Which would you rather have watching production at 3am?
Three things an always-on AI "foreman" catches that your exception tracker never will:
• a provider quietly changing its response shape
• activity drifting outside its normal range
• an integration going down without raising a single exception
Stephen Margheim retweeted
Back on the mic with @fractaledmind covering why code is cheap but still matters, why software foremans beat factories, and deep breathing exercises for your agents
yagni.fm/episodes/i-need-a-s…
