home.social

#ctos — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #ctos, aggregated by home.social.

  1. Every single one of those suffers from severe self-selection biases - and even if a representative sample could be correctly taken, they're not actually closely related to how programming languages are matched to various problems.

    It's lazy, click-baity #journalism at best, and #listicle fodder in actual fact most of the time.

    [1] #CTOs may like to pick "popular" languages so they have more programmers to pick from, lowering what they need to #pay. See "Java", 1998-2015.

    2/2

    #SamplingError

  2. Every single one of those suffers from severe self-selection biases - and even if a representative sample could be correctly taken, they're not actually closely related to how programming languages are matched to various problems.

    It's lazy, click-baity #journalism at best, and #listicle fodder in actual fact most of the time.

    [1] #CTOs may like to pick "popular" languages so they have more programmers to pick from, lowering what they need to #pay. See "Java", 1998-2015.

    2/2

    #SamplingError

  3. Every single one of those suffers from severe self-selection biases - and even if a representative sample could be correctly taken, they're not actually closely related to how programming languages are matched to various problems.

    It's lazy, click-baity #journalism at best, and #listicle fodder in actual fact most of the time.

    [1] #CTOs may like to pick "popular" languages so they have more programmers to pick from, lowering what they need to #pay. See "Java", 1998-2015.

    2/2

    #SamplingError

  4. Every single one of those suffers from severe self-selection biases - and even if a representative sample could be correctly taken, they're not actually closely related to how programming languages are matched to various problems.

    It's lazy, click-baity #journalism at best, and #listicle fodder in actual fact most of the time.

    [1] #CTOs may like to pick "popular" languages so they have more programmers to pick from, lowering what they need to #pay. See "Java", 1998-2015.

    2/2

    #SamplingError

  5. Every single one of those suffers from severe self-selection biases - and even if a representative sample could be correctly taken, they're not actually closely related to how programming languages are matched to various problems.

    It's lazy, click-baity #journalism at best, and #listicle fodder in actual fact most of the time.

    [1] #CTOs may like to pick "popular" languages so they have more programmers to pick from, lowering what they need to #pay. See "Java", 1998-2015.

    2/2

    #SamplingError

  6. Dear #technology #journalists,

    Please stop writing and disseminating "most #popular #programming #languages" articles. Besides the fact that #popularity is a relatively useless criterion to select an implementation by [1], the sources of your data are all terrible, and generally fall into:

    -questionnaires sent to #CTOs by #management sites
    -undocumented analysis of some large but random #corpus of #code
    -#survey questions given to users of some popular tool or website

    1/2

    #analysis

  7. Dear #technology #journalists,

    Please stop writing and disseminating "most #popular #programming #languages" articles. Besides the fact that #popularity is a relatively useless criterion to select an implementation by [1], the sources of your data are all terrible, and generally fall into:

    -questionnaires sent to #CTOs by #management sites
    -undocumented analysis of some large but random #corpus of #code
    -#survey questions given to users of some popular tool or website

    1/2

    #analysis

  8. Dear #technology #journalists,

    Please stop writing and disseminating "most #popular #programming #languages" articles. Besides the fact that #popularity is a relatively useless criterion to select an implementation by [1], the sources of your data are all terrible, and generally fall into:

    -questionnaires sent to #CTOs by #management sites
    -undocumented analysis of some large but random #corpus of #code
    -#survey questions given to users of some popular tool or website

    1/2

    #analysis

  9. Dear #technology #journalists,

    Please stop writing and disseminating "most #popular #programming #languages" articles. Besides the fact that #popularity is a relatively useless criterion to select an implementation by [1], the sources of your data are all terrible, and generally fall into:

    -questionnaires sent to #CTOs by #management sites
    -undocumented analysis of some large but random #corpus of #code
    -#survey questions given to users of some popular tool or website

    1/2

    #analysis

  10. Dear #technology #journalists,

    Please stop writing and disseminating "most #popular #programming #languages" articles. Besides the fact that #popularity is a relatively useless criterion to select an implementation by [1], the sources of your data are all terrible, and generally fall into:

    -questionnaires sent to #CTOs by #management sites
    -undocumented analysis of some large but random #corpus of #code
    -#survey questions given to users of some popular tool or website

    1/2

    #analysis

  11. Schools are laden with video surveillance cameras. Their goal is to protect children, but the effect is often the opposite. Video #surveillance provides insight into what happened but doesn’t necessarily prevent it. #Encryption prevents bad things from happening. Why not empower students and staff with knowledge? blog.tcea.org/cyber-protection #TCEA #CyberProtection #CyberSecurity #Education #Schools #CTOs