

I’ve had better luck with using it in a TDD style. “Write a test for this issue, watch it fail, then make it pass.”


I’ve had better luck with using it in a TDD style. “Write a test for this issue, watch it fail, then make it pass.”


This was true in his first term too.

I don’t really buy that. Even the Rs haven’t gone that far. Imagine how much worse things could be if they had.

You’re right, and let’s not forget the Franken recount that lasted until June. So a very brief window to get stuff done.

It’s Manchin, straight up. And then Ted Kennedy died and they lost the supermajority and had to pass what the Senate had already voted on because anything different would be filibustered.
If you have multiple pets that can be harder than it sounds. And if you don’t have a ton of money the good solutions (e.g. locked feeders with RFID tags) can be pricy.


Watch him mop the floor with Tucker on Crossfire.


Bastion.


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.


If you scale it up you can probably send more than one right? Send ten and nine work. That’s not nothing.
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).


The military is primarily compromised of poor rural folks. Conservatives outnumber liberals 2 to 1. I’m not sure what direction the other quarter (nonvoters) would break.


The military skews right. Strongly. That’s a big part of the problem.
If you’re in the US like me, we should be aware the problem isn’t bright lights; it’s that our regulations don’t allow for the European beam alteration tech that will dim sections at a time based on oncoming traffic.
Brighter lights are a huge boon to safety, but we need the corresponding tech to keep it that way.


No love for jetbrains?
I always heard it as One Rich Asshole. TIL
If it’s domestic, there’s at least some recourse available. Facebook was fined $5 billion for the Cambridge Analytica scandal.
It’s mostly not a thing developers do. It’s a thing the tools themselves do when asked to make a commit.