>To put it in perspective, programming has barely had its Archimedes and its Da Vinci by this point. Best practices are a joke, and are usually based around sup

>To put it in perspective, programming has barely had its Archimedes and its Da Vinci by this point. Best practices are a joke, and are usually based around superstition, personality cults, and faith instead of actual empiricism. Standardization is moving backwards, and computer 'scientists' rarely solve the problems software 'engineers' actually have. I think a lot of software engineering is quite hard to measure reliably. That's why you get all these cults. Software engineering to me is kind of like writing an essay. It's all about having a structure that other people can understand. But like essays, it's hard to put clarity of thought and readability into metrics. Putting your essay into easily digestible paragraphs and chapters is like splitting up your program into functions and modules. One idea per paragraph is the same as a function doing what we can express in the function signature etc. These are all tried and tested methods which have been working over millenia of writing and carry over in software as well.