You are absolutely correct. I have no idea where all of this animosity towards stainless steel cookware is coming from. It’s an absolute workhorse and doesn’t need princess treatment like cast iron or carbon steel.

I cook vegetable dishes all the time in stainless steel. Works fine. It all comes down to technique and heat control.

When the pan heats (and expands), its microscopic gaps close up. If foods are added before this happens, it pinches and traps the food causing it to stick.

Abstractions aren’t concrete and all of these standards you’re referring to are concrete data serialisations. You may be interested in CUE which captures this concept in its design.

You’re doing it right by avoiding as much of Gitlab’s CI features. I’ve seen versions where scripts are inlined in the YAML with expressions in random rule fields and pipeline variables thrown all over the place. And don’t get me started on their “includes” keyword, it’s awful in practice, gives me nightmares.

Then I write a Kubernetes manifest in YAML with JSON schema validation and the heart rate goes down again.

Bay leaves contain several different fatty acids which, when cooked, are transferred into your food. Fatty acids have a large effect on the flavour and nutrition of food. Next time to cook plain rice, add a few bay leaves to the pot and you will notice the change in flavour.

Neon is the only one that I think is passable. The rest are a bit too stylized for code. The texture healing is a great idea though, I would love for that to be common.

Edit: Actually I’ve changed my mind. Texture healing would introduce too much variation in similar texts. If spacing is a problem then maybe the font is simply no good.

Comic Code is a thing and it’s 10/10. It’s proof that handwriting style fonts for code is possible.