
CTO @userscape - Personal site https://xitter.gq/t.co/K4bKjBs5zQ. Podcasting over at 🎤 https://xitter.gq/t.co/5kxK3n77JC
Montrose, CO
Joined December 2007
- Tweets3.5K
- Following344
- Followers377
- Likes411
Matt Stenson retweeted
The patch release should not be the blog post, it should be when everyone can actually download it. A blog post with no way to actually update is not ideal.
a weird inversion with LLMs is the models improve faster than the tinkerers
when i see people with custom workflows and setups they're all addressing problems that don't exist anymore
the person naively using vanilla codex is more likely to be experiencing state of the art
Matt Stenson retweeted
Home baking killed bakeries. Nespresso killed Starbucks. Packaged pasta killed Italian restaurants. Nail polish killed nail salons. AI killed SaaS.
Should I continue?
Matt Stenson retweeted
spent 5 days building semantic memory for @laravel Boost.
embeddings. search. all the fancy AI stuff.
then i deleted the whole thing because markdown + grep was better 😭
wrote about the entire saga here:
laravel.com/blog/semantic-me…
Matt Stenson retweeted
Just a reminder that this is the creep we're supporting by staying on this platform.
Matt Stenson retweeted
When customers request a feature, what they most want is a commitment: Yes, we'll do that! And that's the most tempting thing in the world to offer them. But you're better off saying THANK YOU and meaning it, without binding yourself to a specific solution.
Matt Stenson retweeted
Dookie DEMASTERED — this is incredible!
dookiedemastered.com/
Matt Stenson retweeted
We have been made aware that the Advanced Custom Fields plugin on the WordPress directory has been taken over by WordPress dot org.
A plugin under active development has never been unilaterally and forcibly taken away from its creator without consent in the 21 year history of WordPress.
Matt Stenson retweeted
Broadcasting that you've found a vulnerability before it's been fixed, even if you don't reveal what it is, isn't how responsible disclosure works folks. 🤦 😡
If anyone was left in any doubt that Automattic are working in bad faith to hurt WPE, this should remove all doubt.
This Post is from an account that no longer exists. Learn more
Matt Stenson retweeted
Average gen z founder:
"dawg i chatgpt'd the license... can't be bothered with legal"
Matt Stenson retweeted
Guzzle has two notable options you can access in Laravel's HTTP client via the `withOptions` method that you may find useful!
sink: Specify where the body of a response will be saved. Really useful for storing the contents of an HTTP request directly in a file
progress: A callback to execute every time transfer progress is made. Really useful for displaying/tracking the live download progress of the file
Matt Stenson retweeted
My current role was affected by a lay off, I'm officially looking for my next adventure! Would appreciate whatever reach I can get!
Matt Stenson retweeted
Noticing myself using AI (both ChatGPT and Claude) more while coding, especially when I'm unfamiliar or rusty with the language / framework. 🧠
Don't think we're very close to AGI, but I'm bullish on AI continuing to seriously augment the way developers work. Increased productivity, faster learning, and more shipping.
Matt Stenson retweeted
There's a huge death valley between the one machine and the many. You will INCREASE your likelihood of an outage from infrastructure complications as you split-out services (dbs, caches, jobs) EVEN WHEN ADDING REPLICAS, as it's the config and interconnects that'll fail you.
Matt Stenson retweeted
🆕 Prompt caching with Claude.
Caching lets you instantly fine-tune model responses with longer and more instructive prompts—all while reducing costs by up to 90%.
Available in beta on the Anthropic API today. anthropic.com/news/prompt-ca…
Matt Stenson retweeted
Firefox forever, no matter what platform I’m using
Chrome and its derivatives are hot garbage
Matt Stenson retweeted
I don't typically like putting companies on blast given my large audience here, but wow does @Zendesk deserve it.
The longer version will be shared later, but the short version is they:
1) Misled us twice on our contract renewal date
2) Refuse to accept that their mistake locked us into another year-long contract after acknowledging that they did make this mistake
3) Are continuing to charge us over $2,000/month for a service we explicitly canceled based on what their team shared with us about our contract renewal date.
This is so beyond unacceptable customer support that I'm genuinely speechless.
Matt Stenson retweeted
Laravel Advanced String Package laravel-news.com/laravel-adv… posted by @ericlbarnes
























