Do you manage infrastructure? Do you use #Terraform #Tofu to do it? Do you like operating at scale?!?!! You better come to the next #Stategraph Demo Day on MONDAY MONDAY MONDAY. You'll see the latest in Stategraph functionality and what it can do for you! Reach out to me for an invite

And yes, we’re hiring! oxide.computer/careers

Interesting competing (I think??) predictions in Oxide predictions. @ahl.bsky.social predicts AI Slop will make proprietary software more valuable. And another prediction is that AI will reduce the value of a lot of software because you can write it yourself.

Working on episode 2 of our podcast, Pid1. First one was titled "There are no Freeloads in OSS". This second one is about our pricing and how we got there, it's called "Software is too Expensive". #podcast #oss #terraform #tofu

I think a fundamental, and important, difference between application code and infrastructure code is testability. You can test application code in a range of environments and gain confidence it will work in production. Infrastructure code is defining the environment so you cannot test it elsewhere

Last Friday I realized why all these "you're doing X, X is wrong, you should be doing Y" posts from competitors bother me so much: the lack of empathy it has for users that often aren't in control of doing X.

You know you're old when you enjoy a sunrise without having stayed up all night

I'm moving to Firefox, one tab at a time. Maybe. I don't know. The web experience is turning to a pit of despair so maybe it doesn't matter which browser I use. But I really hate Google for killing my adblocker.

As a software engineer I'm legally required to relate engineering I know nothing about to my form of engineering. As such, after reading Skunk Works (recommended by @bcantrill.bsky.social on Oxide and Friends), ...

"I like all things pickles". Does that mean I like anything that's pickled or that I like to pickle everything?

My dream is to make the first Michelin Star salad buffet

I see posts from competitors out there that are roughly "you're doing X, but X is wrong, you should be doing Y". Today I finally articulated why these posts piss me off so much: they lack any kind of empathy for the user.

Added a new ticket to the backlog github.com/terrateamio/...

Like most people, we reflected on the last year and what we learned, and the #1 takeaway was that our pricing didn't reflect our values. We were in the mindset of trying to maximize contract value rather than give the fair, and honest, value. So we redid our pricing page to reflect that.

The recent news around Tailwind, to me, is more evidence of @sogrady.org 's thesis in The Software Paradox. Fantastic product, nobody wants to pay for it. The paid product always felt to me like a good passive income idea but not a career. Does The Software Paradox need an LLM update?

I really dislike mobile apps that are limited to specific regions. What is this, DVDs? Yes, just because I live in Europe doesn't mean I never need to access my Bank of America account.

I've never deployed SQLite as the system of record into production where I didn't regret it and wish I'd just used PostgreSQL. SQLite as system of record is a neat thought experiment. But, like unikernels, falls flat in the face of actual production workloads and needs.

Q1 is going to be an intense quarter for Stategraph, we have some ambitious plans, to make #Terraform and #Tofu scalable and faster. For me, it's going to be a real test of my ability to stay organized and focused on the goals.

Dropping a big refactoring today. Hold on to your butts. I've tested it a lot but at this point it's better to get it out in front of people and iterate quickly on the remaining edge cases.

Slack has really improved my life.

Over the past 6 months I've been doing a big refactoring of our event evaluator based on Build Systems a la Carte. It's taking 6 months not because it's so hard but because it's not a priority (the current evaluator works, it's just not as good as I want).

We use a "capabilities" model in our API, to make MQL sane for admins, I think maybe the capability to do joins in MQL might be useful, that would reduce the chances of queries that destroy performance, maybe.

I think I'm going to backport MQL from Stategraph back to our orchestration product, it's just too useful to have this super expressive interface to all rows that a user has access to. Yeah, performance can be a question, but thankfully PostgreSQL lets you limit how long a query can run.

For Stategraph, we developed MQL, the M is ambiguous . But it's a proper subset of SQL. We parse it into an AST, do some (security) analysis on it, updates some parts, and then turn it back into SQL and run it directly on the database.

Websites telling me that my password needs a capital letters and a symbol and number in 2025 is stupid AF. My password is 120 chars long, measure the entropy.

If you close your eyes, you can't tell which decade we are in. IBM mainframes all come with code, for free, back in the day. "Open source" (in the sens they didn't value open source at the time). And you listen to this and it's the same idea. I mean that in a positive way.

I think my favorite time to do development is after a big release. There is something about looking at the code base not under the pressure of a release where you can see all the answers to the things you were struggling. It brings clarity.

Catching up on Oxide and Friends podcasts, hit the episode where @bcantrill.bsky.social states the three most influential technology books to him, so now I'm reading Skunk Works by Ben Rich.

@coryodaniel.bsky.social A lot of people don't know this but Val Kilmer's character in Willow's complete first name is "Madmartigan". The "Mad" is not a title. All these years I've been calling him "Martigan", I was wrong.