Many programming "best practices" taught today are performance disasters waiting to happen.

Hacker News is a community-driven platform for sharing and discussing technology news, startups, and programming-related topics. Through user submissions and comments, Hacker News offers insights into emerging technology trends, industry developments, and entrepreneurial ventures. Readers can participate in discussions, share their insights, and stay informed about the latest advancements in technology and innovation.

Hacker News

The post discusses the impact of 'clean' code rules on performance and provides examples comparing class hierarchy and switch statement implementations. It shows that following certain 'clean' code rules can lead to significant performance degradation.

"Clean" Code, Horrible Performance

Too bad you don’t allow comments for the general user on your blog, but only pay subscribers. Subscribers will suffer from confirmation bias since you won’t have a different opinion because nobody that thinks differently will pay to read your articles. But a different opinion can be very handy.
The code that you show in your article is not real-life code where Clean Code should be applied. Clean Code works great on Enterprise Software where the performance depends on the database since you are only dealing with information.
Enterprise Software is very complicated to write and maintain, so that is the reason we come up with techniques to make it easy to develop. That is one of the primary reasons Python became a very good programming language and guess what, it performed very slowly compared to other languages.
Outside of the Enterprise software I wouldn’t use Clean Code, every niche has its own proper frameworks and patterns to do the best code. For example, using clean code for writing a video game will be a huge mistake since dealing with real-time is important and, as you pointed out, that is not the best quality of clean code and there are already very good frameworks and patterns to do so in a very efficient way.
So, every time somebody says that some pattern or framework doesn’t work, is usually the opinion of a person that don’t fully understand it or doesn’t actually know how to properly use it.

I believe this article oversimplifies the issue by focusing solely on the performance of method invocations versus no invocations. The example program shown is overly simplistic, with most of the code consisting of structure and invocations. In real-world applications, business logic typically dominates the performance cost, making the overhead of invocations a small fraction of the total. Clean Code practices, such as modularity and maintainability, often outweigh minor performance losses in method calls.