• 1 Post
  • 1.03K Comments
Joined 3 years ago
cake
Cake day: June 9th, 2023

help-circle
  • My crimes will be explored in as much depth as possible in any extensive biography

    Probably not. Without any investigation it will all be speculation. Biographies are written for a commercial audience. Who’s going to buy a biography of Andrew? People who like the royals, not people who hate them. If he’d actually appeared in court, the biography would have to address it. But, with it all just speculation, they can mention the speculation and move on.

    It’s possible that some of the people who met with Epstein did it because they knew he could introduce them to other rich and powerful people. They might not have known about the child sexual abuse. Or they suspected something, but thought that Epstein was always seen with barely legal 18-year-olds, and that that was the extent of it.

    I personally don’t think that Epstein introduced himself to billionaires by saying “Hi, I’m Jeff Epstein, I rape children, are you interested in raping children too?” I don’t believe that being a billionaire automatically means you not only enjoy raping children, but are excited to share that hobby with other people. Epstein probably sounded them out, investigated them, and only went into details with the ones who weren’t going to expose him. And, most likely, he got blackmail material on anybody who he did share his “hobby” with. He probably kept anybody who he thought might expose him at arms length, and he only let them see him with girls who were 18+.

    So, while that plausible deniability exists, I’m sure Andrew wants to be able to claim that he was buddies with Epstein, but was so clueless that he never knew about the child sexual abuse.


  • Look, the kind of people who show up in Epstein’s files are the kind that deserve zero sympathy. They’re the kinds of ultra-rich people who should be lined up for the guillotine just because of their obscene wealth hoards, even if they had nothing to do with child sex abuse.

    But, just look at the phenomenon of SWATting. People phone in a malicious tip to the police in the hope that they kick down someone’s door. In addition to malicious people, a tip line is going to get people having schizophrenic episodes, people suffering carbon monoxide poisoning, etc.

    To me, these allegations seem about as likely as there being a secret basement at Comet Ping Pong pizzeria where the elites were draining children of their adrenachrome. And, I’d really like it if my side didn’t go all Q-Anon and start believing every possible rumour just because it makes someone they hate look bad.


  • It was a bribe, but they still made a movie, and they still put that movie in theatres. It’s still going to be embarrassing if nobody sees the movie. There are reports of movie theatres where there are 3-4 people in the audience, and every one of them is being paid to be there because they have to write a review of the movie.

    They could have paid Melania for her life rights, pretended to make a movie, and then not released it, or made it streaming-only, making some excuse about protesters, the safety of the theatre goers, etc. Instead they actually put it out into the world and invited the kind of ridicule it deserves.




  • Not every big change is necessarily something you can meaningfully break up into small changes. Sometimes when you could break it up into small changes, you have to change its structure in a meaningful way to half-implement it and test out that half-version. It takes experience to know when it’s best to get the whole structure expressed it code, then to go back and tweak it based on any compiler errors. Most of the time the compiler errors are very minor things like a typo, so you don’t lose any meaningful time fixing them.



  • Most programmers I know compile a program when they have fully expressed an idea they have in their heads. It might just be the first outline of the idea. But, it’s a solid first sketch that contains all the key details. Unfortunately, often that’s a complex idea so it can be somewhere on the order of an hour before they stop coding and try compiling. One reason for that is that compiling the program is a context switch, and when they context switch they can’t keep all of their thoughts about the program in their head, instead they have to think about compiling. And, if compiling takes more than a few seconds their attention also starts to drift to other things.

    Coding for something like an hour without making a single typo or braino is difficult. This is especially true if the programmer is attempting to express a creative idea. Their focus won’t be on getting every single detail correct, it will be in sketching the shape of the idea as completely as possible. 99% of the time, those mistakes are entirely obvious and take no time to fix. But the compiler is (luckily) unforgiving of errors, even if the fix is obvious. But, that’s why it’s suspicious if the code compiles perfectly the first time.

    It’s possible that some people have different workflows. Maybe they write out the entire program in comments and pseudocode before using an actual programming language. If you do that, then you can probably afford to take a break from the actual coding more often and compile what you have so far. Maybe you’re compiling every 5 minutes instead of every 30, in which case it’s pretty normal not to have any compiler errors. Maybe some people use a super advanced IDE that effectively compiles the code in the background all the time and flags errors that will become compiler errors. I think a lot of people who became programmers before that kind of thing was popular find that sort of thing to be distracting. If they’re trying to write something on line 50 and the IDE flags something from line 45, they might have already shifted their context a bit, and having to go back and fix that will distract them from the thing they’re currently trying to express.

    Personally, I’ve often had no compiler errors when writing tests. Tests are often very small, self-contained bits of code that don’t take long to write, and aren’t very complex, so it’s pretty normal to have a test compile and run perfectly the first time.

    The point is, programmers who have been programming for a long time are the ones who are more likely to be surprised if their code compiles perfectly the first time.








  • I think I’ve had it happen once over something like a decade of using them. From what I remember it was because I was running something in the terminal that ignored the signals it was sent, so the laptop didn’t properly go to sleep. Of course, the program ended up failing because a lot of the things it depended on did suspend themselves and that caused major breakage.

    Luckily I noticed a whining sound (fans at maximum speed) from my backpack before anything too bad happened.



  • My ultra-religious mother “heard from someone” that AI “is the devil” so she wouldn’t use it. That’s great. Unfortunately, it made her really scared of everything. She was super anxious because AI was in the news all the time.

    I really don’t want her to use AI, because she already has such a hard time distinguishing fantasy from reality. But, I still had to try to explain to her that LLMs are just fancy auto-complete, and how often they get things wrong to reduce her stress level. I hope she continues not to use them, but now I hope she just shakes her head and sighs when someone else uses one, instead of thinking they’re letting evil into their bodies.


  • Apple laptops are typically extremely good when it comes to sleep and suspend.

    A major advantage of having a very small range of hardware you have to support is that it’s pretty easy to test all possible combinations and make sure they work well together. As far as I’m concerned, Apple has been, and probably always will be the undisputed champion of doing this right.