> "That’s exactly the point. These are concepts that are far more common in interviews than they are in production web programming."
The list includes things like Big-O analysis. While, formal analysis is certainly not a day to day occurrence of most programming, knowing what the runtime complexity of the code you are writing is almost always important.
While, I generally don't care for most algorithmic problems, I am honestly concerned when someone can't tell me that something runs in O(n^2) and good probably be optimized.
EDIT: I should note, I'm not necessarily looking for them to use precise term here, but they should be able to clearly articulate it.
The list includes things like Big-O analysis. While, formal analysis is certainly not a day to day occurrence of most programming, knowing what the runtime complexity of the code you are writing is almost always important.
While, I generally don't care for most algorithmic problems, I am honestly concerned when someone can't tell me that something runs in O(n^2) and good probably be optimized.
EDIT: I should note, I'm not necessarily looking for them to use precise term here, but they should be able to clearly articulate it.