They want to eay without paying the cost of bringing food to market. It's pernicious entitlement, made more outrageous by complaining about the greed of those actually providing the food.

So all these workers went to remote work in a company without a remote work culture, then were measured for a short period of time before a remote work culture and the policies and tools to support it could be ironed out.

Also, how are they measuring "innovation"?

I feel like this is still the case under "Agile"

We were use to this happening and most of the time it was for half a day or so. So we pulled out the kerosene heaters and the oil lamps for light. Bundled up and waiting.

We ended up being snowed in without power for two weeks. My mom and dad would take turns bundling up and walking a mile or so every few days to get to the roads to get more fuel.

One thing I remember clearly was cooking on out outside wood fire grill, which was essentially cinder blocks and a grate. No worry about running out of wood since there was always plenty around.

I remember the whole ordeal pretty fondly. As a kid it was a good change of pace and like camping.

I feel like my point is, if you're gonna want hourly work, pay for hourly work.

Take this scenario, I'm a highly productive dev. I work 5 hours a day and I'm burnt. But my manager makes my sit my butt in a seat for 8 hours. "Fine, whatever" I say.

Now crunch time comes and I'm pushing hard to 10 or more hours a day. I'm going to look back at the wasted time before in my seat with resentment. Because it's expected of me to give you more hours than my alotted 40 when the time comes, but when it's light I don't get to take that back.

If they weren't highly productive, they'd work the 40 hours and not meet their targets. Seems like the same situation except manager wants a butt in a seat.

> Other times they’ll get their parts done but be really har to get a hold of for other employees which might impede them.

Then they aren't really getting them done. There should be docs and enough information for someone else to interact and build off their work. The sync culture of butts in seats promotes high levels of tribal knowledge and over the mid to long run hurts velocity.

> Sometimes you’ll just have issues with other employees being angry that they seemingly make the same but put in a lot more effort which tanks the moral of all the other employees.

I gotta say, too bad for them. This comes from a butts in seats culture, which will drag everyone down to be the lowest common denominator.

You'll have a department where you have 90% normal devs, and 10% high productivity (per hour) devs. Force those 10% to be butts in seat and they are gonna go somewhere else.

Or browse hacker news all day. :)

What about them. Maybe they are highly productive because they are "part-time"?

Sounds like a good problem to have to me.

This is exceptionally bad, but sadly true.

If you have an engineer who can unblock teams and fix issues in an hour that others take a week or cannot fix at all, they are gonna jump ship if they can't be recognized.

At that point you've lost a valuable resource.