home.social

#codinghorror — Public Fediverse posts

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

  1. 🎉 Oh, the horror! #GitHub decided that what developers really need is more popups! 🚨 Because clearly, the best way to streamline coding is to introduce surprise windows at every click. 🤦‍♂️
    github.com/orgs/community/disc #Popups #DeveloperExperience #CodingHorror #UXDesign #TechNews #HackerNews #ngated

  2. 🎉 Oh, the horror! #GitHub decided that what developers really need is more popups! 🚨 Because clearly, the best way to streamline coding is to introduce surprise windows at every click. 🤦‍♂️
    github.com/orgs/community/disc #Popups #DeveloperExperience #CodingHorror #UXDesign #TechNews #HackerNews #ngated

  3. 🎉 Oh, the horror! #GitHub decided that what developers really need is more popups! 🚨 Because clearly, the best way to streamline coding is to introduce surprise windows at every click. 🤦‍♂️
    github.com/orgs/community/disc #Popups #DeveloperExperience #CodingHorror #UXDesign #TechNews #HackerNews #ngated

  4. 🎉 Oh, the horror! #GitHub decided that what developers really need is more popups! 🚨 Because clearly, the best way to streamline coding is to introduce surprise windows at every click. 🤦‍♂️
    github.com/orgs/community/disc #Popups #DeveloperExperience #CodingHorror #UXDesign #TechNews #HackerNews #ngated

  5. 🎉 Oh, the horror! #GitHub decided that what developers really need is more popups! 🚨 Because clearly, the best way to streamline coding is to introduce surprise windows at every click. 🤦‍♂️
    github.com/orgs/community/disc #Popups #DeveloperExperience #CodingHorror #UXDesign #TechNews #HackerNews #ngated

  6. TIL:

    why:

    Integer.MAX_VALUE smaller by one than 2147483648, so it overflows and becomes negative again.

    so -Integer.MAX_VALUE will effectively do not do anything as it goes back and forth. I kinda agree with that.

    What I am perplexed about is the "contract" of Math.abs() being broken here.

    #java #codinghorror

  7. TIL:

    why:

    Integer.MAX_VALUE smaller by one than 2147483648, so it overflows and becomes negative again.

    so -Integer.MAX_VALUE will effectively do not do anything as it goes back and forth. I kinda agree with that.

    What I am perplexed about is the "contract" of Math.abs() being broken here.

    #java #codinghorror

  8. TIL:

    why:

    Integer.MAX_VALUE smaller by one than 2147483648, so it overflows and becomes negative again.

    so -Integer.MAX_VALUE will effectively do not do anything as it goes back and forth. I kinda agree with that.

    What I am perplexed about is the "contract" of Math.abs() being broken here.

    #java #codinghorror

  9. @C3nC3 @DanielMReck @codinghorror @SkepticalScience

    Took a look at Matomo. Reads well. Thanks!

    We mostly use in-house because ultimately the horse's mouth is server logs and GA is so money/conversion framed that it misses critical info on publication usage etc. Even so, some info from GA is interesting and this option is appealing.

    Thank you to #CodingHorror for surfacing the issue.

  10. @C3nC3 @DanielMReck @codinghorror @SkepticalScience

    Took a look at Matomo. Reads well. Thanks!

    We mostly use in-house because ultimately the horse's mouth is server logs and GA is so money/conversion framed that it misses critical info on publication usage etc. Even so, some info from GA is interesting and this option is appealing.

    Thank you to #CodingHorror for surfacing the issue.

  11. @C3nC3 @DanielMReck @codinghorror @SkepticalScience

    Took a look at Matomo. Reads well. Thanks!

    We mostly use in-house because ultimately the horse's mouth is server logs and GA is so money/conversion framed that it misses critical info on publication usage etc. Even so, some info from GA is interesting and this option is appealing.

    Thank you to #CodingHorror for surfacing the issue.

  12. @C3nC3 @DanielMReck @codinghorror @SkepticalScience

    Took a look at Matomo. Reads well. Thanks!

    We mostly use in-house because ultimately the horse's mouth is server logs and GA is so money/conversion framed that it misses critical info on publication usage etc. Even so, some info from GA is interesting and this option is appealing.

    Thank you to #CodingHorror for surfacing the issue.

  13. @C3nC3 @DanielMReck @codinghorror @SkepticalScience

    Took a look at Matomo. Reads well. Thanks!

    We mostly use in-house because ultimately the horse's mouth is server logs and GA is so money/conversion framed that it misses critical info on publication usage etc. Even so, some info from GA is interesting and this option is appealing.

    Thank you to #CodingHorror for surfacing the issue.

  14. So… it's a new year… 2024 at long last. It's literally new year's day, and the whole year now follows. We've got 366 days until we're doing the same thing again.

    Here are some people that you might consider following for your timeline. This is not an exhaustive list.

    #Journalists: @dangoodin, @benjedwards… both writers for @arstechnica

    @[email protected] #AmateurRadio operator and journalist for @VOANews

    @mmasnick journalist for #TechDirt

    @lorenzofb, @zackwhittaker journalists for #TechCrunch

    @codinghorror writer for #CodingHorror

    @briankrebs independent #InfoSec writer and journalist

    @[email protected] / @north@ꩰ.com playfully prodding sites' punycode domain compatibility 🙂

    #Ukraine

    @EugeneMcParland has been posting lots of news about the conflict

    @Gala posts lots of photos and videos showing life in Ukraine -- some beautiful scenery

    #RetroComputing and #RetroTech

    @Gammitin posts lots about restoring classic PCs

    @kenshirriff does lots of deep dives into old tech of all sorts… deep analysis of classic ICs, old mechanical avionics, all sorts.

    #Gambia

    @buba has been posting lots of photos from his native Gambia (west coast of Africa)

    #AmateurRadio

    @xssfox has been experimenting with all kinds of radio-related things (as well as putting monitors on crooked angles).

    #NewYearFollows

  15. So… it's a new year… 2024 at long last. It's literally new year's day, and the whole year now follows. We've got 366 days until we're doing the same thing again.

    Here are some people that you might consider following for your timeline. This is not an exhaustive list.

    #Journalists: @dangoodin, @benjedwards… both writers for @arstechnica

    @[email protected] #AmateurRadio operator and journalist for @VOANews

    @mmasnick journalist for #TechDirt

    @lorenzofb, @zackwhittaker journalists for #TechCrunch

    @codinghorror writer for #CodingHorror

    @briankrebs independent #InfoSec writer and journalist

    @[email protected] / @north@ꩰ.com playfully prodding sites' punycode domain compatibility 🙂

    #Ukraine

    @EugeneMcParland has been posting lots of news about the conflict

    @Gala posts lots of photos and videos showing life in Ukraine -- some beautiful scenery

    #RetroComputing and #RetroTech

    @Gammitin posts lots about restoring classic PCs

    @kenshirriff does lots of deep dives into old tech of all sorts… deep analysis of classic ICs, old mechanical avionics, all sorts.

    #Gambia

    @buba has been posting lots of photos from his native Gambia (west coast of Africa)

    #AmateurRadio

    @xssfox has been experimenting with all kinds of radio-related things (as well as putting monitors on crooked angles).

    #NewYearFollows

  16. So… it's a new year… 2024 at long last. It's literally new year's day, and the whole year now follows. We've got 366 days until we're doing the same thing again.

    Here are some people that you might consider following for your timeline. This is not an exhaustive list.

    #Journalists: @dangoodin, @benjedwards… both writers for @arstechnica

    @[email protected] #AmateurRadio operator and journalist for @VOANews

    @mmasnick journalist for #TechDirt

    @lorenzofb, @zackwhittaker journalists for #TechCrunch

    @codinghorror writer for #CodingHorror

    @briankrebs independent #InfoSec writer and journalist

    @[email protected] / @north@ꩰ.com playfully prodding sites' punycode domain compatibility 🙂

    #Ukraine

    @EugeneMcParland has been posting lots of news about the conflict

    @Gala posts lots of photos and videos showing life in Ukraine -- some beautiful scenery

    #RetroComputing and #RetroTech

    @Gammitin posts lots about restoring classic PCs

    @kenshirriff does lots of deep dives into old tech of all sorts… deep analysis of classic ICs, old mechanical avionics, all sorts.

    #Gambia

    @buba has been posting lots of photos from his native Gambia (west coast of Africa)

    #AmateurRadio

    @xssfox has been experimenting with all kinds of radio-related things (as well as putting monitors on crooked angles).

    #NewYearFollows

  17. So… it's a new year… 2024 at long last. It's literally new year's day, and the whole year now follows. We've got 366 days until we're doing the same thing again.

    Here are some people that you might consider following for your timeline. This is not an exhaustive list.

    #Journalists: @dangoodin, @benjedwards… both writers for @arstechnica

    @[email protected] #AmateurRadio operator and journalist for @VOANews

    @mmasnick journalist for #TechDirt

    @lorenzofb, @zackwhittaker journalists for #TechCrunch

    @codinghorror writer for #CodingHorror

    @briankrebs independent #InfoSec writer and journalist

    @[email protected] / @north@ꩰ.com playfully prodding sites' punycode domain compatibility 🙂

    #Ukraine

    @EugeneMcParland has been posting lots of news about the conflict

    @Gala posts lots of photos and videos showing life in Ukraine -- some beautiful scenery

    #RetroComputing and #RetroTech

    @Gammitin posts lots about restoring classic PCs

    @kenshirriff does lots of deep dives into old tech of all sorts… deep analysis of classic ICs, old mechanical avionics, all sorts.

    #Gambia

    @buba has been posting lots of photos from his native Gambia (west coast of Africa)

    #AmateurRadio

    @xssfox has been experimenting with all kinds of radio-related things (as well as putting monitors on crooked angles).

    #NewYearFollows

  18. So… it's a new year… 2024 at long last. It's literally new year's day, and the whole year now follows. We've got 366 days until we're doing the same thing again.

    Here are some people that you might consider following for your timeline. This is not an exhaustive list.

    #Journalists: @dangoodin, @benjedwards… both writers for @arstechnica

    @[email protected] #AmateurRadio operator and journalist for @VOANews

    @mmasnick journalist for #TechDirt

    @lorenzofb, @zackwhittaker journalists for #TechCrunch

    @codinghorror writer for #CodingHorror

    @briankrebs independent #InfoSec writer and journalist

    @[email protected] / @north@ꩰ.com playfully prodding sites' punycode domain compatibility 🙂

    #Ukraine

    @EugeneMcParland has been posting lots of news about the conflict

    @Gala posts lots of photos and videos showing life in Ukraine -- some beautiful scenery

    #RetroComputing and #RetroTech

    @Gammitin posts lots about restoring classic PCs

    @kenshirriff does lots of deep dives into old tech of all sorts… deep analysis of classic ICs, old mechanical avionics, all sorts.

    #Gambia

    @buba has been posting lots of photos from his native Gambia (west coast of Africa)

    #AmateurRadio

    @xssfox has been experimenting with all kinds of radio-related things (as well as putting monitors on crooked angles).

    #NewYearFollows

  19. I noticed that an online shop didn't offer Paypal as payment option but on the same checkout page they said they do.

    I sent them a polite mail with a screenshot pointing out the discrepancy. And so began a back-and-forth in which they tried to prove that I was wrong and I - looking deeper into their sourcecode - found increasingly horrifying things.

    Over 3000 positive reviews were hidden via a JS loop below the footer. Apparently an attempt to SEO on a checkout page.

    #webdev #codinghorror

  20. I noticed that an online shop didn't offer Paypal as payment option but on the same checkout page they said they do.

    I sent them a polite mail with a screenshot pointing out the discrepancy. And so began a back-and-forth in which they tried to prove that I was wrong and I - looking deeper into their sourcecode - found increasingly horrifying things.

    Over 3000 positive reviews were hidden via a JS loop below the footer. Apparently an attempt to SEO on a checkout page.

    #webdev #codinghorror

  21. I noticed that an online shop didn't offer Paypal as payment option but on the same checkout page they said they do.

    I sent them a polite mail with a screenshot pointing out the discrepancy. And so began a back-and-forth in which they tried to prove that I was wrong and I - looking deeper into their sourcecode - found increasingly horrifying things.

    Over 3000 positive reviews were hidden via a JS loop below the footer. Apparently an attempt to SEO on a checkout page.

    #webdev #codinghorror

  22. I noticed that an online shop didn't offer Paypal as payment option but on the same checkout page they said they do.

    I sent them a polite mail with a screenshot pointing out the discrepancy. And so began a back-and-forth in which they tried to prove that I was wrong and I - looking deeper into their sourcecode - found increasingly horrifying things.

    Over 3000 positive reviews were hidden via a JS loop below the footer. Apparently an attempt to SEO on a checkout page.

    #webdev #codinghorror

  23. I noticed that an online shop didn't offer Paypal as payment option but on the same checkout page they said they do.

    I sent them a polite mail with a screenshot pointing out the discrepancy. And so began a back-and-forth in which they tried to prove that I was wrong and I - looking deeper into their sourcecode - found increasingly horrifying things.

    Over 3000 positive reviews were hidden via a JS loop below the footer. Apparently an attempt to SEO on a checkout page.

    #webdev #codinghorror

  24. This is a real screenshot of actual production code. It ran for years and helped putting lots of food on the table.

  25. This is a real screenshot of actual production code. It ran for years and helped putting lots of food on the table. #refactoring #programming #imperative #codinghorror

  26. This is a real screenshot of actual production code. It ran for years and helped putting lots of food on the table. #refactoring #programming #imperative #codinghorror

  27. This is a real screenshot of actual production code. It ran for years and helped putting lots of food on the table. #refactoring #programming #imperative #codinghorror

  28. This is a real screenshot of actual production code. It ran for years and helped putting lots of food on the table. #refactoring #programming #imperative #codinghorror

  29. Stack Overflow sold to tech investor Prosus for $1.8 billion - Enlarge / If you've ever gone looking for answers to software development questio... - arstechnica.com/?p=1769534 #stackexchange #stackoverflow #codinghorror #naspers #prosus #tech