On why internal "software factories" built inside companies turn into a maintenance burden. Horthy compares it to GitHub Actions, where teams define their own build steps but don't build the scheduler or the logging themselves.
Yep.
And it's somebody who is saying, we can't do that because we need all of these things. Yep. And you go, ah, yeah, well, our agent actually will get to that, I guess. Yeah. But nobody actually wants to do that. Well,
and it's like the people building these things, like, they have day jobs. It's like you do the Skunk Works project of like, cool, I built the software factory. And like, oh, we have 30 users. Now we have 50 users. And people are running a bunch of work through this background agent system I built. And then people have feature requests. And it's like, do you want your job to become like maintaining this like side project you Vibe code? Or do you want to do your day job? Or, like, which parts of it are worth investing in, right? Same with GitHub Actions. Like, in GitHub Actions, you define how is the language runtime set up, how are the tests run, but you don't build the thing that captures the logs, you don't build the scheduler, you don't build the thing that like catches a webhook from GitHub and launches the work.
Exactly.
There's like this overhead of building a CI system. GitHub Actions got the interface really, really well. Like, hey, you build this YAML format, you commit it to your repo. I mean, Circle and Travis had this too, but like, basically, that idea of like the hard, boring, annoying, not sexy part of…
I smell a reefer.