
Why I'm Learning ROS 2 as a Database Person
There's no real story for storing and querying ROS 2 telemetry at fleet scale. I'm going to build one and document everything I get wrong along the way.

Author profile
I host the Arrested DevOps podcast. Ex-DevOpsDays organizer. Head of DevRel at Tiger Data: Postgres, time-series. Formerly pretending to be a Go dev. Currently pretending to understand robotics.
Browse the latest writing surfaced through DevArt.

There's no real story for storing and querying ROS 2 telemetry at fleet scale. I'm going to build one and document everything I get wrong along the way.

The agent isn't the hard part. The scaffolding around it is. Here's how we built ours so a non-engineer could ship to production safely.

You've created hundreds of indexes but do you know what's actually happening underneath? B-tree internals, page splits, MVCC bloat, and the diagnostic queries to see it all for yourself.

Coding agents aren't magic. But for internal tooling? They've brought back the "just build the thing" era I've been missing since Microsoft Access.

Strategic product leaders sit at the intersection of everything. Learn why Product is DevRel's most valuable partnership—and your secret source of business intel.

You've learned sales, marketing, finance, and PLG. Now learn how to translate DevRel work into business language that resonates with every stakeholder in your company.

Product-Led Growth changes everything for DevRel. Learn how PLG works, why it matters for developer tools, and how DevRel becomes essential infrastructure.

Want to defend your DevRel budget? Learn to speak finance. Understand P&Ls, CapEx vs OpEx, and why your CFO cares about things you've never thought about.

DevRel isn't marketing, but you need to speak their language. Learn about funnels, MQLs, and campaigns...and why understanding marketing makes you better at DevRel.

Stop treating sales like the enemy. Learn what your sales team actually does, decode pipeline and ARR, and discover how DevRel impacts deals without selling out.

DevRel teams struggle to prove value because they lack business literacy. Learn why understanding sales, marketing, and finance is foundational to DevRel success.

Bridge the gap between CloudGovernance.org's 5 Pillars and DevOps culture using the CALMS framework and Westrum organizational model.

Use Tailpipe (a lightweight, open source tool) to analyze GitHug audit logs using familiar SQL syntax to identify overrides to branch protection rules

https://keyoxide.org/6529B08F20194D84FFAC7C5850F46247289D3110 (please feel free to ignore this!)

Sept 1, 2020 was the 7th annual DevOpsDays Chicago conference. It was also the first time we did it virtually. It was super well-received, and a lot of folks have been asking me for details on our implementation.

We tend to focus on the negative, and rarely recall the positive things we have accomplished, or the impact we have on others. Here's my tip for helping to overcome this.

Did you know that Homebrew can install more than just packages? Here's a guided tour through my Brewfile to see how I set up applications and more on my MacBook.

Infamous cloud influencer Corey Quinn live-tweets Matt Stratton's talk from DevOpsDays NYC 2020, in a good-natured "roast" format.


Don't believe everything you read on the internet when it comes to DevOps. A lot of people think they know what they are talking about, but they really don't. I, on the other hand, know exactly what I'm talking about.

Deciding to submit a talk for consideration at an event can be a troubling thing — what if my idea isn’t good enough? Do I think big enough thoughts to share a stage with Thought Leaders? Why would anyone care what I have to?

Wouldn’t it be great if we could generate an incident when our systems fell out of compliance? By combining Chef Automate and PagerDuty, through simple webhooks, we can absolutely do this.

Back in October, I decided I was going to “force” myself to use Visual Studio Code as my only edito...

I just remembered that it’s compulsory to write a blog post when you change jobs. This is mine. If yo...

Traditionally, we attempt to ensure stability by reducing the vectors that can make changes to a system. In practice, that means "deployments are executed by trusted individuals with admin access". The trouble with this approach is, people make mistakes. Even admins. And not everyone can understand the implications of every script, command, or function they are asked to execute.

When we are working to bring about cultural change in our organization, it’s essential for us to understand that not everyone speaks the same “language of DevOps as we do.

It’s quite easy to become creatures of habit, especially with our tools.