Not all jobs are measured by time spent on the clock, so no it doesn’t have to be that way. Many jobs can and should be measured by simply meeting productivity requirements. A parking attendants job is being present on shift because that is a requirement of that job. But a programmer’s job is to create software that performs a certain way. There is no time requirement of the product there.

Just cause you suffered your way through it doesn’t mean you should encourage others to do the same.

You are not wrong about the lack of corporate culture. But at the end of the day, is that worth giving up family time, company of your pets, a corner office of your choosing, with access to your own fridge and amenities, being able to receive people at the door at reasonable hours, and not having to commute asinine hours?

Many people will reject that notion.

But here’s the kicker: companies don’t care about your well being. They only care about the bottom line. What incentive do they have to cater to your needs? None, other than the minimum for employee retention.

This idea of “team building” is just smoke and mirrors. An excuse to not have to admit the real reason: adapting away from buts-in-seats as a performance measure is hard.

You’ve got bigger problems than labour relations when “having a pleasant feminine voice” is the success criteria you use to measure the performance of a reporter.

I dunno, this logic sounds exactly like the fucked up logic that went on in the conference room that dreamed up this shitty idea only to have it face reality and be pulled on day one.

It’s faster until you need the human operator to keep coming over because the anti-theft sensors keep getting tripped up by false positive readings. Or you need to find some vegetable code that a normal cashier has memorized.

Self checkout is great when it’s done well, and total shit when poorly executed. And unfortunately, it’s not always just a matter of technology (which normally keeps improving); it’s often a matter of business model: sometimes customer convenience is really important, other times loss prevention (which creates frustration) is more important.

I’ve seen countless good self-checkout experiences backslide into crap experience because the business felt that a controlled client is more profitable than a convenienced client.

Typing characters is maybe 1% of the job. The other 99% is understanding how the change affects everything else. Changing a single line of code in a function called by 1000 other functions each themselves called in 10 other functions can still potentially be more work and a bigger change than changing 9000 lines of code in a function called once.