Why You Are Wasting Your Time Making Your Code Performant

I'm sure you may have come across some post in LinkedIn comparing junior vs senior code. They are unmistakable, with that fresh morning smell of heated arguments and even holy wars, with endless comments arguing why some option is better than another option or how something runs 1% faster. Sometimes they favour highly performant code, other times they favour much shorter code, usually including some nerdy or obscure feature of the language being used. These snippets of code are shared to show you how senior the original poster is, seniority being directly proportional to the amount of those obscure features they know and inversely proportional to the length of their code. Some other times they discuss functional vs imperative approaches, arguing about the time and space complexity of the different solutions. These discussions offer endless insights about the vast knowledge of the senior developers involved in the discussion. Calculating the price of discounted products One of those pos