I kinda get it. To massively simplify: Without AI, your choice is 8 days implementing, or 5 days planning/designing/refactoring and 5 days implementing. With AI, your choice is 5 days wrestling with the AI to implement, or 4 days planning/designing/refactoring and 1 day with the AI to implement. I made up those numbers but the general idea is that good practices have a lot more leverage with AI, since the make the implementation "free".
Saying "there are models of ZFC where CH holds as well as models where it doesn't hold" sounds to me like talking about truth.
If I say "there are countries with an access to a sea, and there are also countries without an access to a sea" does it mean that there is no truth about whether seas exist or not?
Esperanto has been dead for decades. English is the world's lingua franca in trade, science and technology.
The idea that a language, any language, can be learned in a year or two is not consistent with observation. Just think of any immigrant you have ever ran into in real life.
> using un-introduced abbreviations (bonus points for abbreviations that have common meanings, e.g.: EG, NB, IE, ETC)
Every company should give their new employees a list of in-company invented words and abbreviations, so that you don't search for them online and then feel like an idiot for not being able to find them. Especially when the older employees use them as if they are common knowledge.
Of course it does. It alone does not make you a body builder, but compare the average person who does regular cooking with those who do not but eat fast food.
Step 1: Follow these best practices, they really help humans develop and maintain software.
Step 2: Whatever, we will just be "agile" and humans need to deal with it or get fired.
Step 3: Follow these best practices, they really help robots develop and maintain software.
Somehow "it reduces token usage" is more important than "it prevents developer burnout".
reply