3 Matching Annotations
- Mar 2021
-
github.com github.com
-
This is a copy of the "AMD" document in the repo, kept here to maintain historical links. If this document differs from the one in the repo, the repo version is the correct one.
Why not just make this document empty (besides a link) and link/redirect to the canonical version?
That way it is impossible for them to disagree.
Tags
- make it impossible to get wrong/incorrect
- I have a question about this
- canonical version
- avoid duplication
- maintaining redirect/copy at old URL in order to maintain historical links (broken links)
- avoid duplication: impossible for them to disagree/diverge if there's only one version/copy
Annotators
URL
-
- Feb 2021
-
dry-rb.org dry-rb.org
-
In other words, once you've used Maybe you cannot hit nil with a missing method. This is remarkable because even &. doesn't save you from omitting || "No state" at the end of the computation. Basically, that's what they call "Type Safety".
-
- Oct 2020
-
meta.stackoverflow.com meta.stackoverflow.com
-
Looking at all those bearing, heading, orientation, navigation, position, direction, etc. I think we have a bigger problem here. Someone has decided how to use tag (e.g. orientation is about page orientation), but there are 100 other cases. Imho, to disallow misusing there should be no "heading", but rather "html-heading", "gps-heading", "whatelse-heading", which make mistakes impossible. So yes, "heading" should go.
-