No one, either in comments, nor in article, actually touches on form factor. The fact is that sedans are only good for moving people, but there’s better options for that: like cycling or train. The real benefit of an SUV’s form factor (or pickup, or station wagon, or hatchback) is that you can move cargo with it, the kind of stuff that you can’t move with efficient people movers.

Counter argument: https://en.m.wikipedia.org/wiki/Peter_principle

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.

problem seems to be […] intertwined language with culture

You lost the argument right here. Language is as fundamental to culture as the sky is blue.

The rest of your post amounts to “communication is important to function” and you are not wrong on that front. But you put no weight on the importance of culture too.

Consider this your wakeup call, that just because you don’t personally care about society having an identity doesn’t mean the rest of us don’t.

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.

The carbon sequestered in the earth in the form of coal, oil and gas hasn’t always been in the earth. After all, hydro carbons are in fact hundreds of millions of years of dead trees buried under mud sequestering atmospheric CO2. Which implies there was a time with all that CO2 in the air yet still trees to capture it. By releasing it all, we reset the biosphere’s clock to about a time when earth supported a different kind of life (one without us in it), but life nonetheless.

Frankly, the comparisons to Mars and Venus seem a bit overblown.

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.

Professional engineering is really about implementing processes and procedures that create reliable and dependable systems. Ultimately it’s about responsibility and risk management. Being an engineer has nothing to do with understanding or implementing technology or technical details and specifications (unless you are in an extremely junior level engineering position). That work already has another title: that’s called being a technologist (and there ain’t nothing wrong with that title and that work).

Very, very, very few technologists (including self-taught programmers, computer scientists, and even some engineering grads) have, or even understand the skills needed to manage technical risk, simply because those skills are not part of any of those curriculums and the licensure required to be recognized to conduct those activities. It requires knowledge, training, and certification specifically, not just a university degree or x years on the job. Of course, it’s not the sort of distinction that the general public understands by “engineering” since the public kind of just takes the act of technical risk management for granted.

Conversely, it’s perhaps also why the number of engineers with hands-on skills is shockingly lower than we expect: using technology is not on the engineering curriculum.

But yeah, just because the general public confuses technical skills with engineering doesn’t give you, lacking all three of : an accredited engineering degree, an engineering licence, and perhaps most importantly, malpractice insurance, licence to call yourself an engineer.

What does “stale code” even mean in this context?

Does that mean it falls behind stable? Just merge stable into your branch; problem solved.

Or is this just some coded language for “people aren’t adopting my ideas fast enough”. Stop bitching and get good.