You might be surprised. Yours sounds like the attitude of someone who has not had the luxury of reviewing well-constructed commits. PRs with intentional commits permit both faster and deeper reviews—but alas, not everyone is so respectful of their reviewers’ time and energy.
> Yours sounds like the attitude of someone who has not had the luxury of
Sometimes when people speak rhetorically I'm baffled because I feel they literally do not understand what they're saying because they end up supporting an opposing rhetorical purpose. Yes you're 100% correct well-structured commits are a luxury that most of us do not have the privilege of experiencing because we work in high-pressure, deadlines driven environments where no points are awarded for beautifully crafted commit messages.
So in effect your argument is like "people that haven't had the luxury of a Michelin star restaurant don't appreciate amuse bouche and they should strive to rectify that".
Yeah, exactly. It seems like you understand just fine.
You claimed that “literally no one” has a different review workflow than yours. I do, and my experience is that clear commits make reviews both faster and deeper, which is very helpful specifically in a high-pressure, deadline driven environment where being slow and wrong is costly. You’re of course free to disagree and work differently.
You gotta go slow in order to go fast, and utterly useless commit messages and inappropriate commit sizes will bite you in the ass. They don't have to be the most beautiful commits ever, but ideally there's a minimum standard we can all live up to.
To use restaurants as the analogy, Michelin star-grade dining might be unavailable, and we might have to live the Olive Garden, or even McDonald's life. Regardless of which restaurant we're at though, if the food is moldy and gross, we shouldn't eat it.
I grew up about 3 minutes away from a big hardware store, doing projects all the time. This contributed to a very wrongheaded idea about how long projects take.
When I moved into my current house it was suddenly a 40 minute trip. For the first couple years I couldn’t get anything done on Saturdays because I’d never needed to optimize away trips to the store before.
I wrote a thing for this back when you could download the whole hash database as a single torrent, but I haven’t checked it since they moved over to the PwnedPasswordsDownloader system. This doesn’t use any probabilistic data structures though, it just packs the database into the smallest binary file I could come up with.
I don’t know that much about materials science. Why is a “titanium hemisphere bonded to a carbon fiber cylinder” “such a fundamentally compromised design” in this application?
I imagine maybe carbon fiber would be better in tension (e.g. airframes) than in compression (this), perhaps. Or do carbon fiber and titanium not get along somehow?
Because engineering a competitive GPU takes massive resources. Why pour resources into Quantum computers when you're loosing the battle on CPU and GPU side? Buy the time Quantum computer become mainstream Intel might not survive, if they don't pick their battles wisely.
Always neat to discover that multiple high-quality tools you discovered separately are all written by the same person. I use both bat and hyperfine regularly and had no idea. Now, knowing to look up the author, I've learned about insect and hexyl too!
Fabrice Bellard, klauspost, and bradfitz are three prior examples of this that spring to mind. I'm sure there are plenty more I haven't noticed yet.
Sincerely, thanks to the people who make contributions like this.
pv is invaluable but my issue with it is it’s only useful if you think to include it before you run the command. Usually the thought doesn’t occur to me until I have some runaway cp or dd and I want to be reassured that it’s going to be done soon. For that case that this looks super interesting.
