radlad

As a native English speaker, I worry about picking up LLM-speak simply due to interacting with Claude Code all day.

I'm sorry to hear that's how it's going at your work.

The best engineers hand-edit .git

Edit: But actually, one of my favorite Git explainers is https://wildlyinaccurate.com/a-hackers-guide-to-git/

Considering most teams have only switched to heavy AI use in the past few months, the verdict is still out on this.

That said, I've had lots of success using AI to learn, refactor and clean up codebases.

I notice another trend were a lot of AI naysayers haven't really spent a ton of time getting intimately familiar with AI.

Definitely not - the biggest risk with this increased speed is going full-bore in the wrong direction. A product mindset (and a critical eye to architecture) matters more now than ever.

I use LLMs for exploration and for review, but I write the code myself. I find it hard to believe why so many engineers try to avoid it. It’s not consuming much of my time. And it’s actually the most enjoyable part.

At my workplace, there is more work to be done than there is engineers, and approximately 2 engineers per service. I can spin off multiple Claude Code instances on unrelated work, steering them occasionally, and then finally reviewing the output. After I have reviewed it, I post it for team review.

You're absolutely right that my depth of familiarity is lesser with this code, but we are absolutely shipping more as a result of increased parallelization.

The bottleneck now is typically reviews - both pre-push and team reviews.

I find project-wide or subpackage-wide (for sufficiently large projects) CLAUDE.md's that document patterns (including for tests) solves this.

/init will make a project-wide one, or you can instruct it to "Create CLAUDE.md in any sub-directory that is sufficiently complex" then modify from there.

I don't expect that would be the case. This is what's called BLUF or Bottom Line Up Front: https://en.wikipedia.org/wiki/BLUF_(communication)

The model will still have read the entirety of the document before composing its response. And I believe that even in auto mode, there are thinking tokens behind the scenes.

I could be crazy, but don't all the external antennas allow for more flexibility with regard to directionality of signal?

I have a U7 Lite and it is very directional compared to other routers I have used (spider style, trash can style, etc.)

Seems kinda weird - it's cognitive load I'd love to avoid. If I'm going to take it on, I might as well try other providers.

I can empathize with this view but I've also seen one line clear bug fixes rejected because CC signed off on it.

There's no other correct fix - why do you care which pen I used to write it?

What fundamentals are those?

This sounds like what regular commit messages do. How are conventional commits specifically helpful?

As I recall, Amazon also famously didn't turn a profit for ages - but they were also capable of turning one much earlier than they did.

Are AI companies capable of turning a profit today if they turn some knobs?

Regarding seed ratio, generally by perma seeding. Many private sites either use seed time requirements instead of ratio or offer bonus points for seed time which can be exchanged for ratio. But also as new editions and formats are released, the library has a bit more turnaround than your music sites of yesteryear.

Out of curiosity, what movie?

hey there's a project idea: a "todo list" for rippers that scrapes imdb and checks what's not in pirate ba

Private sites do things like this, archival efforts and have request systems.

Don't want to name drop, but this is unfortunately a real phenomenon.

Counterpoint: I've done 3 and all went through without drama.

1. Tell it to find docs and research best practices.

2. Ask for references and read them.

When done properly your own knowledge should have grown to meet the product you end up with.

A mobile phone?

It just means people pick up their phone instead.

The position they took sounds much more politically feasible than the one you suggest they should've taken, at a time when the White House was threatening them with the Defense Production Act.

You seem to be responding to OP line by line instead of understanding their overall point.

OP doesn't appear to be saying Catholicism ought not to grow - rather that they believe trying to appeal to a wider audience than that which is already interested in religion is likely to fail, or worse, backfire.

They simply function in whatever way they "consider to be valid".

No, they would function in the manner courts deem to be valid.

I find in these cases the best option is to provide references, docs, etc. If you'll need them regularly, save them to Markdown files.

And domains can change hands legitimately.

Like some kind of UI over a database scraped by code which understands Github, Forgejo, Gitlab, sr.ht, etc?

One issue is that issues tend to be monotonically increasing numbers, and references to old issues vs. new issues get confusing over time.

People can indeed form cooperatives to handle the protection, but this is hard to manage globally as an entity.

This is a fascinating idea. Is this something anyone is working on?

Right, it already is that, and adding shared trash bins won't make it not that.

But it will change participant behavior. Most attendees work very hard to reduce the amount of trash they generate at a burn, period. This is why people bring reusable cups and plates and silverware, etc. If you provide trash services, people will be more willing to bring trash - after all, it's easy to dispose of. And this violates the LNT principle.

Can't wait to use it as a mouse for my Windows-based couch gaming PC.