> Your code will be running slowly and you won't know why Ever hear the expression "tools, not rules"? Using big-O analysis while coding is almost the textbook

> Your code will be running slowly and you won't know why Ever hear the expression "tools, not rules"? Using big-O analysis while coding is almost the textbook definition of what makes someone a bad developer. That's of course not true if you're developing some foundational tool meant for other developers like Redis or whatever, but for the average developer doing complexity analysis at work is probably a red flag that they're prematurely optimizing their code, using company time to work on a side project, or otherwise doing something that's not contributing to the success of the business.