A colleague of mine brought up an interesting behavior in console.log that I wasn't aware of. Because of how things are evaluated, sometimes your console.log might end up loading lazy and thus resulting in results you didn't expect.
There's a good discussion about this and explanation of how it works and how to go around it in Stack Overflow:
I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin from the late 20th century.
These days I do more Javascript and CSS and whatnot, and promote UX and accessibility.
A colleague of mine brought up an interesting behavior in
console.logthat I wasn't aware of. Because of how things are evaluated, sometimes yourconsole.logmight end up loading lazy and thus resulting in results you didn't expect.There's a good discussion about this and explanation of how it works and how to go around it in Stack Overflow:
stackoverflow.com/questions/405744...
I think that's pretty out of date (2010?) and it doesn't behave that way in current versions of Chrome.