> I want it to just work; that kind of design takes effort & there's no way around it
Nothing "just works" for everyone. You are a product of your environment, people say apple interfaces/OSX are intuitive, I found them utterly unusable until I was forced to spend a lot of time to learn them.
Depending on which software you grew up using, you either find it intuitive or don't. If you found someone that has never used technology, no modern UI would be intuitive.
Personally, I hate it when software that I have to use daily is not configurable (and ideally extensible via programming). It's basically designed for the lowest common denominator for some group of users that product/design groups have decided is "intuitive".
> People hate UI redesigns for a reason...
I do agree here, stop changing things for the sake of changing things. When I owned some internal tools, I would go out of my way to not break user workflows. Even minor things, like tab-order, which I think most people don't think about, I'd have browser automation tests to make sure they remained consistent.
The parent mentions the DTV visa which is the opposite of the visa-run strategy. Realistically though, if you're a "nomad" from a country with a powerful-ish passport you can come to Thailand for 60 days, extend once for 30 days for a total stay of 90 days. After that you can do a bit of a loop between Malaysia, Vietnam, Cambodia, Laos, Indonesia, Philippines in whatever order you prefer and come back to Thailand in a year. They'll have no problem letting you in again.
It's pretty easy to spend a year in SEA without raising eyebrows at any border if you're willing to change countries somewhat often and don't mind AirAsia flights.
That is basically my life. I've visited almost every country in the region this year (+ China and Japan) on a tourist visa.
The problem for me personally is this life is stressful on relationships, health, and personal productivity. Spending a weekend every 1-2 months to deal with travel (and arrangements) is exhausting and expensive on productivity hours.
The 3rd party has continued to exist when the first party support died the first time. It's the exact opposite, you don't want to buy a device that is tied to some 1st party service. The service can go down and you're stuck with a brick.
I agree with your point about "install" vs "sideload".
> Google’s message that “Sideloading is Not Going Away” is clear, concise, and false
Given your(and my) definition, this statement is false. Google isn't taking away sideloading, you can still use adb. I'd say using adb to load an apk from another device is the proper use of "sideloading".
What Google is doing is much worse, they are taking away your ability to _install_ software.
And yes, HN loves splitting hairs. But if it wasn't for the hairsplitting, there probably would be be much discussion. Just most people agreeing with you and a few folks who would prefer to give up freedom for security.
> No one would retrieve all users and then filter them within the program.
No one _should_ do that, but that's a common enough problem (that usually doesn't get found until code is running in production). I suspect with the rise of vibe coding, it's going to happen more and more.
Sometimes it's forced by using the wrong database in the first place, or the wrong data structure. It can be less pain to do a bit of post-processing in the application layer than to unpick either of those.
> Fizz-buzz is a difficult problem. There are a few different ways to solve the problem and every single one has some uglyness about it that should make a qualified programmer squirm and hate their answer
What are you talking about? The question is basically just a gotcha to catch out folks that don't know about the modulo operator. Or is this satire and I completely missed the joke?
Implementations details of fizzbuzz are ugly. There are a couple different ways to implement it (not all use the modulo operator!), but not matter how you implement it there is a special case that doesn't elegantly fit your algorithm and in turn your code is ugly in ways it seems like a better design could fix.
That you cannot find a an elegant solution to what seems like it should have one is what makes it difficult. A good sign of a good programmer is then you ask them about their code after it works they will say they don't like this solution and would like to spend time making it cleaner. If you know there isn't an elegant solution of course you won't bother spending that time, but if you don't know that if seems like there should be a better answer if you can just restructure the code a little.
If anything, I know people that are getting pissed off about all the AI stuff in windows and are considering switching.
reply