Now, granted, Simple Made Easy only directly addresses deciding between alternatives and knowing that your work works. It doesn't address what I consider to be the biggest problems (read: dysfunctions) in software.
This is the thing about this talk (which I think is illustrated by the replies to @hillelogram 's original comment) -- the talk is so vague that you can interpret it in many different ways. I don't think your interpretation is wrong, but I don't think it's the only one.
-
-
Your interpretation explains the "guardrail programming" thing in a reasonable way, but literally every other time I've seen that section of the talk cited, it's cited to mean that types = bad since types = guardrails = crashing, which (IMO) is an absurd viewpoint.
-
You might say that all of these other people are misinterpreting the talk, but if that many people misinterpret the talk, I think that saying that they're misinterpreting the talk is blaming the user. This is the perspective I personally have when I write, YMMV on this.
- 4 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.