A DevOps crew? Mainframes aren’t something that are just part of some random web app project in a company. A System Administration team would be the likely maintainer. But a lot of mainframes are designed to be run with very little manual maintenance these days.

They’re also wildly different architecturally from your typical rack of x86 servers, which is why the initial reaction to Linux running on a mainframe sounded stupid at first. When I worked at IBM in the 2010s, a Linux Zserver felt more like a VM running inside the mainframe than anything else. There were abstractions of the mainframe components that intentionally leaked into the Linux side that were interesting. I knew very little about traditional mainframe software development at the time, so I was very fascinated by how it all worked.

I had to think about what a “slimming jab” would be. Interesting terminology for weight-loss injections.

We definitely had syntax highlighting in the 90s. I distinctly remember Turbo Pascal supporting it as early as 1992.

This kinda sounds like hell for low memory machines. RIP shared memory optimizations.

Keyservers already “solved” this problem without needing federation because we only needed one keyserver anyway. Federating them isn’t going to do anything. Web of trust is a broken system that sounds super cool until you try to really use it. It has so many flaws that there’s really no way to revive it. Keybase tried to do something about it and also failed.

To be clear, this is not Web of Trust. It's using Key Transparency as a means to distribute public keys more securely than TOFU.

If people want to build WoT on top of ny design, I won't stop them, but it's not a goal of mine.

Keybase was doing great until it got acquired by Zoom and people felt uneasy about the implications, IIRC

This is a false equivalence. The iPad would have to be 45 years old and, after the artist had sold the art many times before to others, had the iPad rediscovered by someone after it had been lost in their mom’s attic.

I'm specifically referring to the line of reasoning that if it doesn't cause material harm to infringe copyright, then it's okay to do.

You didn’t click into it, did you? The top level post did not have that restriction, but instead the post it replies to does. Go look.

The actual message in the bsky widget could be improved to state that the label is masking the original post and not the reply.

What a weird bunch of hacks just to stick it to Python.

Okay but has this process actually improved anything, or just substituted one process for another? Do you have fewer defects, quicker ticket turnaround, or some other metric you’re judging success?

Oh yeah, I’ve been a lot more productive, closing tickets faster.

These tools are somewhat slow, so you need to work on several things at once, so multitasking is vital.

When i get defects from the QA team, I spawn several agents with several worktrees that do each of the tickets- then i review the code, test it out and leave my notes.

Closing the loop is also vital, if agents can see their work, logs, test results it helps them to be more autonomous

If a question like these are a red flag to a company, that’s a big red flag itself and I personally don’t want to work there.