Higher level than Rust, lower level than Go.

That’s a great introduction. Having written both I completely understand your meaning.

Have I missed the “AI did/n’t help with my compiler” article?

Any feed and tack store have horse stall mats. Cheap and effective. Ex-CrossFitter here to say don’t waste any money on named brand for this.

Plausible yet wrong. This phrase captures a lot.

I’ve done this and … increased my font size in my editor. Both because my old age eyesight is worsening but also I’ve realized having “whole file visible” was decreasing my ability to focus on specifics of logic. Wasn’t expecting my focus to improve because there are fewer lines on screen.

Ironically this iteration of yarvin is what turned a family member around from the deep end. Their recent discovery of this led to this comment: “wow that’s lunacy” and a swift change to their perspective. I wish it didn’t require all the trouble and tragedy in some cases.

This is an incredible opening line to a short story.

In my recent experience profit is the metric that’s an aggregate of others, like lead time. Lead time usually improves when employees control it. Sometimes this gets confused as ill-concern for profit because it’s indirect. I’m still not great at expressing this to leadership.

Which line represents the “fire department”?

I remember Doc Ozone (ozones.com). To this day I’m not sure I know who that is, but back then that site taught me more than all the books I read about JavaScript.

Yes certain types of code. But that’s not the zeitgeist right now. It’s more like “build your business software” or “improve the quality of your enterprise code”. And those are definitely not the “write once” type. I appreciate the nuance and wish it were more pervasive.