It’s how Bugs Bunny said “moron”.

It was a male-targeted soap opera.

I see this a lot but until you can get rid of money in politics all this policy does is shift power to lobbyists who are even less accountable, because they become the keepers of long-tenured institutional knowledge.

One side appoints Justices that voted against Citizens United and one appoints Justices that voted for it. That’s a huge distinction.

Every election since I could vote (early 2000s) has been the most important.

Why? Because the results built the Supreme Court that curtailed every progressive policy achievement and accelerated our current descent into fascism.

Without GWB you don’t have Roberts or Alito. Without Trump you don’t have Gorsuch, Cavanaugh, or Barrett.

Those fuckers have lifetime appointments. One lost election sets us back decades. The only good time for a protest vote is the primary.

Honey, nut, cheerio.

If you scale it up you can probably send more than one right? Send ten and nine work. That’s not nothing.

“All models are wrong; some are useful.”

You’ve missed the role of the Supreme Court in this. The Justices appointed by the Ds have been against the worst of it at pretty much every opportunity and they have lifetime appointments.

That was the real cost of Trump 1.0.

There’s a scene in Scrubs about this.

https://youtu.be/0RGCWPtKIhM

The PR isn’t public yet (it’s in my fork) but even once I submit it upstream I don’t think I’m ready to out my real identity on Lemmy just yet.

I just spent about a month using Claude 3.7 to write a new feature for a big OSS product. The change ended up being about 6k loc with about 14k of tests added to an existing codebase with an existing test framework for reference.

For context I’m a principal-level dev with ~15 years experience.

The key to making it work for me was treating it like a junior dev. That includes priming it (“accuracy is key here; we can’t swallow errors, we need to fail fast where anything could compromise it”) as well as making it explain itself, show architecture diagrams, and reason based on the results.

After every change there’s always a pass of “okay but you’re violating the layered architecture here; let’s refactor that; now tell me what the difference is between these two functions, and shouldn’t we just make the one call the other instead of duplicating? This class is doing too much, we need to decompose this interface.” I also started a new session, set its context with the code it just wrote, and had it tell me about assumptions the code base was making, and what failure modes existed. That turned out to be pretty helpful too.

In my own personal experience it was actually kinda fun. I’d say it made me about twice as productive.

I would not have said this a month ago. Up until this project, I only had stupid experiences with AI (Gemini, GPT).