Oxide and the Chamber of Mysteries [video]
youtube.com
youtube.com
But now I can look forward to their leap over to “social audio”. First Twitter spaces (where I would sometimes chime in live) and now the Discord-hosted On the Metal.
Most podcasts are sports commentary. These guys are full-contact in the game. I love it. Keep it up Bryan!
What I (we!) love about social audio is that it allows for many more voices -- both on the team here at Oxide and in the broader community. As a result, we've been able to get into some really deep detail with members of the team; I collected a few of my favorites in [1].
Thank you again for the kind words; I think you'll enjoy exploring the back catalog of Oxide and Friends!
May I suggest a small teaser trailer post to the old “On the Metal” feed? I’m still subscribed there, but wasn’t aware of the new channels.
Those were some incredible interviews! I’ve listened to a few of the episodes twice.
You made my commute a lot more enjoyable. Still going through the old catalog -- the episode about NeXT and Objective-C (S1E8 July 5, 2021 [1]) was excellent.
Keep up the great work Bryan!
Big same. I was so happy to find the Oxide and Friends podcast that I went through the entire backlog in the last couple months. It really helped solidify my thoughts on debug-ability as a first class property of a programming language/environment/system.
It's a great mix of tech history, personal accounts from industry, practical conversations about development and debugging and current industry happenings.
A few standout episodes:
Engineering Culture
Engineering Incentives... and Misincentives
The Rise and Fall of DECTo the best of my knowledge (and I would love to be proven wrong!), this is the first time an engineering team has gone on the record with their warts-and-all experience with electromagnetic compatibility (EMC) and safety compliance testing. If you have never heard of compliance before or have no idea what any of this could possibly be about, you're guaranteed to learn something about the world of devices around you. And if you have dealt with EMC: you know how wild and unpredictable the process can be -- and I think you'll enjoy hearing some of our own harrowing details. Either way, this is a technically meaty discussion that I think the HN demographic will enjoy!
Indeed. Any update on a ship date?
The D-Jetronic isn't really microprocessor-controlled though; a similar story came from the Missouri Highway Patrol. In the 1980s, they had pursuit 5.0L Ford Mustangs, with Ford EEC-IV MCU fuel injection. They also had police radios that had been tweaked to increase the transmitting power past what the FCC would consider normal, and past what Ford had rated the EEC unit for EMF. It was discovered that, at highway speeds with the cruise-control on, holding the transmit button on the handset down for more than ten seconds caused:
1.) The engine controller to think the gas pedal had been floored. 2.) The transmission to need to downshift.
With the police-duty 5.0, this was...startling.
In a time when tech is imploding under the weight of its own hype, the amazing retrospectives, history lessons and low-level hardware/software lore contained in that podcast has been the highlight of my days every. Single. Time.
It reminds me that there is a side to this industry that is still actually solving real problems (from testbench design to firmware/software supply chain and attestation) instead of just throwing GPUs at a problem and virtualizing an infinite number of monkeys to generate Shakespeare sonnets.
In these days of layoffs done to compensate for hyped investments and lack of strategic focus, it is a shining beacon of... actual engineering.
A minor sidenote, for those who probably care more about software: The podcast drew me back to Rust because, all of a sudden, here were these people who actually _reasoned out why_ it made sense, and had decades of expertise that allowed them to spell that out with actual examples.
But I really stuck around because of the low-level hardware discussions, and the history background (I just listened to the Optane episode yesterday, and although I knew some folk at Micron and understood why it had failed in general, the discussion was amazing).
(I'm a telco/hardware guy drifting inside the bowels of a cloud/software behemoth and dearly wish I could burn to the ground all the paperwork, ceremony and "strategic investments" that surrounds me and just go and do interesting stuff, so forgive me if this seems a bit much. If I can stay up late enough--I'm in Europe--I might try to join on Discord some day.)
I've been wondering, what's the plan at Oxide with the recent announcement from Intel about moving away from the Intel Tofino business? Are you still going to be using tofino 2 chips for the network?
The conversation goes along as if there's periodic pictures to be seen of what's being discussed.
Yeah, just feeling grumpy about this not being a podcast like it used to be :)
> just feeling grumpy about this not being a podcast like it used to be :)
In what sense is it not? If you mean about the medium here, you can still get it that way! https://oxide.computer/podcasts/oxide-and-friends has the various links to different ways of getting it in pure podcast form.
Part of what we wanted to create with both "On the Metal" and especially with "Friends of Oxide" is something that we (Adam and I) both really appreciated as younger engineers: hanging around the (metaphorical) campfire, absorbing the wisdom of more senior engineers through their lived stories. On the one hand, we have lost a bit of that in that we (broadly) aren't in person, and as a result we don't break bread as much as we used to with the team. But on the other, social audio offers us an even better path: the campfire is not only accessible and open, but recorded -- the tales and wisdom can be absorbed beyond earshot. This was something I was uncertain about when we started, but I have now heard from so many younger engineers for whom "Oxide and Friends" has been meaningful that I can now say it with confidence: social audio is an essential vector for engineering oral tradition -- would that more teams partook!