• 3 Posts
  • 392 Comments
Joined 2 years ago
cake
Cake day: July 7th, 2023

help-circle

  • After tens of thousands of bash lines written, I have to disagree. The article seems to argue against use of -e due to unpredictable behavior; while that might be true, I’ve found having it in my scripts is more helpful than not.

    Bash is clunky. -euo pipefail is not a silver bullet but it does improve the reliability of most scripts. Expecting the writer to check the result of each command is both unrealistic and creates a lot of noise.

    When using this error handling pattern, most lines aren’t even for handling them, they’re just there to bubble it up to the caller. That is a distraction when reading a piece of code, and a nuisense when writing it.

    For the few times that I actually want to handle the error (not just pass it up), I’ll do the “or” check. But if the script should just fail, -e will do just fine.
















  • Your age group, sex, location, profession/industry, income estimation - you can assume they have this data.

    That + a few data points that could be tracked by apps or websites:

    • Searched online for symptoms
    • Searched for doctors
    • Called the clinic to schedule an appointment
    • GPS to the clinic
    • Connected to the clinic’s WiFi
    • Doctor is a specialist in X

    Cross some of that, personal info, and ads of treatments for conditions of X.

    They don’t need to listen to your mic.

    That said, if it’s a fairly common condition, it might be the case you were presented the ad before and never noticed it.