Got it, thank you for that explanation. I completely agree that we can eliminate all kinds of erroneous behaviors with better type systems. > good luck with a legacy microservice architecture in a few years. And it…
I imagine an implementation of this is equivalent to writing code and tests with the same level of detail as one might today. Language features put constraints on the solution, but do not reduce the essential complexity…
Not quite. Dropping a column or updating a row is typically irreversible.
I took an interest in programming in high-school and ran into Todd (mentioned in the article) in the lobby of an online first-person shooter. The topic of programming came up, and I explained where was at in this whole…
Got it, thank you for that explanation. I completely agree that we can eliminate all kinds of erroneous behaviors with better type systems. > good luck with a legacy microservice architecture in a few years. And it…
I imagine an implementation of this is equivalent to writing code and tests with the same level of detail as one might today. Language features put constraints on the solution, but do not reduce the essential complexity…
Not quite. Dropping a column or updating a row is typically irreversible.
I took an interest in programming in high-school and ran into Todd (mentioned in the article) in the lobby of an online first-person shooter. The topic of programming came up, and I explained where was at in this whole…