Example: “skin” has multiple sounds to help decipher the word as spelled: “sss”, “sk”, “ih”, “nnn”, “iinn”.

Identifying some of those sounds in order helps a reader to sound out the word “skin”. After doing this a few times in a context that helps the reader confirm the meaning of the word they’ve just sounded out they’ll learn it outright.

From that point forward they can recognize “skin” on sight without requiring any context.

Independently wealthy folks can stay in the game longer without needing to extract a lot of cash compensation in the company’s early years.

I imagine this is a large part of why tooling and language wars are still compelling throughout decades of computing. No amount of lecturing on the joy of e.g. Rails vs. Node will really convince anyone to use an “outdated”, slow, dynamically typed language like Ruby in 2025 — even in places where it’d be a major win.

I imagine most of us here can agree that some elevate the craft and ritual to great effect while others avoid such high-minded conceits in favor of shipping whatever hits the expected target this week.

I’ve been both at different points in my career. Usually it’s a response to my environment.

I’ve heard several folks say that about Kubernetes, but in my experience the *nix core always resurfaces the second things get weird.

I’d make so many syntax errors without at least some sort of lint/build step.

May as well ask family to stop having opinions on my cooking.

This might soon prove to be A Problem for folks who reasonably yet erroneously expected that each responsible player would of course update the diagram immediately after each move.