11,181 karma · joined December 23, 2017
See: every manager and CEO that gets a bonus from cutting down head count or keeping the hiring budget as low as possible.
I don't care about what they say because of who they sold out to
Or it's an obscure bash oneliner hidden in another repository as a package that you can depend on, which is either wrapped by another YAML config or maybe some JS.
I don't think the criticisms of Jenkins compare because Jenkins is really much more than a CI layer, predates the concept of devops and our modern understanding of CI/CD, and it has a lot of complexity to make that work. That was back when you'd have IT teams provisioning your servers for you and shit.
People have to take 'no' for an answer sometimes, even if they don't accept it. You can't really 'gatekeep' your own product.
Maybe the CI could be a bit better (secrets management will sting you if you don't read the docs first), but that is also pretty no-nonsense and gets the job done.
If you like no-frills and an expectation that you know what you're doing, it's pretty sweet.
Would probably scare off most collaborators though but that, IMO, is part of the appeal. If you want to contribute then it's more likely you're invested and not driving by.
Also I like that it has a concept of projects so you can group repos together (which on GH would normally require creating an organisation account). And a repo can be public but unlisted, so it's open but not drawing attention.
AI makes investors/shareholders go brrr.
It has really just coasted on GH's network effect because everybody uses GH for git by default. It doesn't really have much direct competition and anything that does offer something like GH just doesn't have the same mindshare.
In that way, GH became more like MS.
AI doesn't make that very easy if you're just two people staring at an agent, but I think a lot of people who aren't already senior are going to hit a wall they can't climb when their experience limits what they are capable of doing with AI.
As with many things, usually the bad experiences with collaborative methods come from a specific implementation and those experiences become the bias.
It is pretty much the lowest common denominator for code.
Seems to me like that worker's ass wasn't covered at all and now everyone's all up in his shit on his socials, and the layers of management get to wash their hands, even though it's the management and executive that are pushing AI at all costs.
But you know what is a better neighbour than a data centre or an office or a strip mall? A nice public park and local shops that support the community without you having to drive your car a distance that in any other country would be easily walkable.
Why would anybody want a monolithic megastructure sat next to their house that offers nothing good to the community itself? There is no upside for the locals. No improvement to quality of life.
The credits at the start are off centre, biased to the right hand side.
The prose that follows is fully centred, so it hangs to the left of the actor names, and it has a little bit of rich formatting. It's not even good prose because it is overloaded with emdashes, almost as if it's direction. People will say this is like AI but even AI has more restraint than this.
So the fucking amazing title card for blade runner is a studio intern scrolling the first couple of pages of the screenplay through an overhead projector. Because it follows the exact format of a screenplay.
But really it is the audio that is doing all the work. That is ominous and spooky and futuristic as hell.
Funnily enough CF has redesigned its navigation several times in the past year, just like GitLab used to do. Shuffling the UI like a deck of cards is pretty desperate.
The readme I generated for an agent I put on top of pi reads almost the same as this.
AI does not do emotion. There is no punch, or pop. If I walk away from an announcement thinking it's AI slop then the announcement failed.
It's nothing like the posts Cloudflare used to write.
You can probably throw together a passible auth system on top of it that works with the htaccess format. Which is another cgi script but chowned so it can't be called from the outside. If not that, public key crypto - give your agents certificates that are part of the chain of trust. Mint those out of band and give them an insanely short TTL. Fail2ban or something like that to prevent abuse (agent getting handsy with the server gets blocked, credentials revoked).
The side benefit is that everybody starts writing perl and awk again. Who needs a JS runtime when you have CGI?
Only when my AI and its subagents are modelled through a graph of producing agents, consuming agents, and agentic mailboxes, will Claude Code truly shine.
Easier to just do a reset instead of thinking about how one might bring effective change over a reasonable period of time.
It became pretty clear that drinking culture in a lot of places develops around people having a lot in common, and certainly becomes worse when one of those things in common is 'enjoying drinking'.
I don't mind this. I had all of my 20s and most of my 30s for drinking after work. Now it's not really something I care about.
I've had trouble unpacking some of the copy it generates because its default tone of voice is fairly unintuitive. It's almost like it's designed to induce psychosis because it makes you feel like you've discovered something novel.
This does not even speak to it pegging my CPU and keeping the fans running on full blast even when the laptop is supposed to be idle overnight.
I think even this is largely beside the point. The acquisition of any project by Big Capital (whether tech or VC) is usually a killing blow.
I'm sure there was some logical reason for shoehorning web technology into this stack given that we have a good 40 years or so of experience with interactive terminal programs that use curses/ncurses, alongside emacs, vim, almost the entirety of MS-DOS, and so on.
The process of iteration, or the feedback loop, typically allows space to try things out and experiment and then either drop an idea or refine it more purposefully. And those breaks in between the pure delivery to focus on that gives you room to breathe and also see the progress of your work.
Blatting it out in 6 hours with Fable 5 skips all of that and you have something like an MVP, but you haven't really put anything of yourself into it. So why bother committing unless you can take that further or apply something novel or reflect your own personality in it? Or you genuinely believe you're on to something and the AI approach actually gave you a path to building it?
I've been 'vibe coding' something, I've spent about a month on it on and off along with a fair bit of debugging on some sticky issues. I still think I'd suffer going into that codebase and doing stuff in it by hand, no matter how well I thought I organised it all.
There is no clear product vision or overarching roadmap in terms of users and UX, it is just vaguely connected things being vibe-coded in parallel.