699 Matching Annotations
  1. Sep 2020
    1. Svelte will not offer a generic way to support style customizing via contextual class overrides (as we'd do it in plain HTML). Instead we'll invent something new that is entirely different. If a child component is provided and does not anticipate some contextual usage scenario (style wise) you'd need to copy it or hack around that via :global hacks.
    1. It's fashionable to dislike CSS. There are lots of reasons why that's the case, but it boils down to this: CSS is unpredictable. If you've never had the experience of tweaking a style rule and accidentally breaking some layout that you thought was completely unrelated — usually when you're trying to ship — then you're either new at this or you're a much better programmer than the rest of us.
    1. Over time we tend to develop confirmation bias, forever seeking evidence that reinforces what we already believe, and downplaying or dismissing what doesn’t. We’re also designed, both genetically and instinctively, to put our own safety first, and to avoid taking too much risk. Rather than using our capacity for critical thinking to assess new possibilities, we often co-opt our prefrontal cortex to rationalize choices that were actually driven by our emotions.
  2. Aug 2020
  3. Jul 2020
  4. journals.sagepub.com journals.sagepub.com
    1. Sorokowska, A., Sorokowski, P., Hilpert, P., Cantarero, K., Frackowiak, T., Ahmadi, K., Alghraibeh, A. M., Aryeetey, R., Bertoni, A., Bettache, K., Blumen, S., Błażejewska, M., Bortolini, T., Butovskaya, M., Castro, F. N., Cetinkaya, H., Cunha, D., David, D., David, O. A., … Pierce, J. D. (2017). Preferred Interpersonal Distances: A Global Comparison. Journal of Cross-Cultural Psychology, 48(4), 577–592. https://doi.org/10.1177/0022022117698039

  5. Jun 2020
  6. journals.sagepub.com journals.sagepub.com
    1. Sorokowska, A., Sorokowski, P., Hilpert, P., Cantarero, K., Frackowiak, T., Ahmadi, K., Alghraibeh, A. M., Aryeetey, R., Bertoni, A., Bettache, K., Blumen, S., Błażejewska, M., Bortolini, T., Butovskaya, M., Castro, F. N., Cetinkaya, H., Cunha, D., David, D., David, O. A., … Pierce, J. D. (2017). Preferred Interpersonal Distances: A Global Comparison. Journal of Cross-Cultural Psychology, 48(4), 577–592. https://doi.org/10.1177/0022022117698039

    1. McBride, O., Murphy, J., Shevlin, M., Gibson Miller, J., Hartman, T. K., Hyland, P., Levita, L., Mason, L., Martinez, A. P., McKay, R., Stocks, T. V. A., bennett, kate m, Vallières, F., Karatzias, T., Valiente, C., Vazquez, C., & Bentall, R. (2020). An overview of the context, design and conduct of the first two waves of the COVID-19 Psychological Research Consortium (C19PRC) Study [Preprint]. PsyArXiv. https://doi.org/10.31234/osf.io/z3q5p

    1. However, a ActiveRecord::Rollback within the nested transaction will be caught by the block of the nested transaction, but will be ignored by the outer transaction, and not cause a roll back! To avoid this unexpected behaviour, you have to explicitly tell rails for each transaction to indeed use proper nesting: CopyActiveRecord::Base.transaction(joinable: false, requires_new: true) do # inner code end This is a safer default for working with custom transactions.
    1. transaction calls can be nested. By default, this makes all database statements in the nested transaction block become part of the parent transaction. For example, the following behavior may be surprising: User.transaction do User.create(username: 'Kotori') User.transaction do User.create(username: 'Nemu') raise ActiveRecord::Rollback end end creates both “Kotori” and “Nemu”. Reason is the ActiveRecord::Rollback exception in the nested block does not issue a ROLLBACK. Since these exceptions are captured in transaction blocks, the parent block does not see it and the real transaction is committed.

      How is this okay??

      When would it ever be the desired/intended behavior for a raise ActiveRecord::Rollback to have absolutely no effect? What good is the transaction then??

      What happened to the principle of least surprise?

      Is there any reason we shouldn't just always use requires_new: true?

      If, like they say, the inner transaction "become[s] part of the parent transaction", then if anything, it should roll back the parent transaction too — not roll back nothing.

  7. May 2020
    1. Betsch, C., Wieler, L., Bosnjak, M., Ramharter, M., Stollorz, V., Omer, S., Korn, L., Sprengholz, P., Felgendreff, L., Eitze, S., & Schmid, P. (2020). Germany COVID-19 Snapshot MOnitoring (COSMO Germany): Monitoring knowledge, risk perceptions, preventive behaviours, and public trust in the current coronavirus outbreak in Germany. https://doi.org/10.23668/PSYCHARCHIVES.2776