12 Matching Annotations
  1. Sep 2022
    1. need to be united in one single place

      often repeated advice, especially in the modern period.

    2. The rigidness and immobility of the note book pages, based on the papern stamp andimmobility of the individual notes, prevents quick and time-saving retrieval and applicationof the content and therefore proves the note book process to be inappropriate. The only tworeasons that this process is still commonly found in the studies of many is that firstly they donot know any better, and that secondly a total immersion into a very specialized field ofscientific research often makes information retrieval easier if not unnecessary.

      Just like Heyde indicated about the slip box note taking system with respect to traditional notebook based systems in 1931, one of the reasons we still aren't broadly using Heyde's system is that we "do not know any better". This is compounded with the fact that the computer revolution makes information retrieval much easier than it had been before. However there is such an information glut and limitations to search, particularly if it's stored in multiple places, that it may be advisable to go back to some of these older, well-tried methods.

      Link to ideas of "single source" of notes as opposed to multiple storage locations as is seen in social media spaces in the 2010-2020s.

    1. As a reminder, the JSON Schema is not the source of truth for the Specification. In cases of conflicts between the Specification itself and the JSON Schema, the Specification wins.
    1. As a reminder, the JSON Schema is not the source of truth for the Specification. In cases of conflicts between the Specification itself and the JSON Schema, the Specification wins. Also, some Specification constraints cannot be represented with the JSON Schema so it's highly recommended to employ other methods to ensure compliance.
  2. Jan 2022
    1. Oh, I just figured out a workaround for my project, in case it helps someone. If you want the source of truth on the prop to come from the child component, then leave it undefined in the parent. Then, you can make the reactive variable have a condition on the presence of that variable. eg: <script> let prop; $: prop && console.log(prop); </script> <Child bind:prop/> Might not work for every use case but maybe that helps someone.
  3. Oct 2020
    1. In the next major, we'll start copying the ref onto both the props and the element.ref. React will now use the props.ref as the source of truth for forwardRef and classes and it will still create a shallow copy of props that excludes the ref in these cases. At the same time, we'll add a getter for element.ref in DEV that warns if you access it. The upgrade path is now to just access it off props if you need it from the element.
  4. Aug 2020
    1. Do not include the same information in multiple places. Link to a SSOT instead.
    2. There is a temptation to summarize the information on another page. This will cause the information to live in two places. Instead, link to the SSOT and explain why it is important to consume the information
  5. May 2020
    1. Code Owners allows for a version controlled single source of truth file outlining the exact GitLab users or groups that own certain files or paths in a repository.