Frog & Toad is a grown up book disguised as children’s book. I very much enjoyed reading it to my boys.

Hard no buddy. Junior dev means junior code and junior judgement. Countless times we had prod issues because some dev thought the change was harmless and they didn't need review.

In the article, they specifically exclude juniors and people who are still being onboarded.

I can’t find that disclaimer in the article.

OP here. In this one the closest is probably: "I love the process at Pylon: engineers merge their own code and only request reviews if they need input, think they have a risky change, or are still onboarding. "

But I fully agree that for juniors it makes sense to have it mandatory.

Sorry I’m too paranoid about this stuff.

I couldn’t get past ”Paste the private key file id_ed25519 into the .git directory of your current repo,”

I stopped worrying after I began protecting all keys with a passphrase.

Then the access of your git repos is protected by a single factor, the private key, since the private key is already in the wild.

Copying a private key on a removable storage or to another device than the device that generated it is never a good idea.

I protect mine with GPG for SSH authentication.

The only use of the passphrase is to give you time to rotate out the key after it's been compromised. It's not meant to be your main line of defense

Take Counterexample #2. Add n5 as another arrow from n3. That looks like a legitimate use case to me.

Anything technically interesting you can share about any of these?

How do you decide on which parts to extract?

What models do you use for the features you listed?

Sure, here’s what I can share: we use Veo 3, and Sora 2 is coming soon. For captions, we rely on FFmpeg combined with our own speech-to-text and dynamic subtitle API.

Good faith and common sense is being violated. That’s a valid point here.

Good faith ended at sale and support. Common sense isn’t at play because who is going to host installation media for eternity? No. There’s a nothing burger here.

Who mentioned eternity?

You criticize the initiative because you judge it doesn't have impact on the product or business. I would challenge the assumption with the claim that a sense of acconplishment, of decision-making and of completion are strong retention and productivity enhancers. Therefore, they're absolutely, albeit indirectly, impacting product and business.

Just because you can't measure the loss of customers who are turned off by your buggy product doesn't mean they don't exist.

If the only tool you know is a hammer, everything starts looking like a nail.