Viewing profile — throwaw20221107

This is another argument why "not squashing is bad"; because it discourages people from committing.

That's fair. Both overwrite (edit: seemingly overwrite) (un)staged changes. But `checkout` requires less hyphens. I feel like all of this would be resolved if my boy Linus had rena…

Ya this is basic economics, fixed investment vs markup driven return.

>merging a sequence of PRs from same branch is bad if you squash For me in this scenario, merging `main` w/ squash commit back into PR2 branch after PR1 gets merged works here. As …

Sure but the vision/nlp models required to enable context-sensitive vision apps (i.e. an app to "give me facts from Wikipedia about what I'm seeing"), those models are closed and o…

> the truly adversarial case is rare The problem is not adversarial, or due to malice. The problem is ignorance and expediency driven by a desire to push code and little incentive …

The problem is who is doing the crafting. (And the approving.) At least squash based approach limits to 1 the number of commits an untrustworthy "crafter" can occupy.

"Victorious warriors win first and then go to war, while defeated warriors go to war first and then seek to win.”

Ratorx, do we work on the same team at google? I feel like I've heard you before?

Ok I agree, you roll back to the known working version. The easiest way to do that is revert the whole PR (or data deploy in case of flags, ofc). My point is not "flags vs. no flag…

Sure. I'm just talking about binary deploy. Of course you're gonna use flags to flight things in an industry context, depending on the company and its CI/CD practices. Let's say th…

What do you mean? Dev 1: "I would like my PR to make 2 commits into `main` instead of the 1 that everyone else gets via squash." Dev 2: "Ok then make 2 PRs."

>if a PR is broken, revert a simpler commit and just fix that I guess it differs between "library development" and "service development". When you're developing a service, what's i…

I'd argue "why a method exists" should be addressed with naming and javadocs, not in the commit message. Why split the meaning of the code between the code itself and the commit me…

Yeah, seems almost like the downfall was its openness. It's almost a kind of hubris -- he didn't need to articulate his plan in detail via a traceable comm like email, should've be…

For me it was effective writing. Simple sentences in active voice identifying clear actors and relationships. Going to apply it to my own technical writing style. Is it a work of a…

I would love to just learn about places where I go passively with AR. It won't go down this way. Wikipedia for AR will never happen. More likely it'll be thousands of ads and other…

Ya, the three arguments are 1. `|` 2. `grep` 3. `"my actual filter"`

The only reason people lose code is because 1. they didn't read this one diagram: https://git-scm.com/book/en/v2/Git-Basics-Recording-Changes-... 2. And then they run `reset --hard…