Having a fast and responsive app is orthogonal to “knowing your big Os”. Unfortunately, most tech companies over-emphasize algorithms in interviews and downplay systems knowledge, and I believe that’s one reason behind sluggish apps and bloated systems.
I’ve seen this play out repeatedly. Interviewers ask a LeetCode-style coding question, which is then followed by the ritual of discussing time and memory complexity. Candidates ace the answers. But then… their “real” code suffers from subtle yet impactful performance problems.
Focusing on big O complexity rarely matters in most apps. Sure, it’s important to think about your algorithmic choices, but there are so many more details to worry about that have a direct impact on app performance and responsiveness. Let’s look at a bunch of them!

Pointer's platform is  dedicated to providing insights and resources for software developers and technology enthusiasts, focusing on programming languages, frameworks, and development tools. Through articles, tutorials, and coding challenges, Pointer offers insights into building software solutions and advancing programming skills. Developers can learn about new programming languages, coding techniques, and best practices in software development.

Pointer

Julio Merino: Good performance is not just big O - Julio Merino (jmmv.dev) Having a fast and responsive app is orthogonal to ‘knowing your big Os’ He says most tech companies over-emphasize algorithms in interviews and downplay systems knowledge.