None of the opinions described in this thread can fix the problem of ultimately having too many or too few commits, whatever norms are enforced. Squashing errs toward too few, not squashing errs toward too many. Probably the ideal is that a PR has meaningful, thoughtful commits which each contain a coherent, self-contained increment of functionality.
You could simply choose a short TTL, or your tool could check for e.g. "some-name._sshkeys.whatever.tld" as well as "_revoked.some-name._sshkeys.whatever.tld" to handle revocation instantly
IIRC judges aren't exactly lining up to throw the book at the feds when they misbehave. I'd love to to hear from someone more well informed though -- do judges just look the other way?
I think Strong Towns would suggest they should include the infrastructure involved as a point to analyze when determining root cause. For example, if a driver was speeding, could the street or road have been built in a way that better discouraged speeding?
I like this in a certain light. It's not so much a problem that PRs should be associated with tickets, it just sounds like the gatekeeping involved in getting tickets into an iteration is horribly overbearing. There _should_ be work happening that is driven by technical wants and needs, and the PO should be amenable to that.
That's only 30 kilowatts, which is really modest in terms of power demand for a commercial kitchen. And electric cooking can often deliver heat more efficiently to the cookware. Electric equivalent to 100k BTU/hr gas is not very hard to achieve.
Consumer Reports, for one, is happy to report that "No other cooking technology we’ve tested is faster than induction."
I would think a lot of the advantages of induction are really obvious, so I don't think your statement that they are "inferior to gas in every way" is particularly in good faith. No gas in a building should be obviously advantageous. Reduced ability to cause burns or fires too. Reduction of use of a potent greenhouse gas.
Look, I was a pretty crappy student in a lot of ways. But this thread has a few instances of folks implying that, especially at more "elite" schools, blatant cheating is practically routine and everyone does it. Again, I was not a model student, but it's pretty maddening to hear that. I didn't cheat to get my degree. I'd ask that you all not rationalize your cheating to the point of making your successors feel comfortable doing so, or worse, feel like outcasts for not doing so.
Put some charity donations on autopay using a dedicated credit card, then configure the card to autopay the balance every month. Or, get hyperoptimal and set it up so that your overall credit card utilization stays at 1%, which is better under the FICO system than 0%.
I just put linux on the MBP in the end. Much better docker experience. I can't believe companies elect to pay for Docker Desktop only to have it be so crappy.
I get and respect that this is true for some people, but goodness, I am exactly the opposite. I find all of their builtin software to be irritating and unobvious.
Agreed. I can't stand the feel of the MBP (16" 2019) keyboard. For one thing, it's too far to the right. But I also agree with you on the weird flat keys and soft F keys. At least mine has a real esc key. And this is purely habit & preference, but the control/option/command nonsense is infuriating. Everybody else does this the right way, get with the program Apple.
YMMV. Linux on the 2019 16" MBP has a lot of issues that make it irritating. It works, but not perfectly by any stretch. And yes the machine is nice, except for the keyboard, which is probably one of the most important parts!