ninjalanternshk

The problem is people keep trying to regulate businesses by name instead of by the effects they have.

If we had regulations on noise, vibration, emissions, water use, electromagnetic radiation, whatever else, then it wouldn’t matter what people tried to build — if it fits within the guidelines great, otherwise back to the drawing board.

Putting “data center” in your ordinances is as lazy and ineffective as putting “abattoir.”

> There are no meaningful regulations in building them

If a municipality doesn’t have emissions, noise, water use, etc regulations, that’s a serious failure in governance.

We don’t need nor want the word “data center” in regulations anymore than we need the word “abattoir.”

The names of the things we build change all the time. Their impact on their communities don’t.

We need to regulate impact, not the name or type of business.

If we did, nobody would know or care about data centers and they wouldn’t be affecting their communities, because they’d be operating under established impact regulations.

Thank you! I thought it was just me.

It’s like saying “make this bad animal drawing look better, and like someone else made it” without telling them what animal was supposed to be.

Yeah this is about the worst way you could imagine to evaluate an AI model.

If you’d given it a real task you’d have been impressed.

I was floored by the day I spent with Fable. Got weeks of work done.

You don’t need to be a TLA.

Google “4chan tracks down Shia LaBeouf”

Just imagine how much an authentic keyboard with a Clippy icon would fetch, to the right buyer that is.

We should be basing public policy on facts not marketing language.

22 year old single me would have enjoyed this little adventure.

NGOs are not lobbyists.

Some NGOs lobby/employ lobbyists.

That’s not the same thing.

I’m working on a DaaS startup (drone as a service) so maybe I’ll locate next to you and your customers can blow drones out of the sky and mine will keep having to replace theirs.

Lots of AWS’s control surfaces are in us-east-1, and (not calling out any specific instances here) sometimes what’s call an “AWS outage” especially regarding us-east-1, is actually a limitation on accessing those control surfaces, ie, making changes to assets that are actually hosted elsewhere.

In such cases the services continue to operate as-is despite problems in us-east-1.

Not saying that’s not a problem, just, clarifying the scope.

The spa approach also achieves what’s probably the key ingredient to making this useful medically — consistent data over time. We know the “what’s this fuzzy bit!?!” hysteria with elective scans can be counterproductive, but if you truly had monthly scans going back 2 years, the fuzzy bit could in fact mean something.

The sci-fi writes itself. Someone hacks the spa’s schedule to find out when you’re getting your scan done, then hacks the machine to push the output to 11 when you’re in, and liquifies your insides.

The first Midjourney Medical murder.

It’s also possible to not really hold that strong an opinion on things. Not everything is a pitched battle where doing what your employer wants means you’ve sacrificed your integrity.

Aren’t human coders non-deterministic? There’s no guarantee two people with otherwise identical levels of experience will always write identical code.

Any software engineering practice that had enough review and feedback to work with humans should work more or less the same with AI coders.

It’s when someone tries replacing an entire team or an entire process with a single prompt that they get in trouble.

And most of that happened under comparatively good administrations. Imagine what’s been greenlit now.

My contracts always state I own tools created or byproducts of the work that don't end up in the work.

Potential monkey wrench: you’re assuming the AI agents we have access to are the same ones crawling and indexing the web for those models. They not only incorporate the text they find while crawling, into their models, but they have access to some kind of web search behind the scenes as well — when you ask a chatbot for information on a product or person or whatever, it doesn’t “go out and look for it” it hits up a web index (which literally could be Google, but is probably something a little different) and then searches the sites the indexer returned.

Your test replicates what happens if someone asks for something specifically on a given site, but not necessarily what happens when you ask the chatbot for info by name/title instead of specific URL. The former is generally much more important than the later.

Just my take - I could be wrong.

By not excavating the whole city they leave work for future archaeologists. :)

Make the keywords meta tag great again.

The image at the top of the article is awesome. The whiteboard in the background holds a passive-aggressive defense of ChatGPT’s coerced confession.

I fear for falling into the trap some political parties get into — anything the other guy came up with is bad, by definition.

If JetBrains Mono suits your work you should use it, not avoid it specifically because AI often uses it.

As someone who’s writing gets flagged as AI a lot, I appreciate the opening disclaimer section.

And I especially appreciate the idea that these patterns aren’t the problem. Don’t just fix the patterns. The problem is they point to hastily or carelessly written content.

I frequently use “belt-and-suspenders” — probably not in wri… crap I just used an em dash.

I’ll take “what is Dunning–Kruger” for $200 Alex.

> No, you didn't create it. AI did.

No, AI assembled bits of code written by hundreds of programmers before you.

Astute observation. Gopher is in fact a portal that lets you teleport from one off-grid cabin to another, all around the world. And some people like that.

That would be irc.

Also, the Unix “talk” command is a nice 1-to-1 chat protocol along the lines of finger, ie

$ talk snoopy@dog.house

I had an algorithms class in undergrad where we designed algorithms for computers with specific memory and processor configurations that didn’t exist, and specifically, would never be built.

But we studied algorithms for them anyway.