> How do you know you are doing stupid shit if you don't know about complexity and don't know your algorithms? So, one cannot understand complexity without Big

> How do you know you are doing stupid shit if you don't know about complexity and don't know your algorithms? So, one cannot understand complexity without Big O calculus? I only learned the notation after years of calculating memory and runtime complexities for real-time code, and that was only for interviews. I don't find comparisons at the Big O level to be useful in day-to-day work. > Really, I do work on CRUD applications from time to time, and I often have to select algorithms based on complexity. Really, you often have to select algorithms at that level of granularity? I never have, in almost ten years of full-time development. I frequently have to select or tune algorithms based on the factors that Big O throws out, though. Then again, I do very little with searching and sorting.