While I agree with the sentiment, I also feel the reverse is true.
A lot of companies are hiring specifically for AI/ML at the moment, because it's the current thing. Performance and efficiency of their applications are somehow seldom prioritized.
That would require the tool to prove the equivalence of the two programs, which is generally undecidable. Maybe this could be weakened to preserving some properties of the program.
> You are now planning to build your next big system as a state machine,
Often people don't actively decide to write a state machine, but do so anyway.
I think the big takeaway of FSMs is how to recognize them in an idea or implementation and actively using them as a nice abstraction.
Not exactly, git creates a snapshot of the working tree for every commit.
The clever bit is that the object store stores files by their hashes, so if two snapshots have identical files they won't be stored twice.