For the same reason the IRS makes you fill out how much you made last year. They know—they know to the penny. But making you fill it out is a humiliation exercise so they can "catch you out" and intimidate you.
Well in the case of the IRS, that, and you know, Intuit.
"I'm sorry" can mean "I am apologizing" but often it instead means "I feel bad". It depends on context which applies.
"I'm sorry for how you feel" without more explanation often sounds like "The thing that makes me feel bad in this situation is your reaction to it". It can come across as blaming the person for the feelings, regretting not being able to control others' feelings better, or dismissing the root causes of the feelings and any agency in them.
It's a bad apology because of the ambiguity, though passive aggressive types like that aspect. It's honestly a bad way to sympathize as well.
Counterpoint: Shaded spots at work parking lots in Texas fill up the fastest. Conspicuously so. Also, use of windshield visors is much more prolific than in cooler climates.
I can't believe your Texan friend never noticed those phenomenon.
> In what way(s) does Rust's C interop depend on cargo?
Do rust and cargo allow for multiple interpretations of the same C header file across different objects in the same program? That's how C libraries are often implemented in practice due to preprocessor tricks, though I wish it wasn't normal to do this sort of thing.
Rust and Cargo do not build C programs, so, the answer to that is "no", strictly speaking.
However, some people use cargo's build scripts to build c programs, which then you can link into your Rust program. Support would then depend on whatever the person wrote with the script, which in my experience usually delegates to whatever build system that project uses. So it should work fine.
I would expect so. Rust and Cargo don't consume C header files directly at all. They consume bindings generated by bindgen (or hand written if you prefer). So you could probably generate mulitple bindings if you needed multiple interpretations of a C header.
If the header files are consumed by C code that is then consumed by Rust then you'll have full support for what C supports because it will be compiled by a C compiler.
Are you saying the mentality is offensive? Or is there a business justification I am missing?
Note that employers do this as well. A classic one is a manager setting a deadline that requires extreme crunches by employees. They're not necessarily compensating anyone more for that. Are the managers within their rights? Technically. The employees could quit. But they're shaving hours, days, and years off of employees without paying for it.
If a company policy says you can expense meals when taking clients out, but sales people started expensing their lunches when eating alone, it’s clearly expense fraud. I think this is obvious to everyone.
Yet when engineers are allowed to expense meals when they’re working late and eating at the office, but people who are neither working late nor eating at the office start expensing their meals, that’s expense fraud.
These things are really not gray area. It seems more obvious when we talk about sales people abusing budgets, but there’s a blind spot when we start talking about engineers doing it.
Frankly this sort of thing should be ignored, if not explicitly encouraged, by the company.
Engineers are very highly paid. Many are paid more than $100/hr if you break it down. If a salaried engineer paid the equivalent of $100/hr stays late doing anything, expenses a $25 meal, and during the time they stay late you get the equivalent of 20 minutes of work out of them- including in intangibles like team bonding via just chatting with coworkers or chatting about some bug- then the company comes out ahead.
That you present the above as considered "expense fraud" is fundamentally a penny-wise, pound-foolish way to look at running a company. Like you say, it's not really a gray area. It's a feature not a bug.
> Like you say, it's not really a gray area. It's a feature not a bug.
Luckily that comes down to the policy of the individual company and is not enforced by law. I am personally happy to pay engineers more so they can buy this sort of thing themselves and we dont open the company to this sort of abuse. Then its a known cost and the engineers can decide from themselves if they want to spend that $30 on a meal or something else.
To give them enough money to buy that $30 meal as a personal expense, you need to pay them around $50 in marginal comp expenses.
It can be a win for both sides for the employees to work an extra 30-90 minutes and have some team bonding and to feel like they’re getting a good deal. (Source: I did this for years at a place that comp’d dinner if you worked more than 8 hours AND past 6 PM; we’d usually get more than half the team staying for the “free” food.)
I have found that the success of things like this depend greatly on so many factors such as office type, location, team moral, management style, individual personalities, even mean age etc.
I have worked in places where the exact opposite of what you describe happens.
As OP says, people just stop working at 6 and just start reading reddit or scrolling their phones. No team bonding and chat because everyone is wiped out from a hard day. Just people hanging around, grabbing their food when it arrives, and leaving.
We too had more than half the team staying for the “free” food, but they definitely didnt do much work whilst they were there.
I'm making the case that mandatory unpaid overtime is effectively wage theft. It is legal in the US because half of jobs there are "exempt" from the usual overtime protections. There's no ethical reason for that, just political ones.
At any rate, I think people who want to crack down on meal expenses out of a sense of justice should get at least as annoyed by employers taking advantage of their employees in technically allowed ways.
That might be a good tip, but people do get signals from their bodies when running a nutrient deficit. People crave calories when in a calorie deficit. And they crave carbohydrates, proteins, or fats when abstaining from them, at least some of the time.
yeah this would just be to help feel full. also don't underestimate the minerals that are in things that supposedly don't have nutrients, especially fiber
Yeah, story points approximate effort, so it's fairly impossible to be 10x on those.
JIRA has a notion of business value points, and you could make up similar metrics in other project planning tools. The problem would then be how to estimate the value of implementing 0.01% of the technology of a product that doesn't sell as a standalone feature. If you can accurately do that, you might be the 100x employee already.
reply