• 2 Posts
  • 564 Comments
Joined 3 years ago
cake
Cake day: June 11th, 2023

help-circle






  • I had four overnight delays in three round trip transatlantic flights in 2025. The airline was at fault for three of them.

    When the airline is at fault for a delay of four hours or more on a long flight that starts or ends in the EU, they owe the passenger 600 Euros, a hotel room, and meals, so those were long delays but not exactly terrible experiences.

    Getting stuck for 20 hours in the Newark airport due to weather wasn’t as pleasant. The airline did not owe me anything because weather is not their fault. There were hundreds of other delayed travelers sleeping on cots in the halls of the airport. They did not have a cot for me.




  • Without seeing the entirety of the interaction, it’s hard to be sure.

    Some people are assholes, and because nobody wants to interact with assholes, they usually end up congregating on whatever forum doesn’t ban them. Moderation is hard and ban evasion is often easy, so there end up being a lot of places like that.

    The other side is that people in general ask a lot of bad questions, and a forum flooded with bad questions becomes useless because people who could answer good questions either get tired of it and leave, or spend so much time on the bad questions they don’t have time for the good ones. People get frustrated when they think that’s happening to a forum they enjoy, and programmers are famously better at communicating with machines than with people.

    Here’s are some tips to ask good questions about programming:

    • First, try to find the answer without asking other people. This is especially important when it comes to programming because the whole job is problem-solving. That means figuring out how a search result, LLM output, or published documentation relates to whatever it is you’re trying to do.
    • Once you’re sure you need help from other people, clearly articulate what it is you want to happen, what you tried in order to achieve it, and what actually happened. Use more detail than you think you need here, especially regarding your expectations. Sometimes the mere act of composing a question this way leads you to the answer, which is effective enough there’s a popular technique of explaining problems to inanimate objects.
    • Include the troubleshooting steps you tried from the first step above in your question. By typing it out, you may discover an error or omission in your process, but you also communicate to other people that you’re not just being lazy, wasting their time, and reducing the signal to noise ratio of their forum.



  • When I can’t use the old one anymore. Every time so far, that’s been because of a hardware failure.

    I’m currently on a Pixel 4A. It’s running Android 16 (LineageOS), and I limit battery charge with AccA so that it doesn’t wear out. It’s currently showing 92% capacity, which seems pretty good for five years. I don’t think I’d actually like a new phone; it would be faster and have a better camera, but my current phone isn’t a bottleneck, and a new phone’s camera will still be worse than my Olympus. It would have 5G, but why should I care? Most new phones are bigger, and as an adult, my hands are not growing.

    I love that answers like this are popular here. There was a time when phone tech was improving fast enough that frequent upgrades made a lot of sense, but now is not that time.