Dr Claire

Dr Claire

@krider2010.bsky.social

Engineering leadership (VP Engineering), startups, tech addict, Evertonian, powerlifter, cats. Co-founder & CTO of Sailhouse. Berkshire 🇬🇧.

806 followers1K following243 posts

Very much looking forward to this! Sign up link in the thread.

Netlify@netlify.com

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.

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 😉)

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.

Dr Claire reposted

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

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!

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?

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?

Dr Claire reposted

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...

sailhouse.devEvent Infrastructure for Modern SystemsAI-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.

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?

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?

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.

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.

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 😂

Dr Claire reposted

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

Dr Claire reposted

"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...

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:

Sailhouse@sailhouse.dev

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...

I wanted to share this for those of you who don't yet know about @codetv.dev (where have you been?!) Jason produces fun, engaging, and educational content. With added 🌶️ (quite literally). I'm a big fan and would love more of you to know about and watch this content.

Jason Lengstorf@jason.energy

okay, announcement time! as of this week, Learn With Jason (the company) has officially rebranded – we're @codetv.dev now! - CodeTV refocuses on what we produce (vs centering on me) - we now have the option to become a supporter to get early access: codetv.dev/support more to come. stay tuned!

Dr Claire reposted

💼 Hiring Update👩‍💼 One of my amazing engineers is transitioning to being an Engineering Manager! This leaves an opening for a Senior Backend Java Engineer on my team. The role isn't open quite yet, but I want to get the ball rolling. Descriptions below, please drop your LinkedIn links 🙌

Dr Claire reposted

and that also means: devs! if you want to be in an episode of Web Dev Challenge, sign up for my newsletter and I’ll send out a casting call soon 👀 codetv.dev/newsletter

codetv.devNew CodeTV releases and more delivered to your inboxLearn from experts. Build something new. Grow your career. The web is more fun with friends; let’s stick together.
Jason Lengstorf@jason.energy

hey dev tools companies! I am actively booking season 2 of Web Dev Challenge and I want to work with you. we’ll pick a use case and get devs to build an app using your tool — then we’ll open up the challenge to the community for fun & prizes! limited spots available — hit me up at info@codetv.dev

More @bolt.new explorations this weekend. It wrote a @netlify.com function correct first time with a dependency to call an external service! 🤯 Messing around with ideas feels fun again. OK, so it didn't run correctly when first deployed as I'd not set up the third party quite right but that was me🤣

Dr Claire reposted

Replying to @kaelig.fr

Continuing on my path to making the web better, I’m now looking for an organization who needs help operationalizing excellence in frontend and product design so we can ship world-class experiences together 🚀

Well that’s a new one… Just got a LinkedIn message complaining to me about Notion bugs. Somewhere I’ve never worked. Nor do I talk about on LinkedIn 😵‍💫 From a security person trying to sell to me. Clearly not good at using their hax0r skills to figure out who to contact 🤣