← Back to blogblog

The work you don't see (and why it makes Chat Thing better)

Chris

Chris

~ 2 min read


The work you don't see (and why it makes Chat Thing better)

Most of our blog posts are about shiny new things you can click on. This one's a bit different.. it's about the stuff happening quietly in the background that you'll never actually see. Stick with me though, because it matters more than you'd think.

This month we rebuilt the engine room of Chat Thing. Not the bit you log into, but the part doing all the heavy lifting behind the scenes.. crawling your website, syncing your content from Notion, Google Drive and the rest, generating your analytics, sending your emails, running your agents' tasks. All of that runs on a separate system, and we tore it down and rebuilt it from scratch.

I know, "we rebuilt some backend plumbing" isn't exactly a thrilling headline! But here's what it actually means for you.

Faster, in the way that counts

The honest truth is that the old system was built on different foundations to the rest of Chat Thing. It worked fine, but it meant our team had to juggle two completely different ways of doing things every time we wanted to improve anything back there.

Now it all speaks the same language. Which means we can ship improvements to crawling, syncing and analytics far quicker than before. When you're waiting on us to make something better, that speed is the difference between "next week" and "next month".

Safer with your data

This is the one I care most about, and it's worth a minute of your time.

Every modern app is built on top of hundreds of little bits of code written by other people. It's how software works, nobody builds everything from scratch. But every one of those bits is something you're trusting, and occasionally one of them gets tampered with by someone with bad intentions. It's called a supply chain attack, and it's one of the biggest security risks going right now.

So while we were in there, we did two things. We cut the amount of third party code this system relies on by nearly 40% (fewer moving parts, fewer things that can go wrong). And we turned on a much stricter set of rules for the code we do use.. including a deliberate cooling off period so we never automatically pull in brand new code before the wider security community has had a chance to vet it.

In plain English: there are now fewer doors, and the ones that remain have much better locks. Your data, and your customers' data, sits behind them.

More reliable, full stop

Fewer moving parts means fewer things that can break at 2am. We also did the whole switch over carefully, running the old and new systems side by side and checking they behaved identically before flipping the switch, with a one button rollback the whole time. No drama, no downtime, nothing for you to do.

Anyway! Your agents are crawling, syncing and replying exactly as they were before. Nothing's changed on your end. But the thing underneath is now faster for us to improve, leaner, and a good bit harder to attack.

The unglamorous work is usually the work that keeps everything else standing up.. and we're more than happy to keep doing it. :)

Related articles