I thought we handled this years ago and coming from aviation experts is rather strange that they don't know the industry has migrated away from having a singular operating system that can't die to having a series of redundant fail-safes to fall back to when it does. It's strange to see the places where the microkernel debate still rages on....and how little investment is being made by those complaining multibillion $$ international corporations into projects like fuschia, RTOS, ZephyerOS, GNU Hurd, MIT Mach (or even Darwin), or even Minix!

I think these arguments are disingenuous and while they are valid the various organizations making them seem to aggressively not want to find solutions. I smell a strong desire to hold the vanguard of what they have built until they retire and can be unconcerned with compliance...understandable to a degree but harmful in the long run to be going so fast in the wrong direction.

Maybe Linux isn't a good fit, that's fine but they clearly don't care about that, they just don't want to implement anything and Linux is a convenient scape goat to not have to contribute back into an open source project even one on a BSD license

I don't think we should be rolling our eyes at an abundance of caution among most people concerning the adoption of AI and LLM, what is the harm in carefully introducing a technology?

AI doesn't need to become sentient to overthrow the natural order of the technocratic society we are currently holding together with gum and glue, it just needs to flip a burger and pump gas...

These corporate concerns are not some law of nature and it's up to us to support people when they are willing to fight for end consumers, something that modern redhat has all together abandoned

It's a false dichotomy to say you only have rock stars and as this person smugly tip toes around "normal people" when in reality you don't need rock stars anymore to make good software and let's be honest... Most rock stars didn't make good software they just make it in a time when software was generally even more crap than it is now.

You want to stop suffering among us plebs? Don't advocate for goofy rockstar developer propaganda, advocate for healthy work life balance and reasonable deadlines for things that truly don't matter. Stop letting sales and marketing write your software and stop taking opinions about systems design from your project managers and "technical leads" when they do not work in these systems day to day.

If you treat engineers well and respect them before a client who will drop you the moment a new product fits their need then yes you will lose clients from time to time but if you focus on making good software and happy people then you will attract stable clients who do the same and maybe the stock holders at the top don't get the ridiculous return per year that they expect out of more shameless companies but at least you have a half decent chance of sleeping at night...

I am well aware that we live in a world where this will be borderline impossible but the first step to solving a problem is admitting it

Does this article present findings from other projects? Does it have a personal code story? Does it use any data or even antidotal evidence to support it's claims.

The answer to all of these is NO it does not...it's just a half hearted article talking about a fundamental problem in modern programming with no real solutions other that an axe to grind that they can't even really elaborate on the origins of.

This is as true of Tesla, meta, Amazon, alphabet, M$ and apple and the reason this incident has sparked such catharsis is that it happens constantly. There is a great article to be written on why there is such hatred for these people but it has to start by admitting that people's feelings are valid and this article simply didn't have the spine to explore that idea. It was clearly written to allow the author to convince themselves of something they know they don't really believe and it doesn't deserve to be read by anybody on here, go read a vacume manual and you will find more thought provoking content.

1. He is disconnected from the reality of the situation he is in where he has had total autonomy of something he loves his whole life and cannot understand the concerns of others who are the backbone of his success.

2. He is disingenuous and needs to be a voice to disuate politicians and corporations from implementing something that would negatively impact his bottom line personally.

I'll leave it up to you to think about but either is quite sad for someone who is in a position of power to reduce the suffering of millions of people by just speaking out.

...I'm sure there is no economic correlation

The most common reason I see people become managers is because they weren't cut out for engineering work or it burnt them out over time. Many couldn't keep up with the ocean of new technologies and philosophies software has gained in the last few decades and so they are relegated to being a machine that checks email for twice a starting engineers salary.

Some managers really have done so to steward a company or team through a problem but so many more of them just want to "check out" essentially and in just a few short years loose most of the engineering context value they had and become some degree of roadblock to progress because sadly they want their cake and they want to engineer it too...they often create tasks and conversations they don't make sense or deliverables that are missing the point because they are no longer engineers no matter how badly they still want to identify as one after leaving a organic growing codebase.

I get it they have families and they are getting older and the kids coming out of college are honestly intimidating sometimes but that's a problem with the absolute lack of upward mobility within engineering and they unhealthy standards of modern corporate culture.

It's sad really. Very intelligent opinionated people slowly go from talking about solutions in concrete terms to a mix of language about deliverables, burn charts, agile, circling wagons, getting on the same page, and determining a funnel for Q4 while the software they are talking about has no unit tests and they themselves have determined that it's not part of the MVP...

If they could go back 10 years and hear themselves I wonder what they would think of the people they've become...

All code sucks, your job isn't to make great code it's to make great products and do your best to reduce the stress on your team, code quality will follow but first you have to be honest, open, and compassionate and sometimes a JR will take that personally and that's ok, eventually they won't or they will find out this industry isn't for them.