Well, often you don't get to "dump" your pension fund. In Denmark, it is your employer deciding what pension fund to use, and you will then have to use it. It is kinda ridiculous.

Why do you not want to name them?

It makes the conversation turn into an electromagnet for racists.

You can’t ignore the stereotypes, but you can let people figure it out themselves. You don’t have to say it when it’s already obvious.

Looks more like a computer mouse than a sports car.

May I ask what tools did you make so far? And what is on your roadmap?

Not OP, but a very simple example: I use AI to review my work before opening a PR for my colleagues to review. I ask it to review the commits in my branch. Instead of consuming tokens just to instruct it how to use git operations and other tools to find the commits since the base commit, I asked AI to create a little bash script to make patch files commit1.patch, commit2.patch, commit3.patch, etc, for all the commits in my branch since the base commit. Now I just use this script to prepare the context of commits to review.

I feel like an imposter here, I’m definitely not using AI as much as it seems everyone is :( I can’t imagine using hundreds of dollars of tokens a day. But maybe this little tip for reviews might be helpful to someone.

> Instead of consuming tokens just to instruct it how to use git operations

Claude already knows how to use git and jj, very well.

I also find it useful for review, and sometimes I use multiple passes to review for different categories. Like security, performance and so on.

Not op, made a tool to convert Microsoft OneNote notes to Obsidian canvas and Markdown. First it used a python lib which was too limiting. Then it used windows API to plug into OneNote and read the doc in its original XML form. That made the conversion correct and fully featured.

Not OP, but I've been focusing on linting and automation.

Custom lint rules to encode best practices that previously relied on astute/alert code reviewer to call attention to. This is handy not just for humans but it steers the bots too. Or turning on some existing rule that required a big cleanup/migration to be compliant with. Now I just throw an LLM at it, since they're often laborious but mechanical changes. Which is the sweet spot for an LLM.

Also automating everything I can. That annoying release process that everyone hates but wasn't quite long/arduous enough to justify the time before? It's now automated. GitHub workflows for all the things.

This kind of stuff will forever be useful, even if the bottom drops out and the bubble bursts. And none of it is reliant on AI to run

I have been self-hosting Forgejo for some time now. It is impressively easy to maintain and operate. I can highly recommend giving it a spin.

Related Cloudflare issue: https://www.cloudflarestatus.com/incidents/z3vgxxfvt3yb

> What's really happening is that a few employees realized they can game the system by turning on a firehose of AI slop and pushing 10x the LOC than any other engineer (with or without AI)

Did they figure out how to game the system? Or was the system set up exactly with incitaments to produce exactly this outcome?

They figured out how. Mind you the system was setup with incentives to produce this outcome - but before AI it wasn't really realistic to produce all those lines of code even though you could and so nobody was gaming it so badly it broke. (it was always broke, but the breakage was acceptable before)

The new system is immature and hence open to exploitation. This is eventually going to destroy some companies.

The article you are thinking of was likely written by Axel Rietschin who worked on Azure core compute team.

https://isolveproblems.substack.com/p/how-microsoft-vaporize...

HN thread: https://news.ycombinator.com/item?id=47616242

Wow. Yikes. I never liked Azure, but this level of dysfunction is just astonishing.

Yeah me too. I moved all my public projects to codeberg and my internal repos to self-hosted forgejo.

Hosting forgejo is really easy as well. It being a single binary makes it really easy to handle with almost zero maintenance.

Well, outages seem to be distributed across all days except weekends. So this seems like people fucking around with stuff being a major factor.

Surely it just means more people working, resulting in more load, resulting in more outages?

Or even both. In any kind of continuous deployment, you'd expect outages at the point of deployment, or shortly thereafter as the unintended consequences ripple.

Then the load during the working days makes those ripples larger and into outages.

Most outages are caused by changes by humans ("actors"?), very rarely are things "People just dig our stuff so much we can't keep up" but more often "We didn't think about this performance drawback when we built thing X, now it's hurting us", and of course, more outages when you try to fix those issues without fully considering the scope and impact.