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-...
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
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-...
Learn how to stay creative, productive, and in control of your code in the AI-augmented era.
🗓️ Nov 19
🔗 www.netlify.com/webinars/ai-...
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.
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
Very much looking forward to this! Sign up link in the thread.
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 😉)
(For the tech hustlers, I already used some AI tooling this morning - the afternoon is for relaxing 😉)
October 5, 2025 at 3:34 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 😉)
(For the tech hustlers, I already used some AI tooling this morning - the afternoon is for relaxing 😉)
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
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.
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.
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
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.
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.
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
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
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
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
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
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!
"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!
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
"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!
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!
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?
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
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?
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?
“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?
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
“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?
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?
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?
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
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?
And if you ignore it long enough… it ends up running your system.
What’s the glue you forgot was critical?
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?
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
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?
Just two people building the thing they wish already existed.
What would you nuke from your team’s process if you could?
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...
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
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...
We wrote about why that’s breaking things, and how to fix it without crying: sailhouse.dev/blog/event-i...
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?
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
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?
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?
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?
- 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
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?
- Tech debt as strategy
- COGS lurking behind every infra choice
- Simplicity beats perfect
What’s the leadership lesson you wish you’d learned sooner?
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
Bank holiday Monday. Drinking a very nice Marzen while working on marketing things for @sailhouse.dev . I know how to have a good time 🤣
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.
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
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.
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.
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.
Been there? Tell me your best "this was totally decoupled, I swear" story.
May 14, 2025 at 1:31 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.
Been there? Tell me your best "this was totally decoupled, I swear" story.
I am reminded once again how easily even cursor code can get distracted and just want to complete tasks and stub random things out rather than doing a great job. Perhaps we are closer to the average programmer AGI than we realise 😂
May 3, 2025 at 11:34 AM
I am reminded once again how easily even cursor code can get distracted and just want to complete tasks and stub random things out rather than doing a great job. Perhaps we are closer to the average programmer AGI than we realise 😂
Reposted by Dr Claire
I had a clear out today.
Here are two lots of books. I'm giving them away for free, cos I want to.
The first pic to a primary school.
The second pic to a secondary school.
If you'd like them for your school get in touch. I'll choose the schools tomorrow
UK only
PLEASE SHARE
Here are two lots of books. I'm giving them away for free, cos I want to.
The first pic to a primary school.
The second pic to a secondary school.
If you'd like them for your school get in touch. I'll choose the schools tomorrow
UK only
PLEASE SHARE
April 28, 2025 at 5:08 PM
I had a clear out today.
Here are two lots of books. I'm giving them away for free, cos I want to.
The first pic to a primary school.
The second pic to a secondary school.
If you'd like them for your school get in touch. I'll choose the schools tomorrow
UK only
PLEASE SHARE
Here are two lots of books. I'm giving them away for free, cos I want to.
The first pic to a primary school.
The second pic to a secondary school.
If you'd like them for your school get in touch. I'll choose the schools tomorrow
UK only
PLEASE SHARE
Reposted by Dr Claire
"It would be [safe], if I was running flyctl in an isolated environment and not on my local machine." Our MCP experiment shows both the power and security considerations of connecting AI to infrastructure tools 🌐
🔗 ➡️ fly.io/blog/30-minu...
🔗 ➡️ fly.io/blog/30-minu...
April 11, 2025 at 6:25 PM
"It would be [safe], if I was running flyctl in an isolated environment and not on my local machine." Our MCP experiment shows both the power and security considerations of connecting AI to infrastructure tools 🌐
🔗 ➡️ fly.io/blog/30-minu...
🔗 ➡️ fly.io/blog/30-minu...
America finally broke me. Home after ten days there and at a meal out this evening at a UK food pub. Service? What what feckin service?
April 11, 2025 at 5:52 PM
America finally broke me. Home after ten days there and at a meal out this evening at a UK food pub. Service? What what feckin service?
People watching is so fascinating!
April 5, 2025 at 11:23 PM
People watching is so fascinating!
Any suggestions as to what I should vibe code on this trans atlantic flight?
April 1, 2025 at 10:12 AM
Any suggestions as to what I should vibe code on this trans atlantic flight?
What I love most is how this demonstrates the power of composable, open tools. @sailhouse.dev + @netlify.com + @resend.com = a solution that would've taken weeks to build from scratch just a few years ago.
Fun fact: I broke our own event system while building this :disappear:
Fun fact: I broke our own event system while building this :disappear:
We built an open-source email confirmation system! It uses event-driven architecture via @sailhouse.dev , runs on @netlify.com Functions, sends emails via @resend.com, & requires zero database setup.
Classic "I'll save time in the long run" developer move, right? 🙃
sailhouse.dev/blog/email-c...
Classic "I'll save time in the long run" developer move, right? 🙃
sailhouse.dev/blog/email-c...
Building an Email Confirmation Flow with Sailhouse, Netlify, and Resend
A ready-to-deploy, event-driven email confirmation system built with Sailhouse, Netlify, and Resend that you can set up in minutes and customize to your needs.
sailhouse.dev
March 28, 2025 at 4:37 PM
What I love most is how this demonstrates the power of composable, open tools. @sailhouse.dev + @netlify.com + @resend.com = a solution that would've taken weeks to build from scratch just a few years ago.
Fun fact: I broke our own event system while building this :disappear:
Fun fact: I broke our own event system while building this :disappear: