Unit testing with 100% coverage is a red flag for me, someone spend insane amounts of time writing tests for useless shit.
Integration tests are the ones that determine whether stuff actually works, have more of them. There's no point in having a test to see if pushing a button produces the correct event if there is no integration test to see if pushing the button does what it's supposed to do in the backend.
There was plenty of very well written software in existence at that point. Large applications, operating systems, databases, games, embedded applications etc. etc.
That's not to say there's anything bad about unit tests just like there's nothing bad about the Agile principles. They don't prove your code works though, that's not really possible. A useful tool- sure.
It might be good to write them as you’re bringing up new code, but deleting the useless ones after that could be an improvement.
I've worked in more recent times on software that was used by millions of people, was extremely reliable, and didn't have a lot of unit tests. We did have other forms of automated testing though.