dandroid

The 20% is relatively new. It was always around 10%, and then restaurants started "suggesting" higher tips on the receipts, and basically guilting people into tipping more. It was pushed up to 15% in the mid '00s, and then only pushed up to 20% during Covid. I have been called a piece of shit human on multiple occasions because I didn't buy into the restaurants randomly changing it on me. There is immense social pressure here around tipping.

The restaurants have a financial motivation to want the tips to be higher, so I feel like it's a conflict of interest for them to be suggesting the tip amount. I think the government needs to get involved and regulate tipping or even outright ban it at this point, because restaurants aren't going to stop pushing the envelope at 20%.

I live in the US and I have never tipped housekeeping, nor have I ever heard of someone doing it.

Exhibit A: All of Lemmy. Seriously, this entire place, especially this community it just controversy and outrage. It's so boring.

Mega Man Maverick Hunter X and Mega Man Powered Up are my two favorites.

Disclaimer: I'm a huge Mega Man fan.

I imagine people who care about this sort of thing are more likely to report it. And people who care about this sort of thing are also more likely to be early adopters and go through the effort of switching to Wayland.

The way to get a more random sample is not something I want (built-in, automatic telemetry by default). So I'm fine with having skewed data for something like this.

WOOOOOO!!!!!

As a Sharks fan, I am ready to be disappointed tonight.

I respect other people's choices in what to consume, and I expect the same respect in return. I have no problem with people being vegan or vegetarian. In fact, most people I work with are from India and are vegetarian. We eat lunch together most days and no one has any problems with each other.

Unfortunately most vegans I know are extremely pushy and judgemental about their diet/lifestyle. They do not respect my choice in what to consume. This used to causes some preemptive judgements on my part, where I would get defensive immediately about my dietary choices, because I assumed they were judging me. Over time I have learned to control this reflex.

I can only assume that many people have had the same experience as me, and jump to the same conclusions.

I conducted coding interviews for a few years at a startup before moving to a bigger company where I had a smaller role.

For me, I never cared about if someone got the right answer. I have actually said no to people who got the right answer and yes to people who got the wrong answer (or didn't finish). The purpose of the interview is to see if I want to work with that person. If someone can write a perfect program, but can't tell me why it works, that gives me no insight into how they solve problems or if they even know how to solve problems. What I want to hear is their thought process.

First repeat the question, and emphasize the key details. Speak an example input and output of the function so the interviewer (and you!) knows you understand the problem. Then start talking about what kind of algorithms or data structures you might use to solve this problem. Reference other common problems that might be similar, and how they differ. Specify patterns that could be used for this problem or even your comparison problem, and whether or not that will work for this one.

Doing all of these steps with spoken words helps your interviewer understand how you think, and they may give away hints to mistakes in your thought process, or even point out that you are misunderstanding the question entirely. And that's okay! It's better to work out the details when speaking about it before writing any code.

Treat the interview like you are solving a problem with a colleage in pair programming. Bounce ideas off them and see what they think. They are very likely to give hints if you talk to them in this way. If you are stuck, tell them! They might be able to reword a part of the question to help you think about the problem in a different way, leading you towards the solution.

AFTER you and the interviewer are both confident that you understand the problem, and you have discussed all the algorithms, data structures, patterns, etc. that you need, maybe spoken through a some pseudocode, or maybe written down a table of example inputs and outputs, only then start coding.

I have only ever packaged for RPM (the company I work for has our own RPM-based distro). How does it compare? I find RPM to be pretty easy, but I have nothing to compare against.