Skip To Main Content
Peter Mbanugo on Muck Rack

Peter Mbanugo

Munich
As seen in: Yahoo, LinkedIn, freeCodeCamp, DEV Community, CODE Magazine, Cloud Native Compass, Eat Sleep Code Podcast
Software Craftsman— builder, writer, teacher, @pluralsight author, podcast dub.sh/web-perf-pod Also on 🦋 @pmbanugo.me
Is this you? As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work. Claim your profile

Get in touch with Peter

Contact Peter, search articles and posts on X, monitor coverage, and track replies from one place.

Learn more about Muck Rack

Actions

Share this page

Is this you?

As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.
Claim your profile

Articles

A Crash Course on Concurrency: Build a Tiny Scheduler from Scratch

|
By Peter Mbanugo
| pmbanugo.me
Concurrency is something we use and experience every day. Yet, concurrent systems fail in interesting ways, for various reasons. One of them is that some of us don’t understand how the concurrency runtimes or libraries we use work, which leads to poor use. I’m not going to argue Async/Await vs Fibers or Coroutines, I’ll leave that to the details of my P99 Conference talk coming up in October 2026.
Open in Who Shared Issue with article?

Search code, repositories, users, issues, pull requests...

|
By Peter Mbanugo
| github.com
What's new Zero copy socket I/O send/write 42b85ae Removed TinaContext as a type and reworked various functions that depended on it. 49855fe Isolate's timeout wakeup no longer depend on mailbox capacity 49855fe Boot validation for supervision group table capacity 1b2724e Make shard liveness broadcasts reliable e2bf14d Added compiler sanitizer (TSan, ASan, MSan) to the CI via compilation flags. Further added AddressSanitizer custom poison/unpoison hooks to that we catch logical lifetime issues.
Open in Who Shared Issue with article?

Control Flow in Odin

|
By Peter Mbanugo
| pmbanugo.me
In the previous chapter, we looked at how Odin approaches memory management. If memory is allocated, you can see where. If it’s released, you can see that too. Control flow follows this same philosophy. Reading control flow in many production codebases is a daunting exercise in mental reconstruction. You dig through exception handlers, nested conditionals, defensive checks, and early exits before you finally uncover the code that does the actual work.
Open in Who Shared Issue with article?
See all 171 articles