re: The Big O Notation - An Introduction VIEW POST

re: It depends on the job though. I do Java backend transaction processing so our team always needs to understand a basic understanding of runtime (an...

Yes, I think the key point is that after some good or bad experiences, most developers will have an implicit knowledge that helps deciding on how to program something and when something’s very slow to find out why.

That said, I’ve probably used it a lot of times. But I never wrote down or talked explicitly about O().

And by the way, I was a java Backend developer for most of my time and just recently started in the frontend as well.

code of conduct - report abuse