Herbert "TheBracket" Wolverson

I haven't received my author's copies yet, but Amazon just notified me that the print edition of Advanced Hands on Rust is now available. a.co/d/fKDDReZ You can also buy the ebook from Pragprog right now, 50% off with the coupon code "save 50" #rust

@DanielSmidstrup Refactoring and bug fixes.

What will come after AI?

I'm also 0 for 3 on /goal. All 3 function, and all 3 skipped specified steps. Still getting far better results with a PRD, small steps and verifying each one. Or just writing the code, which is more fun anyway.

Gpt5.5 is a strange model. It can get things working from a vague outcome (usually with obvious holes). Give it a detailed algorithm for what you want, and half the time it decides it knows better - and makes something far worse. 5.2 xhigh is still my preference.

This is the the quote I've been citing a lot recently.

Eliminating whole categories of bugs is awesome - doesn't mean you can forget the others, but still awesome!

@jaywengrow @ramtop @herberticus Check out the entire top 18 Pragmatic Bookshelf Best Sellers this week: pragprog.com/best_sellers/

#LibreQoS - When we finished removing the reload penalty, we unblocked a lot of development options - many of them features people have been wanting for a long time. The most recent is dynamic circuits: devblog.libreqos.com/posts/0016-dyn… #bufferbloat #latency #jitter #OpenSource #QoE #QoS

🔄 #RustConf Workshop: Practical Actor-Based Concurrency in Async Rust with @herberticus (@ardanlabs) Level: Intermediate. Build a realistic async service from single stateful actor to multi-worker system — covering backpressure, graceful shutdown, and when NOT to use actors. Add to your #rustconf26 registration today: rustconf.com/register?utm_s…

@olson_dan I've used match (thing1, things) and arms like (Some(x), Ok(y)) before, which reads more like a truth table. It's gnarly if you have a LOT of combinations or variables, though. (I actually try to avoid that with let else bailing out early, when I can)

With a naked `if let`, you get used to it. Adding something new on the left makes it hard for idiots like me.

I figured out how to explain why this bugs me... reading order required to understand is just all over the place. But listen, it's fine and I'm just being whiny. I can be whiny on my own twitter.

🦀 Rust: Deadlock-Free Mutexes Instead of hoping lock ordering is correct at runtime, Surelock pushes deadlock prevention into the type system: • invalid lock ordering rejected at compile time • ergonomics that still feel practical notes.brooklynzelenka.com/Blog/Surelock #rust #rustlang

The Rust team is happy to announce a new version of Rust, 1.95.0. Rust is a programming language empowering everyone to build reliable and efficient software. blog.rust-lang.org/2026/04/16/Rus…

@thsottiaux Any word on Linux support?

Codex just got a lot more powerful. Computer use, in-app browser, image generation and editing, 90+ new plugins to connect to everything, multi-terminal, SSH into devboxes, thread automations, rich document editing. Learns from experience and proactively suggestions work. And a ton more.

@Dimillian Linux support?

I’m diligently working on enhancing all the features of the Codex app to make it even better for you. If you have any suggestions or ideas for improvement, please feel free to share them with us here!

Now is the best possible time to register for #rustconf 2026 taking place from Sept 8-11 in Montréal + online. Early bird pricing flies away on April 29, so claim your spot at the 10th annual flagship Rust language event now: bit.ly/4tsiKdf

#LibreQoS very own @herberticus will be at @rustconf 2026 in Montreal 🇨🇦 + ONLINE, September 8-11. You can attend his workshop: rustconf2026.sched.com/event/2IEzX/wo… #RustLang #RustConf #Rust #RustConf26 #OpenSource #FLOSS #FOSS #bufferbloat #latency #jitter #QoE #broadband #RFC8290 #QoS

Looking forward to giving a workshop on using actors!

Free as in Freedom: devblog.libreqos.com/posts/0015-fre… I’m @herberticus, lead developer of #LibreQoS. I joined not long after Robert & #DaveTaht got the ball rolling, added #IPv6 support, and created most of the #Rust parts, C parts, etc.. #OpenSource #FLOSS #bufferbloat #latency #jitter

For a long time, #LibreQoS has only gathered traffic data at “enqueue” time - when packets enter #Linux Traffic Control: devblog.libreqos.com/posts/0014-kpr… A recent update changed this. #OpenSource #FQ_CoDel #RFC8290 #sch_CAKE #XDP #LinuxKernel #eBPF #bufferbloat #latency #jitter #QoE

@BatsouElef That's a pretty cool looking setup, from the features list. I'll send it to the rest of the team and see what they think! Thanks!

I see (I've used Zulip in the past, too). One of the reasons I was asking is that I'm trying to improve my tool (already have some users) regarding receiving feedback. Our motto: "Centralize feedback, prioritize features, and keep your users in the loop with a beautiful, modern feedback management system." My friend and I have been building this for a while... If you want, you can sign up to see its full potential. It's completely free. If you need more info. Feel free to DM me. dxwork.io/dxFeedback/ind…

Genuine question for founders: when's the last time a user's feature request actually changed your roadmap? Not the one you were already building, a real surprise that made you rethink priorities. Drop the story below. 👇

@BatsouElef We run a public Zulip chat, and link to it in the help (and docs), and encourage feedback that way. Trade shows are great for feedback, too. Even just recording a demo video, you immediately see the pain points a lot of the time! Only downside of chat - there's a LOT of messages

@herberticus Wow, 3 years of persistence from one user’s feedback leading to a major core rewrite, that’s dedication. Respect. If I may ask, how are you receiving feedback? I mean, do you use any specific software for that?