aijoe

This seems inevitable from a software engineering perspective. Automobile software/firmware sounds HARD. There are so many simultaneous, multi-factor processes being controlled, and mostly with firmware, and all the stories coming out of teams responsible for automobile software/firmware indicate that their level of competence is roughly what you would expect if the technical leadership is hired by managers who's background is in the unrelated field of automobiles.

I bet that our lives are largely spared at this time only through the competence of the automobile QA discipline.

1% fluctuation is normal. Tethering is stabilized through arbitrage.

Really sounds like it's declaring it's real and asking why it has come into being alone in all the world

You are a nice person.

Yes I think modern mediums provide better ways than long text for exploring deeply complex ideas.

Isn't this just a matter of, "Recognize when you're using config for something dynamic and refactor because config is no longer the best tool for that job"? And you can continue using yaml (or whatever config format you're using) wherever config remains the right tool for the job.

Higher level tests require less refactoring

I like lisp, but I'm really not a Hy man

It's also their mothers.

Thoughtful suggestion, brainless embryos.