> Tom pulled up the tool’s specification on his diagnostic display. This was always the first step: read the spec, not the code. Clearly this writer has never felt the frustration of CC telling them a feature was never a part of the plan, because it overwrote the plan and then compacted.

This approach doesn't give access from the hypervisor to your private keys it gives access to other tenants to your private keys.

Back in 1960 us early detection systems mistook the moon for a massive nuclear first strike with 99.9% certainty. With a fully autonomous system the world would have burned.

Not a big exactly but if pip doesn’t work it goes straight to pip —break-system instead of realizing it needs a venv

Also if a prisma migration fails it will say “this is dev it’s ok to erase the database” before rerunning the command with —accept-data-loss

Given how many projects I've seen that run prisma migrations on prod from their local CLI instead of CI...

This scares me.

Give Cluade Code a go. It still makes a lot stupid mistakes, but its a vastly different experience from pasting back and forth with chat gpt.

There's no free trial or anything?

You can play with the model for free in chat... but if $20 for a coding agent isn't effectively free for use case it might not be the right tool for you.

ETA: I've probably gotten 10k worth of junior dev time out of it this month.

The chat is limited and doesn't let you use the latest model. if that's representative of the answers I would get by paying, it doesn't seem worth it.

Im not crazy about signing up for a subscription service, it depends on you remembering to cancel and not have a headache when you do cancel.

It is ridiculously easy to create an album with Suno and push it Spotify. I'm surprised its only 66% TBH

Anna's archive has a great analysis of the Spotify data.

They identify a huge surge in tracks that few listen to after gen AI started.

The analysis is worth reading. The distribution is (Pareto)^3 ~99% of the tracks played are 1% of the catalogue.

1. Generate slop music nobody will ever listen to 2. ???? 3. Profit

It's actually:

1. Generate slop music no _human_ will ever listen to

2. Use a botnet to "play" this music en masse

3. Profit

This is a whole arms race, with companies (such as Beatdapp) specializing in detecting fraudulent plays.

Source: I work for a niche music retailer that struggles with the same issues on a smaller scale.

When we switched from x264 to hardware based encoders it saved something like 90% on our customers' power and cooling bills.

So while this essay might be "technically correct" in some very narrow sense the author is speaking with far more authority than they have the experience to justify, which is what makes it obnoxious in the first place.

The author is directing this at complete noobs who are subbing their first anime and you are complaining that it is not applicable to running a datacenter?

the author never talked about power savings or cooling bills, they talked about quality so they are still correct.

This is already mentioned in the article. Software vs. hardware is a tradeoff. x264 produces higher quality (perceptual or compression efficiency) video, at the expense of latency.

Someone linked flesh simulator the other day and now my you tube is filled with some seriously weird stuff.

Just Ask them to describe Shannon Entropy. If they start talking about information they are out, if they start talking about their crazy cousin they are in.

You need to get someone out there. Just tell them over and over again its an outside wiring problem and demand they dispatch a tech. the tech will have different phone numbers with people that sort of know what they are doing. At least this worked before chat gpt ate the world.

Sounds to me like they already had at least three on-site visits by technicians.