Tabflows 🏴☠️ retweeted
My hot take from chatting to @poteto is that we should use MORE abstractions in the AI age
You can use them (combined with harsh lint rules) to reduce the design space available to the agent and constrain them only to good decisions.
Combined with the fact that high-leverage abstractions let you do more with less code - so, more token efficient.
Plus, unwinding the damage from a bad abstraction is much cheaper with agents.
This runs counter to a lot of folks thinking that agents just want to read the raw code. They can, but they're not maximally efficient that way.
Be braver! Design abstractions.
241
196
3,678
385,149
Devs will make their agent wait on the rust compiler rather than admitting golang is the best agentic language
Rust no longer the defacto best language for agents
Compile times are too long, I'm always finding myself bottlenecked by time not intelligence
And the agents have gotten really at doing manual memory management now
4
2
20
1,374
custom engine or godot/unity/etc? i'm curious ppls experiences using claude with different engines
23
Tabflows 🏴☠️ retweeted
Only software engineers will understand why this is actually funny.
94
545
11,442
412,850
Tabflows 🏴☠️ retweeted
I want a harness that doesn’t write code for me, but instead tells me what I should do and then forces me to write the code. Imagine me basically trying to build something but instead of it writing code for me it’ll tell me what I need to write and then I can ask follow ups and it will point me to API docs, but it will never write a single line of code. I think this is the best way to stay grounded and continue to be a programmer if that’s something you wanna do that way you’re learning at much faster speeds. You’re basically guaranteed to arrive at the most optimal stack overflow link like the good old days.
88
8
323
34,774
Tabflows 🏴☠️ retweeted
Why should the specific harness that someone is using matter at all to the server? This is like making sure only Firefox can access your website - makes no sense at all.
2
5
276
11,108
Tabflows 🏴☠️ retweeted
What do you mean by "supported list" lol. It's an open protocol that both sides implement, Pi implements it as per spec, its you who don't lol
3
210
9,264
Tabflows 🏴☠️ retweeted
Hey @GayaniFigma , I think in spirit, when I created MCP, I envisioned an open ecosystem. That to me feels core. Seeing restrictions like this is sad and I hope Figma can get to a point where it’s more open or at least make the process of getting into the allowlist very easy.
40
55
1,838
193,439
Tabflows 🏴☠️ retweeted
Evidently Figma does not understand the point of open protocols.
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.
32
40
979
72,311
right- the past 30 years have been a pure and beautiful intellectual exercise, no profit motives at all
6
