Benjamin Charity (@benjamincharity) header
Benjamin Charity (@benjamincharity) profile picture

🧑‍🚀 Building products and the teams that ship them. Founding engineer across SaaS, healthcare, and consumer tech.

Atlanta, GA
Joined March 2009
Photo by Benjamin Charity (@benjamincharity)Photo by Benjamin Charity (@benjamincharity)Photo by Benjamin Charity (@benjamincharity)Photo by Benjamin Charity (@benjamincharity)Photo by Benjamin Charity (@benjamincharity)Photo by Benjamin Charity (@benjamincharity)Photo by Benjamin Charity (@benjamincharity)Photo by Benjamin Charity (@benjamincharity)Photo by Benjamin Charity (@benjamincharity)Photo by Benjamin Charity (@benjamincharity)
Two writers append to the same audit chain at the same instant. Every row still verifies. You now have two histories, and no per-row check can say which one is real. Let one writer append at a time, or you don't have a chain. benjamincharity.com/articles…
8
New leader, burned engineering team: make your first visible fix the thing they've been asking for and been told no on. A technical fix the team requested is a kept promise, so it fixes the system and proves something about you at the same time. benjamincharity.com/articles…
8
An #AI #agent edits a patient record in March. The approval behind it was clicked in November. That's what a refresh token allows. Give each credential its own consent and expiry. Tie it to a shift. If it's minutes, people stop reading the prompts. benjamincharity.com/articles…
13
Your #scaling constraint isn't #headcount. It's how many people can take an idea all the way to done. Keith Rabois calls them barrels; most people are ammunition. Companies have far fewer barrels than they think, and waste the ones they have. benjamincharity.com/articles…
16
Startups reward rule-breakers. Regulated industries punish them. The transferable skill isn't breaking or following rules, it's telling soft rules from load-bearing ones, and treating the load-bearing ones as physics. benjamincharity.com/articles…
16
The bottleneck in software was never typing speed. It was judgment about what to build next. AI makes production cheap, not judgment better. For unknown problems, use code to learn. For known ones, spec-first still wins. The skill is telling them apart. benjamincharity.com/articles…
14
First engineer and third engineer: not the same hire, even with the same title. Hire #1: a generalist who thrives without structure. Hire #3: depth in a gap the team lacks. Swap them and both feel like bad hires. benjamincharity.com/articles…
12
Event-driven ≠ microservices. One is a design pattern. The other is a deployment decision. You can have decoupled domains, async queues, and webhook reliability inside a single codebase. New article on when that tradeoff is worth it (and when it isn’t): benjamincharity.com/articles…
1
8
Benjamin Charity retweeted
I'm excited to host the AI Leadership Exchange TOMORROW (June 12) in Chamblee, GA. We're bringing together engineering leaders from Grubhub, Pro-Vigil, Stax Payments, Revelation Pharma, and This Dot Labs for a candid discussion on AI adoption, developer productivity, and scaling AI across engineering organizations. Featuring - @BenjaminCharity — Director of Engineering, @RevPharma - Sameer Siddiqi — VP Quality Engineering, @StaxPayments - @ElliottFouts — CTO, @ThisDotLabs - Satish Raj — CTO, @Provigilcorp - @edsancha — Director of Engineering, Post Purchase & Care, @Grubhub - @robocell — VP of Innovation, @ThisDotLabs - @JonFontanez — #AI Engineering Lead, @ThisDotLabs If you're a CTO, CIO, or VP of Engineering and would like to join for panels and roundtables, email me at tracy@thisdot.co to request an invite. Learn more: thisdot.co/technology/ai-atl…
1
2
242
Benjamin Charity retweeted
With more than 15 years of experience across SaaS, healthcare, and regulated industries, @benjamincharity brings a unique perspective on building and scaling engineering organizations in complex environments. As Director of Engineering at @RevPharma, he's focused on growing engineering capabilities and helping drive the company's transformation into a technology-driven organization. Join us June 12 in Chamblee, GA as engineering leaders discuss AI adoption, developer productivity, and scaling new ways of working across their teams. CTOs, CIOs, and VPs of Engineering can request an invite at tracy@thisdot.co.
1
1
100
Your stack isn’t a personality trait. It’s a survival decision. Pick a default. Make exceptions rare, explicit, and funded. The novelty tax compounds: hiring, onboarding, review, tooling, on-call. benjamincharity.com/articles…
12
A rewrite can be the right call in a turnaround. It's just almost never the first move. The fix is a sequence: reduce uncertainty, remove drag, invest in leverage. The wins that rebuild trust are the boring ones. benjamincharity.com/articles…
13
Benjamin Charity retweeted
Thrilled to have @BenjaminCharity joining us as a speaker for the Leadership Exchange! Benjamin has spent the last 15 years building products and engineering organizations across SaaS, healthcare, and regulated industries, including helping scale startups through acquisition and growth. We’ll be talking candidly about moving AI tooling beyond experimentation and into reliable, measurable engineering workflows teams can actually operate at scale. If you're a CTO, CIO, or VP of Engineering in the Atlanta area, I'd love for you to join us for the AI Leadership Exchange on June 12th in Chamblee, GA. Reach out directly or email tracy@thisdot.co to request an invite. Learn more: thisdot.co/technology/ai-atl…
1
2
281
Early-stage technical decisions fail two ways: analyzing forever, or moving fast on something irreversible. The real skill isn’t picking right. It’s knowing which decisions deserve real deliberation and which just need a direction. benjamincharity.com/articles…
6