Matt Henderson

10.7K posts

Matt Henderson banner
Matt Henderson

Matt Henderson

@Yerbamatt

Growth at @sentry. Denver sports fan.

Boulder, CO Katılım Mart 2017
816 Takip Edilen1.4K Takipçiler
Cynthia Bell McGillis
Cynthia Bell McGillis@cynthiamcgillis·
It’s truly tragic how we just collectively gave up on headphone usage as a society. It is so rude & invasive to blast your audioslop in public places. Guy behind me on the plane is doing it and I just asked him if he had headphones and he pointed up to indicate they are in his luggage. I offered to get them for him which seemed to appropriately embarrass him. His headphones are now in use.
English
3
0
23
810
Matt Henderson
Matt Henderson@Yerbamatt·
@DLineCo Might be the only big thing we have to look forward to. Strawther making a leap would be huge too
English
0
0
1
99
Michael Grinich
Michael Grinich@grinich·
Today WorkOS is launching auth.md An open protocol for agents to register for services on the web. We're partnering with @Cloudflare and @Firecrawl as some of the first providers. Why did we build this? And why now? 🧵
Michael Grinich tweet media
English
87
159
1.6K
301.3K
Matt Henderson
Matt Henderson@Yerbamatt·
@hridoyreh yes. So far it's pretty decent. The targeting options are very different than any other ad platform. It's just a big input field and you use natural language to tell it what to go after and who you target for each ad set.
English
0
0
0
259
Harpreet
Harpreet@harpreetchatha_·
ClickUp unleashed AI on their blog & this is how it went. The dip keeps dipping.
Harpreet tweet media
Zeb Evans@DJ_CURFEW

Today we reduced headcount by 22%. The business is the strongest it's ever been. So I think it's important to be direct about what I'm seeing and why. First, I made this decision and I own it. I did it because the way to operate at the highest level of productivity is changing, and to win the future, ClickUp needs to change with it. Second, this wasn't about cutting costs. Most savings from this change will flow directly back into the people who stay. We'll be introducing million-dollar salary bands. If you create outsized impact using AI, you'll be paid outside of traditional bands. Most importantly, I have the deepest gratitude for those affected. We're doing this from a position of strength specifically so we can take care of people properly. Everyone affected receives a package aimed at honoring their contributions and easing the transition. I only see two options: wait for this to play out gradually in the market or be honest about what I'm seeing and act proactively. THE 100X ORGANIZATION The primary change is that we're restructuring around what I call 100x org. The goal is 100x output. The roles required to build at the highest level are fundamentally different than they were a year ago. Incremental improvements to existing systems won't get us there. We need new ones. That means creating enough disruption to rebuild rather than iterate on what's already broken. The common narrative is that AI makes everyone more productive. It doesn't. Many of the workflows of today, if left unchanged, create bottlenecks in AI systems. These roles will evolve. But waiting for that to happen naturally means falling behind now. The 100x org is actually heavily dependent on people - infinitely more than today. This is only possible with 10x people that have embraced and adopted new ways of working. THE BUILDERS, AGENT MANAGERS, AND FRONT-LINERS — THE BUILDERS: 10X ENGINEERS I don't think most companies have internalized what's actually happening with AI in engineering. The common narrative is that AI makes all engineers more productive. That may be true in isolation, but at an organization level - that is the farthest thing from reality. Here's what we've validated recently at ClickUp: the great engineers, the ones who can orchestrate, architect, and review, are becoming 100x engineers. They're not writing code. They're directing agents that write code. The skill is judgment. AI makes the best engineers wildly more productive, and everyone else using AI slows these engineers down. Think about it - the bottlenecks are (1) orchestration - telling AI what to do, and (2) reviewing - what AI did. Everything is leapfrogged and no longer needed. So who do you want orchestrating and reviewing code? And how do you want your best engineers to spend their time? If your best engineers are spending time reviewing other people's code, then this is inherently an inefficient bottleneck. These engineers can review their agent's code much faster than reviewing human code. The new world is about enabling your 10x engineers to become 100x. The wrong strategy is to push every engineer to use infinite tokens. Companies doing this are celebrating 500% more pull requests. But customer outcomes don't match the volume of code being generated. I call this the great reckoning of AI coding, and every company will face this soon if not already. More code is just another bottleneck to the best engineers, and ultimately to your company's impact as well. — THE BUILDERS: 10X PRODUCT MANAGERS Product management and design roles are merging. Designers that have customer focus, become more like product managers. And product managers that have intuition for UX become more like designers. The bottleneck of user research is gone. It takes us just one mention of an agent to kickoff research and analyze results. The bottleneck of product <> design iteration is also gone. The product builder iterates on their own, along with agents and skills that ensure alignment with quality and strategy. Also controversial today - I believe that the wrong strategy is to have your PMs shipping code - that just introduces another bottleneck that the best engineers will waste their time on. To be clear, PMs should be coding but they should do this in a playground to iterate, validate, and scope. That code should not go to production. Everything outside of managing systems, orchestrating AI, and reviewing output becomes a bottleneck. That's why the other roles that are critical along with these are the systems managers (to reduce bottlenecks) along with a bottleneck you can't replace - customer meeting time. — THE SYSTEM MANAGERS Ironically, the people that automate their jobs with AI will always have a job. They become owners of the AI systems - agent managers. We have many examples of these people at ClickUp. The underlying systems in which we operate are absolutely critical to get right. I think most companies are delusional to think they can iterate on existing systems and compete in this new world. You must create enough disruption so that old systems are deprecated entirely. If there's any definition for 'AI native' that's what it is. — THE FRONT-LINERS In a world that will become saturated with AI communication, the human touch will matter more than anything to customers. This is a bottleneck that you shouldn't replace - even when agents are high enough quality to do video meetings. One-on-one meeting time with customers is something that shouldn't be automated. The systems around the meetings should be - so that front-liners spend nearly 100% of their time with customers. REWARDING 100X IMPACT In a world where companies are able to do so much more with less, where does that excess money go? In our case, much of the savings in this new operating model will flow directly back to those that enabled it. We must reward people that create productivity accordingly. This aligns incentives on both sides. Plus, in a world where your best people create 100x impact, you can't afford to lose them. You should aim to retain these employees for decades. The context they have and their ability to efficiently orchestrate and review will be nearly impossible to replace. Compensation bands of today should be thrown out the door. We're introducing $1 million cash/year salary bands with a path available to nearly everyone in the company if they produce 100x impact by creating or managing AI systems. THE FUTURE Nearly every company will make changes like these. The ones that do it proactively will define what comes next. The future is not fewer people. It's different work, new roles, and better rewards for those who embrace it. We're already seeing entirely new roles emerge, like Agent Managers, that didn't exist a year ago. ClickUp is positioning to lead this shift, not just internally, but for our customers too. I've never been more certain about where we're headed.

English
37
23
641
156.6K
Code With Antonio
Code With Antonio@codewithantonio·
I spent the last few months building my own Claude Code from scratch 🤖 Today, I’m open-sourcing the entire project in a completely free 12-hour tutorial ⚛️ React-powered terminal UI with OpenTUI ⚡ Stream AI responses directly in the terminal 🛠️ Build your own tool calling system 📁 Read, write, and edit project files 🧠 Create custom agent modes & permissions 🔍 Search and understand entire codebases 🔐 Browser-to-CLI authentication with @clerk 💳 Usage billing with @polar_sh 🤖 AI code reviews with @coderabbitai 🚀 Deployments with @Railway 🗃️ Database with @neondatabase 📈 Monitoring with @sentry
English
14
16
211
10.8K
Joe Devoy
Joe Devoy@JosephDevoy·
Introducing Tempo: The world’s first AI Head of Growth. AI can now scale a brand faster than any human, see how:
English
435
319
3.8K
1.9M
Matt Henderson retweetledi
Sentry
Sentry@sentry·
Have you spotted us in your city? 👀 (kinda hard to miss us tbh, we're in 7 major cities)
Sentry tweet mediaSentry tweet mediaSentry tweet mediaSentry tweet media
English
0
1
9
867
Matt Henderson
Matt Henderson@Yerbamatt·
@cynthiamcgillis Exactly! Conflicting messages. The best I could find on this was: you don't need it for their AI products, but they are acknowledging as valuable for an agent-crawlable website in the future. Especially for things like developer documentation
English
0
0
0
35
TheSearchSherpa
TheSearchSherpa@TheSearchSherpa·
@chris_nectiv This almost makes me sad for the tokens burned two weeks ago when this puzzzle peice was not available to use in a full SEO optimizer macroskill that uses screaming frog MCP and clarity to optimize client sites
Homer Glen, IL 🇺🇸 English
1
0
0
135
Chris Long
Chris Long@chris_nectiv·
I can't contain my excitement SEOs!!! There's now an official Screaming Frog MCP that lets you execute a crawl + analyze the data directly in Claude.
GIF
English
26
21
303
39.1K
Matt Henderson
Matt Henderson@Yerbamatt·
@jakezward It's almost like: Seo = physics Aeo = chemistry Both sciences, but different practices.
English
0
0
0
41
Jake Ward
Jake Ward@jakezward·
SEO in 2026: (if we're REALLY being honest) 1. SEO: Good SEO means good AI visibility in almost all cases. AI has EXPANDED SEO (not killed it). Search is up 26% as a whole since ChatGPT launched. 2. AEO: 90% of "AEO" is just SEO done well. Make sure you don't burn budget on tactics that don't actually do anything. Schema isn't parsed, llms.txt has 0 measurable impact, similarly with .md files. 3. GEO: Every major LLM either retrieves from Google or was trained on data weighted by the same authority signals Google uses. Either way, SEO is the lever. 4. AIO: Optimizing for AI comes down to 2 things: getting mentioned on authoritative sources (so models learn you exist) and ranking well in search (so they cite you live). That's PR and SEO, both are 25+ years old. You don't need a new strategy every time there's a new acronym. You just need better SEO.
Jake Ward tweet media
Jake Ward@jakezward

x.com/i/article/2054…

English
27
26
241
32K
Matt Henderson
Matt Henderson@Yerbamatt·
Also seeing lack of context as one of the top pain points when coding with AI validates a lot of the work Seer in @sentry solves for. Using production context = better results for root causing issues.
Matt Henderson tweet media
English
0
0
1
61
Cynthia Bell McGillis
Cynthia Bell McGillis@cynthiamcgillis·
I need @theHankTaylor & @mgonto to cover @hyperagentapp on their next Code to Market pod. Eschewing the Airtable brand all up feels so expensive and painful. But I guess they understood the sentiment towards Airtable is "who uses that anymore" and so it was easier to just do a new brand.
Cynthia Bell McGillis tweet media
English
3
0
2
329