Running a Japanese Deli & building enterprise commerce at scale. Agentic workflows, design systems · Lead Frontend @IBMiX DACH. Opinions are my own.

Germany
Joined April 2016
Maximilian Henrich retweeted
It's sort of fun to observe how LLMs are turning everyone into middle managers with all the usual middle manager problems
It's so funny to see people who never used AI to code still think in categories like "OK, but then it will break the production and no one will be able to understand what's going on to fix it!" They cannot imagine that no one will be needed to understand anything: They will just send a new prompt "This thing produced this wrong value. Find the reason and fix it."
13
71
2
3,426
190,606
So fun seeing previously known but little used patterns emerging with evolving workflows and ai capabilities. People worry programming will get too „easy“ and sure some things might get solved from traditional fields but complexity is emerging in other areas or shifting. As one thing simplifies more becomes possible and brings its own challenges
Introducing gdp-ts: Ghosts of Departed Proofs for TypeScript. gdp-ts is a library, linter and AI skill for safer API design. Under this contract, sensitive functions require 'proofs' that the caller performed an authorization check. The typechecker verifies these proofs at compile time, preventing your team and agents from shipping catastrophic security (and other kinds of) bugs. While these patterns have existed for quite some time, especially in ecosystems like Haskell, ① human code review and ② cognitive and syntactic overhead made these solutions niche. The situation is now inverted. Agents are writing more code than we can review, and they *thrive* in tight loops with hard constraints that would frustrate us. We see this with the rise of Rust, borrow checker, code aesthetics debate and all. The README and examples model a real-world Vercel API product constraint: changing the password on a Project requires a proof of a certain role + a certain entitlement. Thanks to Matt Noonan and Ollie Charles for their research in this space. github.com/rauchg/gdp-ts
8
I've been struggling to use Figma with Open Code for months. I'm glad this is finally getting more visibility Feel like it definitely goes against the spirit of MCP and an open ecosystem
Replying to @dsp_
Hey David, Gayani here from Figma. You're right that our remote MCP server only accepts clients on our supported list, and Pi isn't on it yet. You can see the current list in our MCP catalog at figma.com/mcp-catalog. If you'd like Pi considered for a future addition, please fill out this form: forms.gle/qSvUawwznWyoj8Go7.
38
Maximilian Henrich retweeted
Been thinking about this a lot: there's still a gap between humans and agents in development. Not capability; agents will keep getting smarter. It's three things that look like weaknesses but aren't: Curiosity, pushback, and rest. Curiosity: we wander off & try things nobody asked for. We get bored/obsessed, want things to exist (like me with state machine tooling), and a lot of really awesome things come from that. Agents can explore, but only inside a "prompt" someone else wrote. They can't come up with ideas on its own (prompting "come up with ideas" doesn't count!) They can build our ideas and riff on them, but they don't have ideas of their own that they obsess over on their own. Pushback: "is this actually needed?" "will this move the needle?" We ask questions like that because we have experience/scar tissue. We've been burned by recognizable patterns before, and push back because of the emotional toll of being the one that has to maintain it. Agents push back too sometimes but there are no stakes; it's just them pretending to pushback without real emotional motive. Of course you can tell them to push back, but ironically that's just another instruction they're obeying. Rest: We know when to stop, more or less. We get tired, call it a day, and that boundary (not laziness!) is a feature. Every change widens the blast radius. Stopping is where you can check the last batch of work and verify everything before the state space explodes again. Agents working in their fancy overnight loops nonstop looks more productive, but it's just accumulating tech/cognitive debt faster than can be paid off. And sure there are tests, but tests catch what you thought to test for; they don't shrink the state space of things that can go wrong. Exhaustion is a feature: it tells us our judgment is slipping. Agents degrade too (context length, drift, etc.) but they don't "feel" it like we do. They just push on with full confidence and worse judgment. Sure you can approximate all three with fancy skills or prompts or harnesses or whatever. They help, but they're all simulations, because those three things come from the one thing agents don't have: a "self" that persists and needs to pay for its own mistakes. They don't need curiosity; we need to scratch an itch, they don't They don't need to give pushback; nothing's at stake for them They obviously don't need rest; although sometimes I wish they'd chill out they were close to hitting their token limits 😅 And no, this isn't something that's "fixed in the next model update" or "this harness/tool/skill/etc solves it". All these things are really the same thing: - Curiosity = what's worth doing? - Pushback = is it actually worth doing? - Rest = when is more not worth it? Agents are incredible at the *doing* part, but they don't have much to say about *worth*, because worth only matters to whoever has to live with the result. That's the human part. IMO it's still extremely important and will continue to be, and it's not something we should automate away. It's what gives agents their purpose.
15
14
1
143
8,398
It's pretty funny to me that half of my timeline is people arguing to use GPT-Astra as an orchestrator with cheaper subagents and the other half is arguing for cheaper models using Astra as an implementer
1
23
The year is 2130. You open your feed. There's a new No Man's Sky update
143
Everything needs a pachinko variant
guys hear me out: new pachinko reasoning picker for Codex 💸
1
32
I do enjoy the influx of Berlin conferences lately, less so the 4 hour delays on trains on the way there and back
19
Great fireside chat and very down to earth AI takes by Werner Vogels at @WeAreDevs Web development has always been a learning journey and AI is a great turning point but it also doesn't change the importance of fundamentals and decision making or responsibility. And also enjoying the process.
1
32
Of course AI is a fundamental change in the industry and an accelerant, and how much AI-generated code actually gets checked and read is a hot topic. Same with people feeling less valid because some or most of their code was generated. But I don't feel like that is fully new, we have been using libraries, copying snippets, even more so with shadcn-style component approaches. Most don't write 100% from scratch. Its not a 1:1 comparison. Ai code is fresh every time, so it doesn't fully translate to libraries. But there can also be bad or poorly maintained libraries and even more so when we copy code from other sources. How much can we trust how much do we validate and what are the validation mechanisms. Same issue really, where do we put focus and do we have systems in place with the limits of our attention and time. So this doesn't feel like a new issue to me, it has basically been like this forever. Approaches, checks and validations might change, but that's fine.
13
Even though they have been around for a while suspense and "use" patterns are often not clear in teams For this and SSR PPR ISR, cache tag etc patterns there is def room for some better dev tooling / visualization
I've been working on the React Suspense docs: there's now a full list of what activates a Suspense boundary, with a live example for each trigger! Thank you @sebsilbermann and Dan Abramov for reviews! react.dev/reference/react/Su… Demos below ↓
2
4
1,459
Maximilian Henrich retweeted
writing fables with Fable, call me Aeslop
124
683
61
10,531
345,091
Google Maps managing a business opening hours is the worst at this, interface jumping on every interaction and no copy Give me all the copy options
New availability components dropping 📦
49
So many posts here I try to zoom with double tap but it gives a like because it’s a 0 second video Not sure if that is a new meta or some other quirk
11
I do love the idea of approving plans with all tool calls and permissions listed. Right now yolo mode or step by step approval babysitting are both not ideal. Permission management will change for sure a lot with more deeper integrations and automations
6
Second time after Vercel Ship in Berlin now for WeAreDevelopers They really were trying to answer the question how many talks can we do at the same time, answer is a bazillion
42
Maximilian Henrich retweeted
If Fable is a steel glove and GPT 5.5 is two horses underwater, I'd describe Sol as a hurricane lantern
10
7
2
112
11,499