Development

Why Less Code Isn’t Always Better

Discuss the balance between code efficiency and readability. Explore examples of overly optimized code that confuses.

Tom Rune Sæverås

Tom Rune Sæverås

Tom Rune, a 29-year-old IT consultant at Noria Vest, has cultivated extensive expertise across diverse technology stacks. Over the years, he has gained in-depth experience working in industries such as shipping, insurance, and banking, which has equipped him with a broad and specialized knowledge base. Tom Rune has successfully utilized a wide range of technologies, including React, TypeScript, .NET, Java, Azure, AWS, and Spring Boot, to deliver innovative solutions in his projects.

Have you ever come across a piece of code that's been "optimized" so much that it is impossible to read? Let’s talk about the fine line between making code efficient and turning it into a cryptic mess. I’ll share some funny examples of code that’s been boiled down to one-liners or clever tricks that look cool... until you try to figure out what they actually do. In this quick talk, we’ll explore why readable code is sometimes better than the "simplified" version, and how to strike a balance between elegance and clarity.