Interesting how many people "Like AI" because it's good at all the jobs other than the one they happen to make a living doing.

Did you hear about the screenwriters school in which the professors said to avoid AI for writing, but it's great for storyboards. And the storyboard school where the professors said the opposite?

The reality is that AI isn't actually "good" at anything. It produces passable ersatz facsimiles of work that can fool those not skilled in the art. The second reality of AI is that everyone is busy cramming it into their products at the expense of what their products are actually useful for.

Once people realise (1), and stop doing (2), the tech industry has a chance of recovering.

Yeah, I think I heard about that. Within certain domains it is certainly a useful tool. I would say things like online search are much nicer now (in that asking an AI is equivalent to searching online but it summarizes it for you). Online search fits the strengths of LLMs nicely, but right now it's being sold as a silver bullet, which it's not.

I have no design talent but wanted to help my partner with some charts. She was making them in Excel. I had Claude Code build them as web docs and they look quite good. Probably had to give it around thirty instructions about changes, which was pretty inefficient, but then again I couldn't have created them myself and they look far nicer than the charts she got from Excel.

It's really just about recognizing what they can do well and applying them in the right moments.

It's a version of the Gell-Mann Amnesia effect.

GitHub has been unreliable since before AI. Though it's definitely gotten far worse.

Seemingly the decline started with the Microsoft acquisition in 2018, and subsequent "unlimited private repository" change in 2019 (to match Gitlab's popular offer)

One example is the search being broken for CI logs. It takes over your browser's search hotkey too. What happens is every stage of the log is collapsed so the search doesn't work until you trigger the expansion but if you attempt to search before expanding the search will never work after it's been initialized. It's pretty infuriating when you're trying to find something in a giant build log.

It really gives you a sense that no one at GitHub finds it necessary to search those logs.

Which I find…unusual.

I bet on rushed Azure migration. A lot can go wrong it devops.

I think maybe it's not that GitHub is using AI, but that the amount of AI slop going into GitHub may be more than they expected.

Productivity is finite. If you pivot entirely to the AI stack, you're going to lose bandwidth for everything else. It's an opportunity cost problem.

Indeed. I used to have 20. Now I have over 500 repos. All ai

We had more and more outages on EVERYTHING since AI. Not sure what they're doing.

The nvidia thing makes sense. If you get AI to write code for a platform you no longer really have an incentive to care that much about (windows) for a purpose you increasingly don't care about (actually drawing things to a screen), you're probably not going to test it as thoroughly as you used to