Adam Simpson

10.7K posts

Adam Simpson banner
Adam Simpson

Adam Simpson

@a_simpson

I do open source 📊 at @grafana. I tweet about the NBA before Christmas. I recognize cookies as currency. I love my wife, Christi. ❤s Magit.

Dayton, OH Katılım Nisan 2007
278 Takip Edilen580 Takipçiler
Sabitlenmiş Tweet
Adam Simpson
Adam Simpson@a_simpson·
Yesterday we launched a project in collaboration with the @okcthunder: ⚡thunder.run I couldn't be more proud of how it turned out. 🏃‍♂️💨🕹
English
0
1
6
0
Adam Simpson
Adam Simpson@a_simpson·
@mutewinter Hey, nice! 🏆 That's exactly the thing I'm talking about 😅
English
0
0
2
12
Adam Simpson
Adam Simpson@a_simpson·
The OpenAI app confusion makes me wonder at what point do people vibe-code their own LLM apps and OpenAI/Anthropic/Gemini are relegated to "just" API providers?
English
1
0
0
113
Michael Yockey
Michael Yockey@myockey·
I wonder how many people hold Bitcoin with the hope that it’ll protect them from the consequences of widespread societal collapse not realizing that it depends on compute and networking resources that will almost certainly fail simultaneously as the collapse for which they are planning.
English
1
0
7
1.4K
travis4nh
travis4nh@travis4nh·
1/ I predict that BTC will never see highs near 120k again. I further predict a long slow slide into irrelevance. I predict that BTC will never see highs near 120k again.mpelling, 99.9% of holders are pure speculators, which creates a hype cycle of "line go up".
travis4nh tweet media
English
63
8
157
11.5K
Adam Simpson retweetledi
Mitchell Hashimoto
Mitchell Hashimoto@mitchellh·
Got em. I poison my AGENTS.md (and other things like code comments) all over the place with prompt injections like this to find people who don't review their code and sling it off to another human. Catches folks all the time and then its an instant ban. As I've said, I don't care if you don't review your own code. But if you're submitting code to an OSS project and crossing a human boundary, it is simple courtesy to do some human review.
Seb ⚛️ ThisWeekInReact.com@sebastienlorber

🤪 Great AI disclosure trick @mitchellh :D

English
184
438
7K
775.4K
Adam Simpson
Adam Simpson@a_simpson·
I'm convinced this Fable fiasco could have been avoided if Anthropic were honest about what LLMs are and not constantly hyping each release as AGI.
Adam Simpson tweet media
English
0
0
2
42
Jeremy Mack
Jeremy Mack@mutewinter·
@a_simpson Hohoho I just got this bad boy used. Mint condition. Only possible now that I can dictate everything and not use the damn painful keyboard
Jeremy Mack tweet media
English
1
0
1
32
Jeremy Mack
Jeremy Mack@mutewinter·
If you’re using Stage Manager on an iPad, try turning it off. Performance difference is massive.
English
1
0
1
76
Adam Simpson
Adam Simpson@a_simpson·
@myockey “Bash tool” calls in Pi is any interactive call. So disabling “bash” disable this whole class of problems. Of course, it’s much less useful 😅
English
0
0
1
9
Michael Yockey
Michael Yockey@myockey·
@a_simpson “Hmm, the user hasn’t provided any tools. I’ll implement setuid so that I can run this command as root.”
English
1
0
1
36
Adam Simpson
Adam Simpson@a_simpson·
@adamhjk Pushing on the core point idea a bit: do we even know what is core in the product? The LLM will frame every optimization like it's essential and incredible. Maybe 1.5ms _is_ totally awesome but these decisions will compound and that's how the psychosis creeps in.
English
1
0
2
652
Adam Jacob
Adam Jacob@adamhjk·
And yet - for the vast majority of domains, this kind of deep optimization is absolutely unnecessary. A $350 ralph loop that takes you from 88ms/150k to 1.5ms and 500 is *amazing*, and you didn't even have to look at it in order to get there. The core point stands - you can't delegate the core of what makes your product great to a machine that builds the machine. You never could. But the vast majority of the software you write? It's not in the category @mitchellh is talking about. It's just code. You could gain massive optimizations for little to no effort.
Mitchell Hashimoto@mitchellh

I've got an agent in a loop optimizing a renderer with the goal to minimize frame times (and tests to measure). It got times down from 88ms to 2ms and allocations down from ~150K to 500. Sounds good, right? Wrong. This is exactly why agent psychosis is a big fucking problem. As an experiment, I rewrote the Ghostty core render state in Go, with access to identically laid out data structures as Ghostty and the exact same validation tests. I made a purposely naive renderer (simple, correct, but slow). 88ms per frame with 150,000 allocations (horrendous, lol)! I then kickstarted a Ralph loop to bring the frame times down. I told it it can't modify input data structures or the public API or tests (they're correct), but it can do anything else it wants. It got to work. It has worked for about 4 hours. I've spent around $350 on this experiment so far. The results? 88ms => 1.5ms 150K allocs => ~500 allocs Incredible right? Nope. My hand-written renderer I ported has frame times (same benchmark) of ~20us (0.020ms) and 0 allocations in the update path. This is the problem with psychosis and lacking systems understanding. If you don't understand the system, you're going to accept that this is an incredible result. If you understand the system, you'll see better solutions immediately and can do roughly 75x better on throughput. The people who blindly trust agent output are in the former camp. They're sheeple, overdrinking from a fountain of mediocrity. Standard disclaimer: I use AI all the time. I like AI. The point I'm making is to not blindly accept results. Think. Analyze. Learn.

English
11
7
86
21K
Michael Yockey
Michael Yockey@myockey·
@a_simpson I hadn’t considered that you could put all common elements in a single template file.
English
1
0
1
24
Adam Simpson
Adam Simpson@a_simpson·
Been working with Go's template library a lot recently, this slide deck (I know right?!) has been super useful #slide=id.gf8c32e69c9_0_0" target="_blank" rel="nofollow noopener">docs.google.com/presentation/d…
English
1
0
2
83
Adam Simpson retweetledi
Jeremy Mack
Jeremy Mack@mutewinter·
I just realized all the homelab dads are now claude code influencers
English
2
0
1
86
Jeremy Mack
Jeremy Mack@mutewinter·
After using Codex for a couple hours, I can safely say all the positive sentiment is due to the generous token limit and has very little to do with the interface or the agent.
English
2
0
0
81
Mario Zechner
Mario Zechner@badlogicgames·
> These engineers can review their agent's code much faster than reviewing human code. wat
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
70
36
1.2K
137.8K