12 Matching Annotations
  1. Nov 2020
    1. The use of antioxidants to prevent some diseases is controversial.[53] In a high-risk group like smokers, high doses of beta carotene increased the rate of lung cancer since high doses of beta-carotene in conjunction of high oxygen tension due to smoking results in a pro-oxidant effect and an antioxidant effect when oxygen tension isn't high.[54][55] In less high-risk groups, the use of vitamin E appears to reduce the risk of heart disease.[56] However, while consumption of food rich in vitamin E may reduce the risk of coronary heart disease in middle-aged to older men and women, using vitamin E supplements also appear to result in an increase in total mortality, heart failure, and hemorrhagic stroke
    1. High doses of some antioxidants may have harmful long-term effects. The beta-Carotene and Retinol Efficacy Trial (CARET) study of lung cancer patients found that smokers given supplements containing beta-carotene and vitamin A had increased rates of lung cancer.[22] Subsequent studies confirmed these adverse effects.[23] These harmful effects may also be seen in non-smokers, as one meta-analysis including data from approximately 230,000 patients showed that β-carotene, vitamin A or vitamin E supplementation is associated with increased mortality, but saw no significant effect from vitamin C
  2. May 2019
    1. Publisher Groups are only visible over the domain(s) they are scoped to, while Private Groups are visible across the web

      I didn't realize this reading the blog (https://web.hypothes.is/blog/expanding-our-groups-capabilities/). Until I came across this article I thought they were globally scoped as well, which IMO would make Restricted groups significantly more useful.

    2. Open Group Restricted Group

      Important to note: these two types of groups work only on certain domains, designated by the group creators. https://web.hypothes.is/help/publisher-groups/

    1. we process millions of transactions per day here and we really need someone with more relevant experience who can handle these things without ramping up
    1. Add revenue.  Reduce costs.  Those are your only goals.

      This is sensible advice, but not actionable for many engineers without business knowledge. Being hired to "add revenue and/or reduce costs" means understanding the business; in many cases this makes people think of you as more than a "programmer". It may be intimidating, but I think most people on this path will tell you it's not such a big deal. Erik Dietrich calls these people "efficiencers", and if it sounds like something you'd like to do you should read as much of his blog as you can, starting with this: https://daedtech.com/the-efficiencers-guide-getting-started/. Seems like McKenzie has something slightly different in mind, something between a "programmer" and "efficiencer".

    1. you are accidentally optimizing for implicit bias

      Besides biases related to gender, race etc. there are expectations one may not be aware of, which make them inclined to hire or not based on how much they fit into their mental model of a "programmer". A very good post on that: https://danluu.com/programmer-moneyball/

    2. The most significant shift we’ve made is requiring every final candidate to work with us for three to eight weeks on a contract basis

      A potentially even better approach is to have a work sample test before that: https://sockpuppet.org/blog/2015/03/06/the-hiring-post/

    3. The real trouble with using a lot of mediocre programmers instead of a couple of good ones is that no matter how long they work, they never produce something as good as what the great programmers can produce.

      Obviously, only a programmer would write this; it may or may not be true, see https://daedtech.com/programmer-skill-fetish-contextualized/