3 ms·
Big O Notation: A Simple Explanation with Examples
- dp-hackernews 3y agoBig-O Notation - For Coding Interviews: https://www.youtube.com/watch?v=BgLTDT03QtU https://www.youtube.com/watch?v=BgLTDT03QtU
- jfengel 3y agoThe fascination with cyclomatic complexity has a lot more to do with being able to measure something, than with that something being important. Not only is it objective, but it requires no domain knowledge. It's "pure", which makes it easy to teach because you don't have to assume your students know anything about anything. And you can talk about it in interviews, because again they don't need to know anything about anything. But most of the work a programmer actually does requires you to know something about something -- and often, that will dominate the decision. Is there enough data that you can't sort it in memory? What's the appropriate key to use? Which is the critical section of the code that I should be optimizing for? It's not that it's useless, or that programmers don't need to know it. But we seem to use it more as a proxy for "this programmer spent the time to study this programming thing" than actually having any experience, skill, or knowledge that's relevant to this task.