[0] https://www.joelonsoftware.com/2000/03/29/painless-software-...
That's so little vacation. America is wild.
They choose? I’ve worked in a lot of companies in a lot of parts of the US, and have never heard of employers choosing a worker’s vacation days. That’s awful.
Lately I've seen a lot of 'unlimited' - read as less than your boss takes
In Europe 20 is the legal minimum
I took a job with "unlimited vacation" at one company and then AFTER I started my boss "explained" to me that "Unlimited means 4 weeks here." About two months after I started I was moved to a different team new boss. My new boss (same company) had clear deliverables and said, "Unlimited means Unlimited so long as you hit your deliverables." Glad I was moved to a new team.
There was also this weird flex I've had older coworkers do where they brag about never taking their vacation time and just cashing it out instead at the end of the year. It happens a lot less nowadays but it was definitely part of the "grind culture" to show you were a hard worker before, maybe it still happens in certain fields.
They said it was challenging because they couldn't loose the project bla bla and if everything went ok we would all be promoted.
People worked almost 24x7 for months. But the project got done with no major delays.
When time to credits came, a friend of the boss who was actually in another team got the promotion and we all heard that there were not enough vacancies for promoting the team but they wanted us to know that they appreciated the effort and it wouldn't be forget.
Months later, a layoff came and half of the team got laid off.
Since then, I only work extra time with OT and I demand that to be written as a plus in my formal evaluations.
Does it help? No. But
My style is to say sure then take 2 weeks anyway.
The boss often wants to feel like they've negotiated the "price" of an issue and won, regardless of whether they pay full price in the end.
The root cause was a previous change in requirements that was not well defined and explored a couple of years ago. None of the original developers are working for the company anymore.
We offered ourselves to fix that bug, but it would take at least a couple of weeks.
This bug prevents us to roll out other deemed important features. But, it is just a bug. No product owner wants it to say to his boss he spent 2w of an engineer solving an issue instead of building another feature.
The boss of the boss called. He says that this bug is not tolerable. He ask us to fix it. We say we agree and we already have screened and have a solution for it, but it will take 2 weeks.
He says he wants that earlier and we say no because no one wants to rush it as we don't want to cause a possible side effect if we fail in something.
The solution according to the is to not fail. Everybody goes back to the planning and no one picks that issue because the condition is to do it in half of time without fail while working on a new feature.
Go back to line 1.