18 Matching Annotations
  1. Mar 2025
  2. Jan 2025
  3. Dec 2024
    1. Over a 10-year period, up until three weeks before his death, we exchanged 150 letters. After Oliver passed away, I had to find a way to handle my sadness. So, I revisited all our letters and wrote a new book, Dear Oliver: An Unexpected Friendship with Oliver Sacks, as a tribute to exploration, letter-writing, friendship, and Oliver Sacks.

      for - book - Dear Oliver: An Unexpected Friendship with Oliver Sacks - from Psychology Today website - article - What Oliver Sacks Taught Me - Susan R. Barry - 2024 - Jan. 23 - to

      to - book - Dear Oliver: An Unexpected Friendship with Oliver Sacks - Susan R. Barry - 2024, Jan 30 - https://hyp.is/6ir6jME9Ee-vLEu_PiRFsw/theexperimentpublishing.com/catalogs/winter-2024/dear-oliver/

  4. Oct 2024
  5. Sep 2022
    1. Indicative of howclose many Americans are to poverty, a recent study by the Federal ReserveBank found that 37 percent of Americans do not have enough savings put asideto protect them from a $400 emergency.20
      1. Federal Reserve Bank, “Report on the Economic Well-Being of U.S. Households in 2019” (Washington DC: Board of Governors of the Federal Reserve System, 2020).
    2. Driving this home, a recent FederalReserve survey found that 37 percent of Americans cannot cover a $400 unexpectedexpense with savings or its equivalence.

      I've read this statistic many times, but where is the original source?


      It's here: Federal Reserve Bank, “Report on the Economic Well-Being of U.S. Households in 2019” (Washington DC: Board of Governors of the Federal Reserve System, 2020).

      This fact is repeated several times throughout the book. At least 3 by my count.

  6. Nov 2021
    1. Seems related, currently there's no way to enforce that object should have attribute values of specific type only. Example: I want to define an abstract Table Row, basically any object limited to attribute values as primitive types. But it doesn't work // Table row export type Row = Record<string, string | number | undefined> // User interface User { name: string } const jim: User = { name: 'Jim' } const row: Row = jim // <== Error
  7. Sep 2021
  8. Mar 2021
  9. Feb 2021
  10. Aug 2020
  11. May 2020
    1. Unexpected features “Unexpected” features are those that are unrelated to the add-on’s primary function, and are not likely from the add-on name or description to be expected by a user installing that add-on. Should an add-on include any unexpected feature that falls into one of the following categories: Potentially compromises user privacy or security (like sending data to third parties) Changes default settings like the new tab page, homepage or search engine Makes unexpected changes to the browser or web content Includes features or functionality not related to the add-on’s core function(s) Then the “unexpected” feature(s) must adhere to all of the following requirements: The add-on description must clearly state what changes the add-on makes. All changes must be “opt-in”, meaning the user has to take non-default action to enact the change. Changes that prompt the user via the permissions system don’t require an additional opt-in. The opt-in interface must clearly state the name of the add-on requesting the change.
  12. Dec 2019
  13. Jan 2019
  14. Oct 2015