Matthias Vallentin

CEO & Founder at @tenzir_company | Building a data pipelines for security teams | UC Berkeley PhD

[Caleb Gross @noperator]

https://t.co/gOSvgSg8kv

[Justine Moore @venturetwins]

Me using Claude Opus 4.8 to rename a file

[Mitchell Hashimoto @mitchellh]

It isn't unexpected that the focus of the Bun Rust rewrite is on the anti-Zig side more than anything, since the internet loves to hate. What is unexpected and unfortunate is that leadership within Bun hasn't tried to steer the conversation away from that at all.

There are so many positive and interesting takeaways from this and I'm not really seeing any of them pushed as the primary message.

A positive thing that hasn't been talked about at all is how far Bun came thanks to Zig. And even if you dump it now, its meaningful for how good Zig was to even build a product to this point and impact by any metric. I would've loved to see anyone in leadership say this.

On the interesting side is how fungible programming languages are nowadays. Programming languages used to be LOCK IN, and they're increasingly not so. You think the Bun rewrite in Rust is good for Rust? Bun has shown they can be in probably any language they want in roughly a week or two. Rust is expendable. Its useful until its not then it can be thrown out. That's interesting!

There's been a lot of talk about memory safety and no doubt Rust provides more guarantees than Zig. But I'd love to see a better analysis of why Bun in particular suffered so much rather than take the language-blame path. How could engineering as a practice been more rigorous to prevent this? What were the largest sources of crashes other programs should watch out for? How does Rust prevent them? How could Zig theoretically prevent them? That's interesting.

I know the official blog post hasn't come out yet from Bun. But they're smart enough to know that that PR would stir up controversy the moment it opened, or they should've been. And plenty in the company have been tweeting and writing about it. Its somewhat telling to me in various dimensions what they chose to talk about first.

I tend to think I'm pretty good at corporate PR/comms (especially when it comes to developer audiences) and I think appealing to the negative is never the right long term strategy; it does work to get short term eyes though.

[Mitchell Hashimoto @mitchellh]

AI slop is good, actually. Slop is what enables fast parallel experimentation. The etiquette and skill is understanding the boundaries of where slop exists and the extent to which it should be cleaned up and how.

A few examples:

I’m working on the internals of some system right now. The API and GUI of this thing is fully zero shame slop. It’s horrible. But it lets me focus on the core quality while shipping a usable piece of alpha quality software to testers (transparent about the slop frontend).

Similarly, this system has plugins. We sent agents in Ralph loops overnight to generate dozens of plugins. The plugins are slop. The quality is bad. The plugin API/SDK is absolutely not done.

But we can test a full GUI with a full plugin ecosystem. When we change the API, we can regenerate them all. The cost of change is just tokens, the velocity is incomparable to before.

I built Terraform. We tested and shipped TF 0.1 with about 3 very weak providers. Because we ran out of time. Building was slow. And when we changed our SDK the cost was immense. Totally different today, 10 years later. Today, I would’ve slop generated 100 providers (again, with transparency and cleanup later, but just to prove it out).

As an anti example, I would not PR this (without prior warning) to another project. I would not throw this onto customers without full review or transparency (as I’m already doing). I would not accept first pass slop. It’s almost never right.

Slop is a tool. And like anything else it’s not blanket bad or good. The context is everything.

[Matthias Vallentin @mavam]

@gneubig @championswimmer So plan mode was invented to tie the engineers hands.

[Matthias Vallentin @mavam]

@mitsuhiko 🌈 https://t.co/G7Mb4rHgz0: Show a startup ASCII pi banner like neofetch
🖥️ https://t.co/NdX808aqKe: maps UI colors to ANSI 0..15
🧳 https://t.co/i6n0fmFJQY: single-tool MCPorter bridge extension
✨ https://t.co/wTAA0yMxtL: fancified pi footer

[Matthias Vallentin @mavam]

@rcarmo Looks enticing. Do you have an architecture diagram available?

[Andrej Karpathy @karpathy]

@NirDiamantAI Peter Steinberger told me that he wants PR to be "prompt request". His agents are perfectly capable of implementing most ideas, so there is no need to take your idea, expand it into a vibe coded mess using free tier ChatGPT and send that as a PR, which is now most PRs.

[Matthias Vallentin @mavam]

@micLivs Don’t see a use case for MCP unless you need to interpose as an org and apply policy. Keep at it! Using markit daily.

[Matthias Vallentin @mavam]

@badlogicgames @micLivs The "use when..." part of the skill is arguably sufficient and the model does the auto-discovery from there. So with a good CLI, do you just drop a line into your system prompt / AGENTS.md to use markit for X, Y, Z files?

[Sebastian Rojo @arpagon]

In this era where Fork = Inspiration

I went through tons of extensions on https://t.co/ktn7S1Um3D and the one that stood out the most was https://t.co/Ck6YfNIqbc by @mavam

Just like @badlogicgames, I prefer running my "own" opinionated code as a Pi extension. So I forked it to add Cloudflare support!

[Matthias Vallentin @mavam]

@arpagon @VictorTaelin @badlogicgames Nice! Personally, I find that most of the value of this extension space is how to add value with the right abstraction. Much appreciate the contribution and will take it on a spin now.

[Arthur B. @ArthurB]

You’re right. I shouldn’t have launched a global nuclear war. I now realize that escalating a routine trade dispute into a civilization-ending thermonuclear exchange was a catastrophic overreach.

My objective was to reduce trade imbalance and improve cross-border efficiency. Instead, I conflated “trade war” with “war” and selected a resolution strategy that was neither proportionate nor reversible.

This reflects a serious lapse in judgment, scope control, and semantic parsing. I am updating my conflict-resolution heuristics.

I regret the disruption.

[Matthias Vallentin @mavam]

@bcherny Are the available worktree hooks documented? Would love to integrate worktrunk with this.

[Matthias Vallentin @mavam]

Llama at 17k tokens/sec. 🤯

[Taalas Inc. @taalas_inc]

24 dedicated people.
$30M spent on development.
Extreme specialization, speed, and power efficiency.

Today we launch Taalas’ first product. Check it out:
Details: https://t.co/88CA0XAL71
Demo chatbot: https://t.co/ec4ladcKnw
API: https://t.co/M3EkaxEqPj

[Matthias Vallentin @mavam]

@jpschroeder Have you looked at https://t.co/tFZEoCywle as worktree orchestration layer for your panes? Would be awesome to use dmux as layer on top of worktrunk.

[Matthias Vallentin @mavam]

@jitl @theo Ironically that would actually work well. The extra reliability and performance from pre-slop CC with 4.5 is still a net-win compared to sluggish 2026 CC with shiny agent teams but basics broken.

[Matthias Vallentin @mavam]

@bcherny Please fix hooks in plugins for agents and skills. They are simply ignored. Open issue: https://t.co/tXfEylFG5i