> What's a 20% productivity gain if I constantly feel deflated by work that used to energize me? That's going to give back the productivity gain and more, while also decreasing my quality of life.
This has been the story of humanity since the industrial revolution.
> This is why I use rebase before PRs, and despise squash. You are not going to remember why you wrote that code that way 2 years from now and all we'll have to understand bugs and identify Chesterton's Fence situations is the deltas and the commit history.
This forces people to work in a very linear fashion that doesn't match how people actually work.
A 400 line commit from a squashed PR should be very manageable when tracing a bug in the main branch, especially if the PR has a good description and review. Having a bunch of "fixed, added, deleted" commits all pushed into main seems like a disaster of noise unless you now force everyone to bundle perfectly reversable actions in every commit.
> Having a bunch of "fixed, added, deleted" commits all pushed into main seems like a disaster of noise unless
unless you skip non-merge commits when reading the history of main. And personally, I don't remember needing to read main's history more often than probably once a year, and even then mostly out of curiosity.
Also: having a bunch of "ticket resolved" commits all pushed into main seems like a disaster of noise, compared to simple "release 203", "release 204", etc. series of commits that comprise the main. Squash even further! Just as you don't need to track every small development change inside a feature request, you don't need to track every small feature or fix inside a full release. Right? You write a changelog (if you even write them) using those 400 merge-commits, then squash it into a one commit for you release, bang, clean history.
> And personally, I don't remember needing to read main's history more often than probably once a year, and even then mostly out of curiosity.
You're probably delegating that work to someone like me who actually figures out what the systemic problem is that caused the same class of bug to make it to production 5 times in the last 3 years. If you're a lead or a principal and still saying this ^ then you need to expand your skillset.
Bad luck doesn't happen very often. Mostly it's blindspots.
I will confess though that the sort of forensics I do is probably not divisable from the fact that I'm also the designated VCS surgeon on every project I've been on since 1998.
I'm saying get rid of those before you invite people to look at the code. Keep the 'code review changes' one because that's comedy gold when the PR changes forced on you by some snowflake actually cause a production outage at 2:00 am.
Honestly, I think if more people actually used git enough that they understood how the git graph worked, we'd have fewer busted graphs. Like CI, you only get better at the tools if you use them more. And people are avoiding using git features and hoping nobody notices when their journeyman standing bites the rest of us on the ass.
We notice, we just reduce your trust level instead of confronting you. I can think of a lot of things that get bitched about over lunches or coffee much more often, but you're still being complained about.
Also - at least in GitHub if you squash with the PR merge action in the UI - the original commit history is still available in the ref maintained by the closed PR yet doesn’t clutter your branch or tags namespace.
One of the major attack vectors is distillation, where millions of questions are auto-generated and coordinated to produce training data for new LLMs. Anthropic alleges Minimax, Deepseek and Kimi were trained this way. Deepseek 4 compares favorably to Opus, so they're probably trying to prevent Deepseek 5 from being a bootleg Mythos. https://www.anthropic.com/news/detecting-and-preventing-dist...
It takes a lot of audacity to train on all the data you can without any license, attribution, etc and then act like you can own the outputs of the model so that someone else doesn't make a model from your data without a license. I've lost a lot of respect for Anthropic in the last 24 hours.
Everyone knows it's bullshit but because these companies are being valued at a trillion dollars a piece, it's hard to say that if you were in their shoes you'd do any differently.
This may surprise the cohort on hacker news but there are large amounts of people on this planet that value things beyond money like ethics or having principles. Excusing absolutely repugnant behavior because of money to be made is so deeply antihuman, but then again most people working at LLM companies are deeply antihuman to start with.
> but then again most people working at LLM companies are deeply antihuman to start with.
I agreed with you up til this point, but this isn’t true and isn’t called for, and doesn’t strengthen your otherwise good point, in fact it weakens your point to make statements like that. Most people who work at LLM companies, like most people who work at most companies, are making a living and have the same ethics and principles as anyone else. I don’t know where you work or live, but don’t forget the exact same logic and exact same hyperbole is being used to make the same claim about people in tech, and the same claim about Americans and Europeans.
No it's totally called for. This is technology that is literally ruining, destroying, and killing lives. Especially in regards to how US companies are operating with this tech. It's a valid claim, "just following" orders has never been a valid excuse.
These people just care about chasing the bag rather than doing right by their fellow humans. In their mind clearly some humans are more equal than others.
edit: to reiterate, the people choosing to work at these companies care more about becoming millionaires and chasing generational wealth rather than maybe questioning if the machine they are building may be producing terrible outcomes. They can work at any company on this planet easily, stop running coverage for FAANG workers that have always shown disdain for their fellow humans, they choose to work at the misery death machines because they simply do not care about the destruction they have wrought about the world.
You can say that but Anthropic are literally the "good guys" that were disgusted by Altman and co, yet even they seem to have sold off their morality. Absolute money corrupts absolutely.
They are not the good guys and never where. They where fine with the Claude being used to plan the murder of people and spying on people as long as they where outside the USA. That is not something "good guys" do, thats what sellouts do. Everyone working at these companies, who where paid small fortunes to ignore any feelings they might have. Hopefully we get a modern version of the nuremberg trials when this madness in the USA is over and we the people will then judge everyone involved.
Distillation is not an "attack", despite Anthropic themselves coining the self-serving phrase "distillation attack". And as others have noted, it is precisely identical to the sort of "attack" on published works which Anthropic themselves used to train their models.
> Anthropic alleges Minimax... were trained this way
I've had some sessions this week with MiniMax M3 where it insisted it was Claude, even though there was no mention of Claude in any system prompts or context I gave to it, and it was running in my own API harness (not Claude Code).
Though I also wouldn't be surprised if "I am claude" is just the new "I am Mozilla/5.0 AppleWebKit KHTML Like-Gecko Chrome Safari".
CEOs are probably the most replaceable position, period, by human or AI. Everyone just gives them information. They don't know any information themselves.
Problem is, a CEO can fire employees, find out it was a dumb decision, then leave with a million dollar severance package. So they don't really care when they're wrong.
> Anthropic has a post about using either a light model call or other logic (regex etc) to dynamically decide what tools to expose per incoming request.
How? Using the agent SDK or Claude Code? If the latter, it'd be nice if they figured that out. There's a huge amount of quality of life things missing from Claude Code. It's a pretty raw frontend to the backend models. And either Claude Code or the backend models get convinced they don't need skills they've been asked to read or even built-in capabilities like reading PDFs.
reply