I think evil is too strong a word for Amazon, I think benzos is one of the nicer billionaires but I have heard the horror stories from Amazon warehouses.

So unhygienic! Definitely don't want to sit on someone elsees fart cushion all day.

I think it depends a lot on what you are doing. For game dev, there is really nothing else but C++. Also most bad code can be good code if someone is intelligent about it, and use good names and comments. Also if they know how to search through the code and trace things. For massive group projects I can kind of see your point. Being ina. Rush makes it very difficult to write good code, something that is laid out well, is interfacable and modular which makes it easier to understand. I personally try to write all my code to where it's mostly an API to anyone else wanting to use it. Something where they don't necessarily have to dig through tons of esoteric and confusing code, but I like to have everything wrapped in nice little function calls, that handle all the edge cases within and have a little description.

I understand rushing makes this hard but that's more so a failure of the team leadership prioritizing the wrong things. If you are going to write code that's going to be used for 20 years, it's actually a much better use of your time to just write really clean and easy to understand and adapt code up front, and save yourself so much time in the future. The only time other people should really have to dig beyond the API layer of your code is when they need to debug or modify the functionality of your code. So to me it seems like you want to write the most abstract and stable and simple interfaces code when working on long term projects with multiple people, even if it takes 4x as long, and for little personal projects and stuff that will only be compiled once, you may just want to through 100k lines of code in a file and compile it and then forget about it.

Other things I do is wrap things and simplify things myself. I create my own libraries which I know that you as a professional programmer hate to hear, but I do believe in the power of simplicity and abstract compression if you really want readable code. Libraries have to be maintained if they are to be used in production, but inlining some of your own code into every project you do is very useful and doesn't rely on external libraries and can greatly simplify the code you need to write. I wrapped many C std lib stuff in my own code for this reason. It cuts my code in half often times, makes the code very readable and descriptive, and I can just add it to all my projects as a header instead of link libraries and stuff. Idk. Maybe sometimes you just have to weigh the upfront development time and cost with later reliability and simplicity, which I'm sure you do, but your managers might be wise to consider that as well. Having bad code isn't just bad for developers, it makes people using your product dislike the products. There are many reasons to just take the time to write better code and use better techniques at the cost of time, and to truly be successful you have to look beyond the next quarterly report and stock price and do everything in view of the long term. Efficiencies are often small by themselves and not worth it, but overtime efficiencies and good habits snowball into massive permanent buffs.

Idk I feel for you corporate software devs. I like coding but I can't imagine coding stuff all day that I'm not interested in and dealing with corporate code and libraries all day. I never really got into tech as a job for various reasons but one of the big ones is that I can't handle the stress of debugging other people's stuff for days on end. I can't deal with crunch culture. I get worse jobs in many ways but at least I'm not stressed all the time. Sometimes heavy mental loads are just too much and I have tol stop programming for the day or the rest of the day. I don't like the idea of being forced to think at a job, but I do jobs that many other people wouldn't like and it doesn't bother me.

Haha well I see you haven't met C yet.

All jokes aside complexity and chaos isn't just there for a reason. It has a purpose. Java and C are complex but also powerful. Things that are easy to use are often very limited in what you can do. Not always but often times.

Next time try bazzite. It mostly just works out of the box and the only tools you really need extra are lutris and protonup-qt which are both guis and can be downloaded from the package store. You don't really ever have to touch the terminal in bazzite. It comes out of the box with wine and stream and proton already configured and it has the best performing driver installed by default for your device.

Welcome brother or sister or nb thing inbetween! This is the way!

Yeah well bazzite was sort of my first real long term use of Linux, it was good for that purpose. Let me mostly just use the machine without needing to be a Linux hacker. I will probably move on to a more simple system after it breaks. It works fine as it is, I can solve many little issues it might have with repos or keys or something. Flatpaks are cool and all that, but some of the software I use like my tethering app, binary decompilers and compilers, and little misc tools aren't available in flatpaks. Sometimes if something is simple enough I just copy it into the bin folder I can't imagine that would cause many issues other than not automatically updating.

Using containers is just too much of headache for me rn. I'm usually pretty limited in my time, I work overtime most weeks. I'm often spending hours just trying to get one or a few simple things done in my off time. Fooling with extra complexity quickly just gets out of control. I don't want to use containers because, it's not integrated into the system, the file system isn't unified, it's tons of extra stuff to learn to essentially gain little to no benefit, and it often breaks more documented ways of doing things, and I rely a lot on documentation and forum posts and chatGPT and stuff to do these things because I'm just not on that level of Linux user yet. Reinstalling an operating system is fairly trivial to me. It's maybe a day, where adding all the complexity multiplies my inefficiencies over many days.

It's not. Just because you don't like something doesn't make it untrue.

They can't, and also they cant haul thousands of pounds of food there without a truck. Even if you lived in a rural area, growing your own food is incredibly labor intensive. Do you know that before the invention of nitrogen fertilizer, it took about 90% of the people on earth to be farmers, in order to have enough food? The global population never really exceeded a billion people until the 20th century.

Interpreted languages are very optimized these days, and get much closer to native C performance.

Also thanks internet stranger. <3

Hmm I guess but DNA is probably the most complex nearly illogical thing that I know of.

DNA is not meant to be stable, it is meant to mutate and evolve, also it wasn't invented, it manifested itself out of chaos. One reason why understanding it is so hard. It is not made like a machine, it doesn't have neat parts with clear roles or categories. It's sort of pure chaos all sort of working together in a giant orchestra without categories or bounds.