Schon einfach geil, was für ein Sicherheitstheater Google macht, und trotzdem würde ich quasi jeder App auf F-Droid mehr Vertrauen als den ganzen Apps im Play Store.
Oder von Google nicht geduldet werden. Die ganzen YouTube-Apps wurden z.B. mit der Einführung von YouTube Red rausgeworfen, weil Konkurrenz schlecht für's Geschäft ist.
The realization that cow math doesn't work out. Cows need to be pregnant to give milk. A pregnancy will typically result in a calf being born. In practice, a milk cow lives 5-6 years, with a calf born every 12-14 months. So, that's about 5 new cows per 1 milk cow.
You necessarily have to kill cows to prevent those numbers from exploding, even after just one generation. Basically, vegetarianism is not possible, because you do not prevent the slaughtering of cows by refusing to buy the outcome.
Many years ago, a girl in our class was telling a friend and me a secret. Then she addressed my friend to say that it is a secret and he shouldn't tell it to others. My friend complained that he knew to keep it secret and why she wasn't addressing me as well. Then she said that I don't tell stuff like that to others.
Yeah, ten seconds earlier, I was the one who suddenly realized that, oh right, it's a secret, when she addressed my friend.
Like, no, I probably wouldn't have told it to anyone, but I feel like I got way too much credit, just because I'm not terribly talkative.
Ah, interesting. I haven't kept up with the newest Java changes, so you kind of answered that backwards for me. Being able to just use IO.println() is already pretty good and for sure what I'd prefer over having to add an import. Seems to also be a new addition in Java 25, so I guess, Hello World looks a lot different all of a sudden.
Also interesting that this kind of static import doesn't work with System.out.println, I'm guessing because out is already a field of System rather than a package or type. It can be used to write it as out.println, but yeah, not much of a point anymore when IO.println exists.
Then you get other side-effects, like them ignoring or infinitely delaying tickets that are harder to solve. It's a somewhat universal rule of capitalism: As soon as there is a metric for success, the goal is to game that metric as much as possible, because that maximizes the supposed success while minimizing costs.
You can try to define multiple metrics to make this more difficult. And you can set a higher target value than necessary, so that even with the gaming, it's still within an acceptable margin.
But IMHO it's still better to just treat it as a cost of doing business than to invest lots of money to try to make it measurable in an attempt to reduce the money spent.
Yeah, I think, it's important to name and shame, because they actively avoid providing the service that they advertise, but I do also expect this to be a common pattern in the industry. If you actually solved problems and did so permanently, you'd be out of business very quickly. External support providers have an inherent interest for things to work as badly as possible, so long as it does not get their contract cancelled.
Yesterday, I was bringing away waste glass into one of these containers:
And there were either bees or wasps, not quite sure, swarming all over the place. They either have their nest there, or there was some damn good juice left in the bottles.
Well, I wasn't gonna take my waste glass back home, so I got to play a game of throwing into the hole from a good step away, while trying to not hit any of them midflight. 🙃
Krass, ich dachte der Witz ist, dass man den vermeintlichen Teufel nicht in Eichhörnchen-Gestalt vermuten würde, weil ein Eichhörnchen überhaupt keine diabolischen Merkmale hat.
Oh man, my workplace switched to an external IT support company, InfoSys, which pulls basically the same scam.
When you open a ticket, they immediately write something underneath – typically a question that's already answered in the ticket – because it shows up in their statistics as low response times.
Then they'll do shit like split up your ticket into three new tickets for no good reason.
And if you happen to be on holiday for a few days and therefore don't respond, they'll close your tickets due to inactivity.
Then you have to open a new ticket and link to the old ticket, if you can still access it, and then re-answer the same braindead questions again.
Basically, if it's something you can solve yourself, you should, because it will take more time to communicate back and forth with InfoSys.
Yesterday, there was kind of like a fair in town and someone afixed a lifesize bat decoration to a random lamppost. I was so confused, since we don't really do Halloween here, and yeah, it is also quite early either way.
You have to click a random heading in the info section to the right of the code listing (or below it on mobile).
I do also find GitHub's URLs are much more user-friendly than the GUI, though.