svtdragon

joined 1 year ago
[–] svtdragon@lemmy.world 1 points 3 weeks ago

Cursed.

Shadow & Bone (but what I really want is the six of crows spinoff).

WoT.

Dead Boy Detectives.

[–] svtdragon@lemmy.world 1 points 1 month ago

All Trump has done is fire people and write executive orders. And he's had a largely friendly Supreme Court.

[–] svtdragon@lemmy.world 2 points 1 month ago (3 children)

They had a 60 seat majority for like 8 months before Kennedy died. And as noted by other comments, one of those votes was a "no" if they tried to do any better.

But it was also partly a victim of Obama's early policy of negotiating with himself to try and appear bipartisan. It took him too long to realize the GOP isn't a good faith opposition party.

[–] svtdragon@lemmy.world 6 points 1 month ago (1 children)

"Heulyn" pronounced Hay-lynn.

[–] svtdragon@lemmy.world 7 points 2 months ago (2 children)

/c/toiletobserving

[–] svtdragon@lemmy.world 25 points 2 months ago* (last edited 2 months ago) (3 children)

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).

[–] svtdragon@lemmy.world -2 points 3 months ago (1 children)

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.

https://www.militarytimes.com/news/pentagon-congress/2018/10/17/troops-see-rising-political-tension-in-the-ranks-poll-shows/

[–] svtdragon@lemmy.world -2 points 3 months ago (4 children)

The military skews right. Strongly. That's a big part of the problem.

[–] svtdragon@lemmy.world 1 points 3 months ago

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.

[–] svtdragon@lemmy.world 3 points 4 months ago

I always heard it as One Rich Asshole. TIL

[–] svtdragon@lemmy.world 1 points 5 months ago

I run massive, global kubernetes clusters in AWS for a company you've probably heard of. There is no queue of clean VMs--not like you're thinking anyway. And provisioning a new node can take Too Long under not-all-that-uncommon scenarios.

The next best option is overprovisioning the cluster, but even 1% overhead has big costs at this scale.

[–] svtdragon@lemmy.world 6 points 5 months ago (2 children)

For large scale compute clusters with elastic load I absolutely care. The difference between one and five minutes of boot time when I ask for a hundred new instances to be provisioned is huge in terms of responsiveness to customer requests.

view more: next ›