I consider Dell’s naming scheme of their monitors the gold standard. It’s short, descriptive and easy to remember.
I got a U2720Q myself, and I know I got it because I know what size it is and when I bought it. I also got another monitor that’s seemingly just a random series of numbers. I can’t remember a single digit of that one.
From a maintainability point of view consistency is important. I’d rather work with an consistent but incorrect code, than correct bit inconsistent code. With a consistent code base it’s easier to do something about the incorrectness, especially if it’s consistently incorrect. It’s also easier to delegate the work.
Code is rarely correct forever. Sooner or later, requirements will change. What once was thought to be correct is no longer correct. It’s difficult to do anything about it if the code is inconsistent as well. It requires a lot of mental effort to understand the thought process behind some code.
I agree that correctness is the goal, but consistency is one of the best ways to ensure this goal.
One thing that isn’t mentioned regarding consistency is that it makes the code more searchable. When you start on a new issue you can easily find where you should do your work. You’ve maybe never seen this part of the code before, but you know how to find it.
This is impossible with a largely inconsistent code base. Anytime you start with a new issue you have to find a needle in the haystack.
The best way to reduce the climate impact of transport is with public transport. Elon Musk has always been anti public transport. The reason why he started hyperloop and boring company was to take away funding that otherwise would go to public transport.
AI is probably going to transform how code is written, but I don’t think AI will fully replace programmers. At least not in the foreseeable future.
Most of a programmer’s work is maintaining existing code. This is something current AI models still struggle with.