Your workflow makes sense for FOSS projects, where the commit is the unit of work. In my experience, on most professional teams, the PR is the unit of work. PRs trigger CI/CD pipelines. PRs map to tickets. The meaningful commit goes with the squash merge to the shared dev/main branch.
There are cases where I've staged commits this way for a PR, to make it more reviewable. I'd usually rather split them off into separate PRs, but when that would create a pipeline of three MRs that are meaningless on their own, then rewriting history for a single MR makes sense. I generally consider my feature branch's commit history to be for me, not for you. Going back and rewriting history is a chore that shouldn't be necessary if I did a decent enough job with the PR description and task decomposition. Those commits are getting squashed anyway. Along with all the "fix MR comments" commits on top of it.
It wouldn't bother me to adopt your workflow if it fits your team and its tools and processes. I'd just say, consider that your way isn't the only correct way of doing things. Your preferences are valid, but so are others'. The only thing that really bothers me is absolutism. "My way or the highway."
Your writing here reminded me of a particularly unpleasant coworker I had in the past. I quickly browsed your comment history to make sure you're not him... Excessive rigidity is not an endearing quality.
All that being said, I have also been constantly annoyed by people with too many YoE who can't be bothered to spend an hour or three to learn the basics of how the Git tree is structured, and what merge vs rebase does. They rely too heavily on their GUI crutches and can't fix anything once it goes sideways. Even when you lead them to water, sending them reading material and offering to answer questions after, they refuse to drink. Willful ignorance is far more irritating than stubbornness. I don't expect them to be able to remember what bisect vs cherry-pick does. Claude will spit out the subcommands for them if they can describe what they need in English. But they can't do that if they have no understanding of the underlying data structures...
I guess the AI companies finally figured out they’re supposed to buy their stolen datasets from a shell company spun up by the most unsavory character within two degrees of the CEO. Every CEO has a drug dealer, and every CEO drug dealer knows the greasy grey hat dude running a data laundry “startup.” The VCs usually know some private equity dons who run the same racket to do bust out fraud, too.
It’s truly unbelievable that OpenAI and Anthropic were so sloppy. Pirating all that copyrighted media and not even bothering to hide behind one layer of indirection. Amateurs.
So yeah… it’s what, five years’ worth of pent up demand for organized crime, hitting the market everywhere all at once? I’m surprised the request volume isn’t higher!
FAA ought to be drowning Kegseth’s DoD in bureaucracy at every possible opportunity, after the massacre over the Potomac River a year ago. They deserve no leniency whatsoever.
Why does everything have to be in the TUI? I like the TUI. But I also want all the logs. And I do mean all of them.
Of course all the logs can’t be streamed to a terminal. Why would they need to be? Every logging system out there allows multiple stream handlers with different configurations.
Do whatever reasonable defaults you think make sense for the TUI (with some basic configuration). But then I should also be able to give Claude-code a file descriptor and a different set of config optios, and you can stream all the logs there. Then I can vibe-code whatever view filter I want on top of that, or heck, have a SLM sub-agent filter it all for me.
I could do this myself with some proxy / packet capture nonsense, but then you’d just move fast and break my things again.
I’m also constantly frustrated by the fancier models making wrong assumptions in brownfield projects and creating a big mess instead of asking me follow-up questions. Opus is like the world’s shittiest intern… I think a lot of that is upstream of you, but certainly not all of it. There could be a config option to vary the system prompt to encourage more elicitation.
I love the product you’ve built, so all due respect there, but I also know the stench of enshittification when I smell it. You’re programmers, you know how logging is supposed to work. You know MCP has provided a lot of these basic primitives and they’re deliberately absent from claude code. We’ve all seen a product get ratfucked internally by a product manager who copied the playbook of how Prabhakar Raghavan ruined google search.
The open source community is behind at the moment, but they’ll catch up fast. Open always beats closed in the long run. Just look at OpenAI’s fall into disgrace.
Maybe. I keep hearing that yet all I've seen are teens that would have been legal in several US states. Given they did not correctly redact the PDF's perhaps there will be some hints to actual children having been involved.
This is my theory as well. A google search for the late prof's name returns a .ir website at the top of the result for some reason. It's a tragic loss for the world and his loved ones as are the victims of the brown incident.
I want a BYD that costs less than a 2000 Camry did brand new in 2000.
EVs are inherently pretty simple machines. All the complexity is in the battery, and China’s crushing everyone at battery tech. It’s not even close. It’s like a human trying to beat a polar bear in hand to hand combat.
They really need to deregulate the auto industry and let us buy the Yugos with a Jetsons battery. America is a poor country now. Nobody can afford used cars in this economy, never mind new ones.
Ford announced the Maverick, it got so much excitement that it sold out and dealerships sold for over MSRP. So in their infinite wisdom they... didn't make more mid range trucks. Ill never understand these guys.
I was interested in this truck when it came out. My in laws purchased one and queued a second one up to have two reliable (new is reliable to them) in their retirement years. The price was good, its a smaller compact truck and very good on utility. The second generation of them - the price went up, and some of the value in what the truck was vanished. Its also years behind on production. Ford doesn't seem to want to sell these.
If Chevy came out with a competitive S10 Electric style truck, I'd consider it as well.
The Mavs have been caught up on orders for a while now. I got one in the spring and pretty much any trim/colour/option package was in stock locally at mildly below msrp.
The idea is that you make more profit selling 50,000 cheap trucks and 50,000 expensive trucks than just 100,000 cheap trucks. When you can fool a largely innumerate populace into 84-month loans with "cheap" monthly payments, overpriced vehicles are the way to go.
All US automakers are doing the same thing. There's gentle up-marketing collusion.
The issue at root is that auto demand is a finite, population-based amount. Automakers are all pretty good at margin and manufacturing cost control.
So that leaves the only independent variable that can influence revenue and profits as {average sold vehicle price}.
New entrants face a scale issue: it's difficult to compete with the larger manufacturers' production costs with orders of magnitude less sales volume.
Which is why you historically only saw state-sponsored new manufacturers break into the market (read: Japan, Korea, China).
Electrification turned some of this on its head, but not completely. GM, Ford, et al. can still build just enough mid-market electrics to spoil others volumes, without attempting to build something really good and cannibalizing their own luxury vehicles.
Price conscious consumers have been out of the "New" car market for a very long time. New cars have a massive premium that never makes sense.
Instead of buying a brand new Geo Metro like you would in the 90s, you just buy a used Corolla or Civic. You end up with a better car and it lasts longer anyway.
That means the majority of the "New" car market has already decided price isn't that important.
Which is why the "average" new car price is $50k and people are signing up for 80 month loans on trucks.
I paid $24k for my maverick. There were tons of dealers who had marked it up to the low 30’s and told me I’d never get one for MSRP. I said, “I guess I’ll wait.” I had to wait a whole 2 weeks.
The EV pickup obsession is so bizarre. Even moreso than the gas pickup obsession. The obvious next step was to take their brilliant EV Transit and scale up production. You don’t have to convince truck bros. There’s no cultural hang-ups. No issues with towing. Just make a nice cargo van with 120v hookups for $50k that’s easy to drive in the city and easy to convert into a camper. Could’ve built three vans with the lithium it took to build these obscenities.
And you know, I’m already compromising here, because it really ought to be a wagon instead of a van, if Detroit had any brains left.
Can’t wait until someone figures out how to smuggle those $15k BYDs in from Mexico. The North American car market needs to be disrupted badly. By China, not by some meme stock.
There are cases where I've staged commits this way for a PR, to make it more reviewable. I'd usually rather split them off into separate PRs, but when that would create a pipeline of three MRs that are meaningless on their own, then rewriting history for a single MR makes sense. I generally consider my feature branch's commit history to be for me, not for you. Going back and rewriting history is a chore that shouldn't be necessary if I did a decent enough job with the PR description and task decomposition. Those commits are getting squashed anyway. Along with all the "fix MR comments" commits on top of it.
It wouldn't bother me to adopt your workflow if it fits your team and its tools and processes. I'd just say, consider that your way isn't the only correct way of doing things. Your preferences are valid, but so are others'. The only thing that really bothers me is absolutism. "My way or the highway."
Your writing here reminded me of a particularly unpleasant coworker I had in the past. I quickly browsed your comment history to make sure you're not him... Excessive rigidity is not an endearing quality.
All that being said, I have also been constantly annoyed by people with too many YoE who can't be bothered to spend an hour or three to learn the basics of how the Git tree is structured, and what merge vs rebase does. They rely too heavily on their GUI crutches and can't fix anything once it goes sideways. Even when you lead them to water, sending them reading material and offering to answer questions after, they refuse to drink. Willful ignorance is far more irritating than stubbornness. I don't expect them to be able to remember what bisect vs cherry-pick does. Claude will spit out the subcommands for them if they can describe what they need in English. But they can't do that if they have no understanding of the underlying data structures...
reply