28 Matching Annotations
  1. Jun 2021
    1. Natalie E. Dean, PhD. (2021, May 4). The imminent FDA authorization of a vaccine for 12-15 year olds is great news, and adolescents should be able to access vaccine. But in the short term, we must also grapple with the ethics of vaccinating adolescents ahead of high-risk adults in other countries. [Tweet]. @nataliexdean. https://twitter.com/nataliexdean/status/1389381649314598914

  2. May 2021
    1. After 10 minutes, the word lists were collected and students were asked to write down as many of the list items as they could recall within five minutes.

      Were students asked or told if they'd be tested with this on long-term memory?

      Personally, I'd have used a simple major system method to memorize such a list for short term memory, but would have used other techniques for long term memory.

  3. Apr 2021
    1. A falsey return value from #validate will deviate the flow and go straight to End.fail_fast.

      Similar to: How, in Rails, aborting a before_action causes all later ones to be skipped.

  4. Mar 2021
  5. Feb 2021
  6. Nov 2020
    1. Important caveat: in the combined expression, if the middle command has a non-zero exit status, then both the middle and the rightmost command end up getting executed.

      I don't think that is surprising, is it? Since && and || have the same order of precedence. So I think this is more of a clarification than a caveat.

      I think this is just because:

      a && b || c is equivalent to: (a && b) || c (so of course c gets evaluated if (a && b) is false (that if either a or b is false).

      I think they just mean, in this case:

      bedmap && mv || fail
      

      if mv fails, then fail still gets executed.

      Easier to see with a simpler example:

      ⟫ true && false || echo 'fail'
      fail
      
      ⟫ false && true || echo 'fail'
      fail
      

      Better example/explanation here: https://hyp.is/-foxmCVXEeuhnLM-le_R4w/mywiki.wooledge.org/BashPitfalls

      The caveat/mistake here is if you treat it / think that it is equivalent to if a then b else c. That is not the case if b has any chance of failing.

    1. The potential problem: if second_task fails, third_task will not run, and execution will continue to the next line of code - next_task, in this example. This may be exactly the behavior you want. Alternatively, you may be intending that if second_task fails, the script should immediately exit with its error code. In this case, the best choice is to use a block - i.e., curly braces: first_task && { second_task third_task } next_task Because we are using the -e option, if second_task fails, the script immediately exits.
    2. When people write COND && COMMAND, typically they mean "if COND succeeds (or is boolean true), then execute COMMAND. Regardless, proceed to the next line of the script." It's a very convenient shorthand for a full "if/then/fi" clause.
  7. Sep 2020
  8. Aug 2020
  9. Jul 2020
  10. Jun 2020
  11. May 2020
    1. For instance, cor does not distribute over cand: compare (A cand B) cor C with (A cor C) cand (B cor C); in the case ¬A ∧ C , the second expression requires B to be defined, the first one does not
  12. Apr 2020
  13. Mar 2020
    1. Pocket Casts is instead committed to podcasting’s open ecosystem of freely available RSS feeds, CEO Owen Grover says.

      I wish their app allowed one to actually use the podcast's native URL(s) when sharing instead of providing a pca.st shortened URL.

  14. Feb 2020
    1. One 15-year-old from Albuquerque said she missed her mother, who was intermittently homeless and mentally unstable, when she stayed in short-term foster homes. But she also felt better taken care of in foster care, and believed she would have more success in school and more opportunities in life if she stayed. Generally, being a short-stayer was like “being luggage, kind of—just tossing me around,” she said.
  15. Mar 2015