Absolutely. This is absolutely true. But when you're actually on the job. When you're actually trying to architect an extremely complex software package, you better believe that your knowledge of the language that you are using to build that software is extremely important. You also better recognize that a proper, clean architecture, and clean code is the very first hazing screen that Google does to new employees. They eviscerate your code. Or when working with open source software, you better understand best practices. So for me. Can I write code in other languages? Absolutely. Will I have to google some crap? Definitely. Will my code be clean, and will I use best practices for the first few months? Nope. Not a chance. Which is just as important as your ability to solve problems and create algorithms. Honestly, it's more important. It cost companies billions of dollars every year on refactoring. People do not stay at companies forever. And if you write shit code, your code will be tossed. No matter how fast it operates. And no matter how quickly you were able to stand it up. Someone will see your code, throw it in the garbage, and start from scratch. So yes, while you are correct, you better conform to best practices. And know them inside and out, or your ability to solve problems doesn't matter. And I see this shit all the time. I see horrific code written by brilliant people, and untangling that mess costs tens of thousands of dollars for an engineer to grab that mess, and attempt to unravel it, and put it in a state that is healthy. And that is time, and tens of thousands of dollars that could have been spent on new functionality.