Matt Brown

@mattbrowndev
413 Followers
387 Following
78 Posts
I write developer tooling at Slack. I used to work at Vimeo, where I made @psalm
LocationBrooklyn NY
Webhttps://mattbrown.dev
This is where LLMs have been most useful at work: making projects that required a lot of boring manual labour suddenly viable

I created two PHP sites in 2011 that are still going, 15 years later. Code that got the job done but was terribly-written. Yesterday I spent a couple of hours with Claude, which modernised the code and eliminated a few egregious vulnerabilities. Some things broke in the migration and optimisation, but they were easy to fix.

It wasn’t worth my time to do this work myself, and paves the way to move a bunch of sites (including psalm.dev) off a $1,000/year server to something much cheaper.

One unambiguously good thing PHP project could would be to port the parser to Rust, which would unlock the potential for lightning-fast static analysis. Right now anyone venturing into a PHP-specific compiled language tooling has to also write and maintain their own parser, which is out of reach of basically everyone except JetBrains.

Announcing the official, hyperoptimized Psalm docker image, +50% faster than Psalm on normal PHP!

I've also contributed the underlying deepbind patch to upstream PHP, and it will be available for everyone to use in PHP 8.5 (or right now, if you're using the Psalm docker image)!

https://blog.daniil.it/2025/07/10/official-psalm-docker-image/

Official Psalm docker image - Daniil Gentili's blog

Announcing the official hyperoptimized docker image for Psalm, a powerful PHP Static analysis tool.

Daniil Gentili's blog
The speed at which I reversed my car when I saw these ladies modding their yard sign
Finally nuked my Twitter/X account. Lots of happy memories from a previous existence on Twitter, but the recent hard-right turn into a monumental pile of shit has been impossible to stomach. It has no value anymore. Sad!
Wow, this vector shooter is beautifully made https://pixeljamarcade.com/game/utopia-must-fall/
V99

(I work at Slack, opinions my own) A bunch of people are sharing viral social media posts saying that we train LLMs on customer data. It's a story that slots neatly into the hype/doom narrative around AI.

But it's not true — we even wrote a whole blog post about it last month: https://slack.engineering/how-we-built-slack-ai-to-be-secure-and-private/

Not discounting the other concerns around LLMs (e.g. hallucinations, environmental impact) that are totally legitimate.

cc @sebastian @derickr

How We Built Slack AI To Be Secure and Private - Slack Engineering

At Slack, we’ve long been conservative technologists. In other words, when we invest in leveraging a new category of infrastructure, we do it rigorously. We’ve done this since we debuted machine learning-powered features in 2016, and we’ve developed a robust process and skilled team in the space. Despite that, over the past year we’ve been …

Slack Engineering
Ithaca *is* gorges
Meta introductory post: over the weekend I switched to the largest Mastodon instance because I wanted more accurate Like counts. Like counts are not federated in Mastodon by design (https://github.com/mastodon/mastodon/issues/11339#issuecomment-518029618). The net result is that instances with vastly more users show more accurate like counts than instances with few users. I’m still happily paying for phpc.social because it’s an important community resource.
Properly federate "like" objects · Issue #11339 · mastodon/mastodon

Pitch Incoming like objects are applied to posts, and posts are fetched for newly seen ones (similar to how announce objects are handled. Any generated like objects are federated to all followers (...

GitHub