Long term computer programmer, making my own library. American based. Far left politically. Promotes use of paper ballots. Follows news about environmental collapse, political corruption in my country, human rights, science and tech.

  • 1 Post
  • 40 Comments
Joined 7 months ago
cake
Cake day: July 16th, 2025

help-circle












  • Dev mode is when developing by the programmers. Production means used by others.

    When I am working with a service, I want to know immediately when there is a problem.

    When I push my code to be used, the dev flag is off and the code does stuff as normal.

    For example: if I am making a payment service using a third party, I use sandbox and fake cc numbers. I want things to fail loudly on my computer so I can make things fail silently. And safely, when it’s used with real money. But I can only do that if I know there are issues. And only logging lets some bugs be unnoticed , particularly if a cluttered log. So being loud in development saves tears in production


  • All good points!

    Also, I’ve learned from others that how you crash depends on the environment, if running in dev, be different than if the thing is used by the public or in production.

    • In a script, dump too much data if dev, in production keep it terse but have relevant info and a link to the docs.
    • In a gui, webpage or app make the crash screen in dev be a thing of beauty that has the full stack trace, database info , and more. But in production only generate a polite message that is vague, with an error code. Push that error to a logging service with the code. And if this is not used by the public but by a company that paid for it, have a feedback button or live chat button, in the error message, to talk with tech support.
    • Backend services and libraries: if in dev mode crashes should be loud and definitely break things, while in production log silently and keep working.
    • And for any type of program: always back up data, and always use transactions to not have the database or files be in an incomplete state if an exception happens.

    formatting edit





  • limer@lemmy.mltoMemes@lemmy.mlVoTe BluE
    link
    fedilink
    arrow-up
    6
    arrow-down
    1
    ·
    3 months ago

    Republican efforts to suppress voting and the democrat “get out the vote” initiatives have much in common.

    In some states voting matters, in most it does not. And federally it does not.

    Seen in this context both efforts are a type of grifting and scam. No different than other political rabble rousing.

    Pretensions USA is a democracy makes reform that much harder. And both parties do this well


  • limer@lemmy.mltoMemes@lemmy.mlVoTe BluE
    link
    fedilink
    arrow-up
    14
    ·
    3 months ago

    This assumes the USA is a democracy at the federal level. Where votes by people matter.

    Many states use election machines, owned by oligarchs, whose operations are a closed book and are not regulated. Coincidentally those states, both red and blue, fail tests approved by the United Nations to detect tampering of votes.

    Those states make the other states, that actually pass the tests, irrelevant.

    What makes democracy, in the USA, unable to curb the even the very gross problems today is not the people doing the cheating.

    But it is the people who refuse to call the cheating out (by addressing the real issues), and more important the majority of citizens who absolutely do not see this as a problem. It’s only when this is addressed can the actual issues of a real democracy be looked at.

    Even then, real reform is hard to do in a democracy. Especially one so large and out of control as the nation we see now. So any reform has to be not using the ballot box.

    A boycott actually could help.