home.social

#defensiveprogramming — Public Fediverse posts

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

fetched live
  1. Good advice from the 'bind_cols' documentation: "Where possible prefer using a join to combine multiple data frames. bind_cols() binds the rows in order in which they appear so it is easy to create meaningless results without realising it." #RStats #DefensiveProgramming

  2. #TodayILearned #TIL ... that you can use combining accents on the # of a #hashtag! For example #̧Cedilla. Why? Because someone, in a heroic feat of #DefensiveProgramming, thought "I bet some #weirdos will do that, I'd better deal with it sensibly". Why would weirdos like me do that? Because we're weirdos!

    Also, you can pile them on top of each other! Therefore the official hashtag of #Zalgo is not #Zalgo, it is #̶̧̼͖̖̦͍͉̝̗͐̈́̏͜Zalgo.

    #Unicode

  3. ... that you can use combining accents on the # of a ! For example . Why? Because someone, in a heroic feat of , thought "I bet some will do that, I'd better deal with it sensibly". Why would weirdos like me do that? Because we're weirdos!

    Also, you can pile them on top of each other! Therefore the official hashtag of is not , it is .

  4. #TodayILearned #TIL ... that you can use combining accents on the # of a #hashtag! For example #̧Cedilla. Why? Because someone, in a heroic feat of #DefensiveProgramming, thought "I bet some #weirdos will do that, I'd better deal with it sensibly". Why would weirdos like me do that? Because we're weirdos!

    Also, you can pile them on top of each other! Therefore the official hashtag of #Zalgo is not #Zalgo, it is #̶̧̼͖̖̦͍͉̝̗͐̈́̏͜Zalgo.

    #Unicode

  5. #TodayILearned #TIL ... that you can use combining accents on the # of a #hashtag! For example #̧Cedilla. Why? Because someone, in a heroic feat of #DefensiveProgramming, thought "I bet some #weirdos will do that, I'd better deal with it sensibly". Why would weirdos like me do that? Because we're weirdos!

    Also, you can pile them on top of each other! Therefore the official hashtag of #Zalgo is not #Zalgo, it is #̶̧̼͖̖̦͍͉̝̗͐̈́̏͜Zalgo.

    #Unicode

  6. Working at #InternetArchive is helping my #DefensiveProgramming a lot. Situations like poweroutages, hard-drive failures, network congestion errors, etc that are once in a lifetime in other environments are encountered regularly for our code.

    In that regard, the code reviews at the Core Infrastructure Engineering are highlighting the depth of problems that need to be tackled in our environment.

  7. Working at #InternetArchive is helping my #DefensiveProgramming a lot. Situations like poweroutages, hard-drive failures, network congestion errors, etc that are once in a lifetime in other environments are encountered regularly for our code.

    In that regard, the code reviews at the Core Infrastructure Engineering are highlighting the depth of problems that need to be tackled in our environment.

  8. Working at #InternetArchive is helping my #DefensiveProgramming a lot. Situations like poweroutages, hard-drive failures, network congestion errors, etc that are once in a lifetime in other environments are encountered regularly for our code.

    In that regard, the code reviews at the Core Infrastructure Engineering are highlighting the depth of problems that need to be tackled in our environment.

  9. Working at #InternetArchive is helping my #DefensiveProgramming a lot. Situations like poweroutages, hard-drive failures, network congestion errors, etc that are once in a lifetime in other environments are encountered regularly for our code.

    In that regard, the code reviews at the Core Infrastructure Engineering are highlighting the depth of problems that need to be tackled in our environment.

  10. Working at #InternetArchive is helping my #DefensiveProgramming a lot. Situations like poweroutages, hard-drive failures, network congestion errors, etc that are once in a lifetime in other environments are encountered regularly for our code.

    In that regard, the code reviews at the Core Infrastructure Engineering are highlighting the depth of problems that need to be tackled in our environment.

  11. A large chunk of client JS code is just this over and over and over again. In case *I* removed a necessary element when *I* wasn't watching. 🤦‍♂️
    ```
    const x = document.getElementById("X");
    if (!x) {
    console.error("X element not found.");
       return;
    }
    //later
    alert("Check console.");
    ```
    #technology #programming #JavaScript #defensiveProgramming

  12. A large chunk of client JS code is just this over and over and over again. In case *I* removed a necessary element when *I* wasn't watching. 🤦‍♂️
    ```
    const x = document.getElementById("X");
    if (!x) {
    console.error("X element not found.");
       return;
    }
    //later
    alert("Check console.");
    ```
    #technology #programming #JavaScript #defensiveProgramming

  13. A large chunk of client JS code is just this over and over and over again. In case *I* removed a necessary element when *I* wasn't watching. 🤦‍♂️
    ```
    const x = document.getElementById("X");
    if (!x) {
    console.error("X element not found.");
       return;
    }
    //later
    alert("Check console.");
    ```

  14. A large chunk of client JS code is just this over and over and over again. In case *I* removed a necessary element when *I* wasn't watching. 🤦‍♂️
    ```
    const x = document.getElementById("X");
    if (!x) {
    console.error("X element not found.");
       return;
    }
    //later
    alert("Check console.");
    ```
    #technology #programming #JavaScript #defensiveProgramming

  15. A large chunk of client JS code is just this over and over and over again. In case *I* removed a necessary element when *I* wasn't watching. 🤦‍♂️
    ```
    const x = document.getElementById("X");
    if (!x) {
    console.error("X element not found.");
       return;
    }
    //later
    alert("Check console.");
    ```
    #technology #programming #JavaScript #defensiveProgramming

  16. Weekly Dev Chat 2024-10-22: Winterizing Your Codebase: Preparing for Stormy Weather

    weeklydevchat.com/2024-10-22-w

    Everyone and anyone is welcome to join as long as you are kind, supportive, and respectful of others.

  17. I set up my Python code to make sure that (a) we're in a clean git state and (b) we haven't already run an experiment with the same ID number.

    This has saved my bacon more than once, preventing either wasting days of computation or overwriting hard-won data.

    #python #DefensiveProgramming #git

  18. I set up my Python code to make sure that (a) we're in a clean git state and (b) we haven't already run an experiment with the same ID number.

    This has saved my bacon more than once, preventing either wasting days of computation or overwriting hard-won data.

    #python #DefensiveProgramming #git

  19. I set up my Python code to make sure that (a) we're in a clean git state and (b) we haven't already run an experiment with the same ID number.

    This has saved my bacon more than once, preventing either wasting days of computation or overwriting hard-won data.

    #python #DefensiveProgramming #git

  20. I set up my Python code to make sure that (a) we're in a clean git state and (b) we haven't already run an experiment with the same ID number.

    This has saved my bacon more than once, preventing either wasting days of computation or overwriting hard-won data.

    #python #DefensiveProgramming #git

  21. Defensive driving on American highways is when you assume that everyone wizzing past you at 30 above posted is out to do you in, so you use more-than-warranted caution.

    Likewise, in #IT, #DefensiveProgramming is when you assume that every piece code—functions your team wrote, libraries and frameworks that were foisted upon you, all of them—are out to get you.

    And like defensive driving, defensive programming turns a freeing, joyous activity, namely programming, into a paranoid schizophrenic #disorder.

  22. Defensive driving on American highways is when you assume that everyone wizzing past you at 30 above posted is out to do you in, so you use more-than-warranted caution.

    Likewise, in #IT, #DefensiveProgramming is when you assume that every piece code—functions your team wrote, libraries and frameworks that were foisted upon you, all of them—are out to get you.

    And like defensive driving, defensive programming turns a freeing, joyous activity, namely programming, into a paranoid schizophrenic #disorder.

  23. Defensive driving on American highways is when you assume that everyone wizzing past you at 30 above posted is out to do you in, so you use more-than-warranted caution.

    Likewise, in #IT, #DefensiveProgramming is when you assume that every piece code—functions your team wrote, libraries and frameworks that were foisted upon you, all of them—are out to get you.

    And like defensive driving, defensive programming turns a freeing, joyous activity, namely programming, into a paranoid schizophrenic #disorder.

  24. Defensive driving on American highways is when you assume that everyone wizzing past you at 30 above posted is out to do you in, so you use more-than-warranted caution.

    Likewise, in #IT, #DefensiveProgramming is when you assume that every piece code—functions your team wrote, libraries and frameworks that were foisted upon you, all of them—are out to get you.

    And like defensive driving, defensive programming turns a freeing, joyous activity, namely programming, into a paranoid schizophrenic #disorder.

  25. Defensive driving on American highways is when you assume that everyone wizzing past you at 30 above posted is out to do you in, so you use more-than-warranted caution.

    Likewise, in #IT, #DefensiveProgramming is when you assume that every piece code—functions your team wrote, libraries and frameworks that were foisted upon you, all of them—are out to get you.

    And like defensive driving, defensive programming turns a freeing, joyous activity, namely programming, into a paranoid schizophrenic #disorder.

  26. * Assertion at /.../src/mono/mono/metadata/....c:..., condition `0' not met: It probably would have worked, @lambdageek, except you added an assert to guarantee that it won't.

    #defensiveProgramming #softwareEngineering #assertOrientedProgramming #thisIsWhyWeCantHaveNiceThings

  27. * Assertion at /.../src/mono/mono/metadata/....c:..., condition `0' not met: It probably would have worked, @lambdageek, except you added an assert to guarantee that it won't.

    #defensiveProgramming #softwareEngineering #assertOrientedProgramming #thisIsWhyWeCantHaveNiceThings

  28. * Assertion at /.../src/mono/mono/metadata/....c:..., condition `0' not met: It probably would have worked, @lambdageek, except you added an assert to guarantee that it won't.

    #defensiveProgramming #softwareEngineering #assertOrientedProgramming #thisIsWhyWeCantHaveNiceThings