We mostly use figma for brainstorming and RICE-scoring, which can be hard work. Hence my lukewarm reaction. My other reaction was "cool, how’d he do that".
What's the purpose of having this at all?
If you used the car as an analogy instead, it would make more sense to me. There were car craftsmen in Europe that Toyota displaced almost completely. And software is more similar to cars in that it needs maintenance…
At work we use it heavily. You don't really see "a zillion interfaces" after a while, only set of dependencies of a package which is easy to read, and easy to understand. "makes it hard to cone up with good names" is…
[dead]
I've always viewed type systems as adding constraints on and descriptions to the data and logic in the system. Which is exactly what you find a ton of in electrical engineering (e.g. IEEE C37.2 and gazillion more).
We mostly use figma for brainstorming and RICE-scoring, which can be hard work. Hence my lukewarm reaction. My other reaction was "cool, how’d he do that".
What's the purpose of having this at all?
If you used the car as an analogy instead, it would make more sense to me. There were car craftsmen in Europe that Toyota displaced almost completely. And software is more similar to cars in that it needs maintenance…
At work we use it heavily. You don't really see "a zillion interfaces" after a while, only set of dependencies of a package which is easy to read, and easy to understand. "makes it hard to cone up with good names" is…
[dead]
I've always viewed type systems as adding constraints on and descriptions to the data and logic in the system. Which is exactly what you find a ton of in electrical engineering (e.g. IEEE C37.2 and gazillion more).