When you check e.g. building code or surgical procedures there is always a reason for something. E.g. use nails not screws because screws are brittle. Wash hand

When you check e.g. building code or surgical procedures there is always a reason for something. E.g. use nails not screws because screws are brittle. Wash hands before surgery because bacteria on your hands might kill your patient. But all of this needed to be proven at some point. With software, best practices often end up being "I would do it differently, hence it's a code smell". In this way developers are less like serious engineers and more like simple craftsman. They learned one way from someone (their first job, the blogger they respect etc.) and that's it, that's the correct way. That's how plumbers etc. operate. So the first step in becoming serious is proving why one thing is important and why we should do it. I am experienced in a way, and I mostly really don't know. I've seen projects built real serious that were impossible to change and duct taped things that were a breeze. So it's not what most people think.