• 0 Posts
  • 59 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle

  • waigl@lemmy.worldtopics@lemmy.worldNo one learnt
    link
    fedilink
    arrow-up
    47
    arrow-down
    1
    ·
    2 months ago

    Germany’s Angela Merkel called the U.S. president’s words “sobering and a little depressing"

    Meanwhile, the Italians thought he was too chaotic and disorganized, the Greek didn’t like his lack of work ethic, the French objected to his constant philandering and the British were put off by his taste in food.



  • They’ve recently been arresting white-skinned people from traditional white and western countries as well, such as Germany. What’s more, we’re not even talking about just sending them back anymore. That, I could even kinda live with, even if it is both unethical and stupid (the US needs those people’s cheap labor). We’re talking about locking them up without trial or any process whatsoever in illegal torture prisons.


  • You’ve hit the nail on the head. As weird and hard to believe as it seems right now, it’s not Trump himself who will be our biggest problem in the mid to long term. It’s who ever comes after him who he and his followers are paving the way for now.

    Trump so far has been of a somewhat limited dangerousness for freedom and democracy so far, not because his views and convictions are not dangerous enough, but because he’s simply too incompetent to be properly dangerous. There is a good likelihood that whoever comes after him will be a lot more competent.










  • Writing good comments is an art form, and beginner programmers often struggle with it. They know comments mostly from their text books, where the comments explain what is happening to someone who doesn’t yet know programming, and nobody has told them yet that that is not at all a useful commenting style outside of education. So that’s how they use them. It usually ends up making the code harder to read, not easier.

    Later on, programmers will need to learn a few rules about comments, like:

    • Assume that whoever reads your code knows the programming language, the platform and the problem domain at least in general terms. You are not writing a teaching aid, you are writing presumably useful software.
    • Don’t comment the obvious. (Aside from documentation comments for function/method/class signatures)
    • Don’t comment what a line is doing. Instead, write your code, especially names for variables, constants, classes, functions, methods and so on, so that they produce talking code that needs no comments. Reserve the “what” style comments for where that just isn’t possible.
    • Do comment the why. Tell the reader about your intentions and about big-picture issues. If an if-statement is hard to parse, write a corresponding if clause in plain English on top of it.
    • In some cases, comment the “why not”, to keep maintenance programmers from falling in the same trap you already found.