Brian Scanlan

@DanielLockyer perl remains undefeated 💪🐪

Nice, now PHP is being attacked

When @darraghcurran @brian_scanlan @clairevo and @gregolsent ran a webinar on our @fin_ai 2X productivity journey, the Q&A cup ranneth over. So they answered all 72 questions you had & here they are. It may be the longest blog post ever published in @intercom / @fin_ai history.

@DanielLockyer You should see the S3 utilisation graphs every day/hour/minute boundary :)

Pro tip: if you've got some sort of cron job executed by many services, add jitter to the start time "Every 5 minutes" seems OK until you're absolutely nuking your DB/backend/API providers It also makes autoscaling harder due to spiky traffic patterns

@brian_scanlan Did you just say the quiet part out loud? That's not just a post. It is a rallying cry for our generation, Brian.

@brian_scanlan User asked for some ideas to brainstorm. I'll search the context available in local files, so I give them a sharp list of actionable products, not a generic list of ideas.

That is a genuinely game-changing opinion. Let's work together to figure out next steps. Should I proceed to brain-storm some options, or do you have other ideas in mind?

This is one of my favorite eng acceleration stories and I’m so psyched to talk tomorrow AM with the team that pulled it off. Come hang! 👇

Most engineering orgs are experimenting with AI. We bet the entire company on it, and hit our 2x productivity goal 3 months early. Join us on May 19 for a live session where Fin CTO @darraghcurran, Principal Engineers @brian_scanlan and Kesha Mykhailov, and special guest @clairevo break down how Fin’s ~500-person R&D org: • Shifted to agent-first engineering • Got 95% of PRs running through Claude Code • Cut defects by 55% • Shipped 2x more product changes at nearly half the cycle time You'll hear about the messy middle nobody talks about – uneven adoption, code quality dips, the human bottlenecks that mattered more than the technical ones, and what they'd do differently. Register at the link in the replies.

Register here: intercom.registration.goldcast.io/webinar/67c1ea…

We're going to spill all the beans next week. Myself and @darraghcurran (and some special guests!) are doing a webinar about our use of AI and how we 2x'ed R&D at Intercom. We'll be going deeper than we've ever gone before :) - link in the comments, as is tradition.

@BeatrizGietner @TheStalwart @UlyssesInc @Willob yes

@TheStalwart joe you need to be bullish on @UlyssesInc get @Willob on the pod

NEW ODD LOTS: A massively underdiscussed element of the modern economy @tracyalloway and I talk to @samanth_s about the extraordinary complex of undersea cables that keep the internet alive open.spotify.com/episode/724d6A…

@bigmonsterlove I like to think that it's not a coincidence that both myself and our CEO are from County Fingal.

Excited to announce my new role. Looking forward to the future!

I keep thinking about @brian_scanlan's words at the last #SFRuby that the unlock isn't the model or the harness: it's everything you bring to it. All the context, the local knowledge, all of the environment-specific stuff. – We saw this with Fin: all of the improvements we got in resolution rates weren't down to the models just getting better every few months. It was about all of the work to make sure you're feeding the right information to the models, to do the right work at the right time. You want the compounding benefits of a well-designed platform. It doesn't matter which tool — you can pick any of them, just pick one. Watch: #meetups" target="_blank" rel="nofollow noopener">sfruby.com/videos/#meetups

I *feel* this awesome blog post about operations.

youtube.com/watch?v=sPNUo9… It's a very fun talk!

If you are interested in learning how to teach an LLM to review code like a senior engineer, I strongly recommend watching this video from my colleague @gregolsent (link in thread)

There is, of course, one AI Agent for Customer Support with public docs, self serve sign-up, public pricing, a CLI, API + more. It's the highest performing one, and we share all our ideas+research too. Product → fin .ai Research → fin .ai/research Ideas → ideas.fin .ai

@mitsuhiko DNSSEC: Pointlessly replacing a minor security concern with a massive availability risk since 2004.

Now that we know it's terrible, can we finally kill DNSSEC?

@Jasonpraful @sama So fun

I like the new @sama