Dr Claire
banner
krider2010.bsky.social
Dr Claire
@krider2010.bsky.social
Engineering leadership (VP Engineering), startups, tech addict, Evertonian, powerlifter, cats. Co-founder & CTO of Sailhouse. Berkshire πŸ‡¬πŸ‡§.
Reposted by Dr Claire
Join Dana Lawson (Netlify), @danielleleong.com (FireHydrant), and @krider2010.bsky.social (Sailhouse) as they unpack what AI really means for developers today.

Learn how to stay creative, productive, and in control of your code in the AI-augmented era.

πŸ—“οΈ Nov 19
πŸ”— www.netlify.com/webinars/ai-...
November 6, 2025 at 7:29 PM
Very much looking forward to this! Sign up link in the thread.
AI’s already in your workflow. The real question is how do you keep your code clean and your sanity intact?

Join Dana Lawson (Netlify), @danielleleong.com (FireHydrant), and @krider2010.bsky.social (Sailhouse) for a candid chat on code quality, career shifts, and staying human while coding with AI.
October 28, 2025 at 5:56 PM
A couple of Negronis and some goldfish crackers. How’s your Sunday afternoon going?

(For the tech hustlers, I already used some AI tooling this morning - the afternoon is for relaxing πŸ˜‰)
October 5, 2025 at 3:34 PM
LLMs aren’t APIs. You call, you get 200 and vibes. With GPT-5, prompts that worked yesterday may fail today; without you touching code. Models drift. Users blame you. Build for it.
August 8, 2025 at 4:36 PM
Everyone’s trying to build the optimal AI workflow.

Agent infra, eval loops, prompt specs, all wired up before anything works.

Using coding assistants is either wild west or over-specced.

Try things first. Optimise later.
August 5, 2025 at 3:26 PM
Reposted by Dr Claire
Engineering is the intersection of Curiosity and Capability

When your curiosity outstrips your capability, you expand your capability and grow

When your capability expands, it allows you to see farther and grows your curiosity

Don't allow your tools take away both your Curiosity and Capability
August 3, 2025 at 3:43 AM
Everyone thinks AI means fewer engineers. But building secure, resilient systems is still hard. AI gives you leverage. Got a 10% output boost? Use it to build better, ship faster, explore more. Replace waste; not talent!
August 2, 2025 at 7:10 PM
Don’t forget all the nuances and human quirks! But also that makes it interesting. No one team or org is the same.
July 28, 2025 at 5:03 PM
"You're absolutely right".

I mean it's nice to hear that. But I kinda wish I wasn't so right and didn't need to make these corrections 🀣 Thanks Claude Code!
July 19, 2025 at 2:26 PM
Debugging async systems feels like ghost hunting. Logs say it ran. Retries say it didn’t. The agent? Forgot the plan halfway through.

You’re stuck piecing together timelines like a true crime board. And half the time, you still don’t know what happened.

What’s your move when async goes sideways?
July 1, 2025 at 6:41 PM
Vibe reply-guys
June 26, 2025 at 4:54 PM
β€œYour agent doesn’t need memory.”

Cool.

Why is it fixing and breaking the same file 3 times in a row?

What’s the weirdest state bug you’ve hit in an AI system?
June 25, 2025 at 3:33 PM
Glue code is never on the roadmap. But it always shows up.

And if you ignore it long enough… it ends up running your system.

What’s the glue you forgot was critical?
June 20, 2025 at 6:49 PM
A very good question! Did you get to go? I have FOMO.
June 12, 2025 at 8:21 PM
No standups. No tickets for tickets. No β€œplease justify this $12 tool.”

Just two people building the thing they wish already existed.

What would you nuke from your team’s process if you could?
June 12, 2025 at 7:07 PM
Reposted by Dr Claire
Most event systems were designed for a time when β€œreal-time” meant β€œsometime this hour.” Now your agents are spinning off retries, branches, fallback calls, and memory loops.

We wrote about why that’s breaking things, and how to fix it without crying: sailhouse.dev/blog/event-i...
Event Infrastructure for Modern Systems
AI-native apps generate 50x more events β€” but most teams are still relying on brittle, legacy infra. Here’s how to modernize your event backbone without breaking everything.
sailhouse.dev
June 11, 2025 at 5:55 PM
Correctness is a nice to have at the moment 😳
June 7, 2025 at 2:12 PM
Not every event-based system needs a streaming platform.

Kafka’s great if you’ve got a team.

Most of us? We just want something that works, retries, and doesn’t explode in prod. What do you use?
June 6, 2025 at 1:21 PM
Done well it can accelerate with aligned handoff. Back in the day, I left PRs for colleagues to review while I was offline. If something shipped product reviewed. Next day I picked up review fixes/merges. Jumped on prod feedback, reviewed things left for me. Rinse & repeat. We overlapped 4 hrs IIRC.
June 1, 2025 at 12:11 PM
Leading teams teaches you new pain:

- Tech debt as strategy
- COGS lurking behind every infra choice
- Simplicity beats perfect

What’s the leadership lesson you wish you’d learned sooner?
May 27, 2025 at 6:38 PM
Bank holiday Monday. Drinking a very nice Marzen while working on marketing things for @sailhouse.dev . I know how to have a good time 🀣
May 26, 2025 at 12:34 PM
Retries aren’t free.

Naive retries = failure cascades, duplicated requests, hidden bugs.

Retries baked into infra = graceful failure, predictable outcomes.

Been bitten by retries in production? Tell me your story.
May 20, 2025 at 6:50 PM
Distributed monoliths: shiny microservices outside, shared DB and deploy pain inside. Infra should be leverage.

Been there? Tell me your best "this was totally decoupled, I swear" story.
May 14, 2025 at 1:31 PM
You know you love it! Also thank you. Or is it because you need me to ship a preview and not break prod? πŸ˜‚
May 7, 2025 at 7:56 PM
That was one I got today!
May 3, 2025 at 6:28 PM