Given those pedals down below I assume he likes to check his side-view mirror a lot.

Urban Dictionary says: Fetch Stop trying to make it happen. It’s not going to happen. “That’s so fetch!” “Shut up, Gretchen. Stop trying to make fetch happen. It’s not going to happen.” Fetch by KamIsTotallyFuckingAwesome May 17, 2011 Word of the Day on March 30, 2019

and also

fetch slang for cool or awsome. Used in mean girls by Grechen Weener. Omg Kadi you love him. That is so fetch. Grechen stop trying to make “fetch” happen! It’s not going to happen! fetch by Kayla February 8, 2005

But from context I can tell you mean the first one :)

I dunno, they did manage to get the antichrist elected. Twice.

To put it into context, it’s doing about one full-time support engineer’s job currently, which is the maximum we’ve permitted it to do so far.

I guess the difference is that it I have actually seen it do legitimate work now. We have implemented outbound SDR and inbound tech support agents that do the right things. Our SDRs generate new leads for our (currently all-human) sales team to go after. They are boosting the numbers of closed deals. Our inbound tech support agents are closing a significant fraction of tickets. My last metrics call was yesterday, it was 12% of inbound tech support chats that never got escalated to a human. These are both first-draft tools, they’ll improve. They cost pennies per session to run. And client NPS scores show that they’re happy with the results. I don’t think we’ll see either of these tasks become 100% automated, but at even 25% or 50% that’s a lot of formerly-human work not being done by humans anymore. And we’re deploying more agents to handle more of the sales pipeline, development pipeline, HR and accounting. I don’t work for a huge company, there are a few hundred people total. This isn’t something that’s coming, it’s here already.

I’m not pro-AI by any stretch for a huge number of reasons, but in my day job as a technical product manager I have to use a number of AI-powered tools and workflows. Whereas 18 months ago they were a novelty that the bosses were enamored of, today they get real work done and speed up a number of key areas, mainly like fancy automation workflows (which have been around forever). The rate of improvement and capability for certain use cases has been very, very rapid. We do seem to be reaching a plateau though. The tools and models from 6 months ago are just about as good as the ones from today. And China’s models from today are better than the US’s models from 6 months ago, but at a fraction of the cost.

So when I hear people talking about the “end of the world”, I think a realistic case for that is that the AI tools that come out in the next few years will be good enough to do a fair amount of white-collar work, and we won’t have a plan in place to deal with all of the now out-of-work people that leads to. Whole classes of jobs in areas like data entry, telemarketing, and customer support will be almost entirely automated out of existence. New classes of jobs will be created, of course, but it’s hard to imagine them existing in sufficient numbers to make up for the losses. And this is just for LLM-workloads.

In other areas, other types of AI are already enabling robotic automation of factories and in the near-ish future might make self-driving truck fleets practical. This would be devastating because factory workers and truck drivers make up like 30% of the US workforce – and again, there are no signs of new classes of jobs that could absorb the out-of-work workers, and no plans for a social safety net or wealth distribution.

So I’m not worried about a rogue AI unleashing some bioweapon or launching a nuclear attack. I’m worried about a bunch of CEOs deploying barely-acceptable AI to displace millions of workers as soon as it is safe(ish) to do so.

If that CRT has a Trinitron tube it’d probably be pretty easy to find an arcade/retro gaming enthusiast in your area who’d want it (and probably even if not…)

One of the very first things the US govt standardized was the size of screws because it was wreaking havoc with shipbuilding efforts.

There was a stretch of the Florida coast that had metric in the late 90s and early 2000s, but people kept stealing the speed limit signs. They also had a problem with people misunderstanding 100kph (about 60mph) and doing 100mph instead.

Originally it was because the ship carrying the official metric measures from France to the US in 1793 was captured by pirates. More recently it’s because there was a near-revolt when Jimmy Carter tried to reintroduce it in the 1970s in an attempt to make the US even slightly less regressive.

Great! Now when can we get one of those?

Yep, tho it’s probably mostly because my house is old and poorly insulated.

I live in south Florida and replaced/resurfaced the asphalt parts of my roof with white PTO and silicone elastomer. It lowered power usage from AC by about 10% in the main zone and much more in a smaller zone where the AC ran constantly because it couldn’t maintain the temp (77F) with the black roof. That seems to be in line with current research but YMMV.

That’s true, but AI fellating is for the poor. Power brokers want to see live humans on their knees.

I do actually, it’s like an exclusive club, they need fresh blood. Plus, if there are no junior bankers, who would be constantly fellating the senior bankers?

Yes, this is the show I’ve been waiting for – big finance vs. big tech. It’s like the unstoppable force meeting the immovable object.

I think I’d catch some shit if I tried calling anyone a “sloperator”

This is what people know as “AI” right now (because it’s being shoved down their throats that way)

After a lengthy argument with my boss, I was allowed to “only” force the AI-first model onto half of my small dev team of 8 engineers and 4 QAs. After about a year, the results are obvious: the engineers who went AI-first are now AI-fluent: they know how to prompt the model, develop agents, AI-automate workflows, and push a TON of code. Like almost an order of magnitude more code into prod. However, to say their skills have stagnated would be generous. In some cases an engineer I could count on to debug a tricky issue is completely not able to anymore. Meanwhile, the non-AI team is now essentially my code quality and bugfix team. Their PRs are small and concise, their changes are understandable, and most importantly, their skills have remained the same (and in the case of the 2 juniors, have improved).

If we hadn’t kept a few people in reserve, we’d be fucked, because there have been multiple times where an AI-first engineer has tried debugging an issue (and with big models - Astra, Fable, Opus) that either totally failed and gave up, or made things worse by introducing “fixes” that made problems elsewhere.

So this is a small sample, and YMMV, but for junior engineers in particular (who usually have the least amount of say in pushing back against bad ideas) this is – not “is going to be” – a major problem.

I think people hate AI because:

• it’s trained on their stolen works
• they get no credit or payment when derivative works are made
• it let’s business owners threaten to dismiss more workers (who need to work to live, since there are no safety nets in place)
• when workers DO get displaced by AI, the AI does a shoddier job (enshittifying products and processes)
• further enables and accelerates the concentration of capital to the absolutely-most-wealthy-people

I could go on and on.