Видео

Please check the date in the title of the episode :-)

Hello from Turin

Which episode is Bryan talking about at 1:39:05?

Beer Tunnel

We've spent the last 60 years - since Dennis and Van Horn - re-implementing capability security badly and re-discovering that these techniques happen to work shockingly well.

System 76 can make Coreboot work on modern processors.

So much respect for 0xide's communication around AI. If you have a use case, here's how easily you can do it, otherwise, there's not a shovel in sight.

I have to say, the sheer speed of provisioning and setting up Helix, really shows off how much Ooomf! is behind the Rack.

Sounds a bit like kql from Microsoft

UNIX is the outgrowth of that which exists in all of us.

If a SQL query is taking too long, then either the index is defined wrongly or there is no index, in either case the query is doing (a) full table(s) scan.

Is that "not invented here" I hear at 06:56? From anyone else, no surprise, but from you guys, the students of history?

Yep, you did reinvent the wheel, and not in a good way. Use ANSI SQL.

Piping tables reminds me of Power Query M code

M3QL was a pipe based query language for M3 TSDB eventually abandoned for PromQL.

I have to say, the audio has been consistently good last 4-6, 7 live streams. Levels have been good.

Oh interesting you're not compiling OxQL to SQL.

There is no on time, only early or late. Except for Gandalf, he arrives precisely when he intends to.

Oh God now I'M triggered. I'm a Deuce Deuce rider too. We have enough high-powered engineering talent in the Bay Area to turn this into a train paradise, if we wanted to! How do we make that happen? IDK

Some great takeaways from this! Was a good one to reflect on my own style of 'management' as I'm trying to navigate keeping a foot in the technical details while taking on more senior managerial type work at the startup I'm at. I think Clarity + Trust is a really great lens to use to decide how to get involved. I don't have the time or energy to micromanage, but I can sometimes be a little too hands-off. I've seen how people, particularly Engineers, can get caught on certain ideas and head down paths that don't really make practical sense to do. I'm not sure if you've covered it in a past episode, but I'd love to hear more about how Oxide manages to set the direction for individuals and how you make sure you're building the right thing, and delivering the right work, on a day to day basis. Like RFDs obviously seem fairly core to setting the direction, but how do you then make plans around that and deliver on it? At my startup we're basically mandated from up-high to be doing sprints and planning in Jira and all that. I try and keep it as low touch as possible while still giving the visibility that the execs need, but I find myself more and more saying "Can you make a ticket for that?" "Is there a ticket for that?" It's our only method for tracking the ridiculous amount of work we need to deliver on, without dropping it all. Also, I loved the detour into the elaborate prank on Dave Hitz

If I ever start a business, I'll probably be in Flounder Mode. Lying at the bottom, both eyes fixed in the same direction. 🐠

Was really hoping you would cover this. Thanks!

I don't know anythibg about servers. How do server CPUs work? Are they x86? Can they run CLI desktop programs the same way?

Now all the jargon is made flesh. Now I know the diff between Gimlet and Scrimlet. Very Nice.

But where's the VGA connection?! 😱

These “neck down” framings are a wise cinematographic decision.

This weird little company has some surprisingly good marketing material

😍

superb design would like to see a better video i.e. hi-res, closeups and better lighting

Very demure, very mindful!

It's such a clean design! Looks like Oxide EEs and MEs are allowed to talk to each other, directly. 😅 I especially like the minimal use of cabling.

Easily replaceable temp sensors on little daughter boards is a great idea.

it looks too big for what it is, should have 2 cpus for the size

To whom do I send the nickel?

Why 54v?

Superb!

21:04 "The content of a note may be any thought, suggestion, etc. related to the software or other aspect of the network. Notes are encouraged to be timely rather than polished. Philosophical positions without examples or other specifics, specific suggestions or implementation techniques without introductory or background explication, and explicit questions without any attempted answers are all acceptable. The minimum length for a note is one sentence." my heart fluttered,,,,,

1:22:32 "owning your strategic weirdness" is amazing. "We didn't even know what they were going to be." There's so few companies that have such concrete backbones, artifacts where institutional knowledge lives and grows. Theres a lot of telling stories here about this RFDs, but man, it all revolves around such a fabulous incredible case of how engineering can work, how information can exist, that so few companies utterly lack. And this just seems like such the better world. Writing things down & letting people see is such a superpower!

"is this a gen x thing?" 😂 "isnt that a boomer thing?" im dyinggg

Germany is accepting Bryan's apology. This time.

it would be interesting to see if there are any abandoned RFDs suitable to be made public -- i would love to read about an alternate-reality Oxide solving different subsets of problems

Bryan Cantrell is ahead of his time

Wow, Dave is humble. Bryan sounds like a great boss. Cheers from Canada.

Too bad you guys didn't know about Vertica. Vertica solved the replication, sharding and clustering problem on top of Postgres, and it does what it says on the tin.

Could you talk about how you sorted out logistics like coming up with the sales / licensing / support contract for customers to sign when they buy the product?

I wanted to like like CoackroachDB but its PL/pgSQL support is incredibly immature.

Curious how many of Postgres sharp edges still exist or have been solved in Postgres-compatible AWS Aurora.

Great episode, and a cautionary tale of the pitfalls of writing software that's so robust that no one needs to upgrade from the open-source version to the new proprietary version.

This seems kinda like structured concurrency, mirrored in server land.