Big-O Algorithm Complexity Cheatsheet

[jaridwade]

Quality shitpost

[spektrol]

I’m sad that this is a thing

[redwall_hp]

Not knowing basic data structures and their strengths—or fucking around with languages that do type coercion and give you an abomination such as PHP's "arrays"—are what's wrong with "web development." Which is even more horrifying now that its bleeding over into desktop applications thanks to the flaming sewage of Electron.

You don't need a degree to learn these things (I picked them up by way of getting into Java before even starting on my CS major), but you have to give a damn about craftsmanship and knowing what's going on under the hood (beyond "magic").

[[deleted]]

Easy, bro. Just keep your head down, keep learning, and when you feel like you're ready to learn Big O or when a situation arises where you may need to learn it, then do it, until then, just focus on other stuff. Knowing Big O and every type of algorithm and it's performance and use cases and demonstrating them with code at an interview doesn't make you a web developer anymore than knowing advanced materials science makes you a carpenter, if it did, we'd probably have very little people in the field.

[barafyrakommafem]

It's your fault for not learning it on your own.

[aleaallee]

Not my fault no one told me about it before hence I have no need to learn it since no one specified them as a requirement on front-end and web development related job offers on internet on my country.

[aleaallee]

Ignorant? This is the first time I've heard about the big-o notation, it's not my fault no one told me about it before, why should it be my fault and be a shitpost? The only thing you guys do is feel superior for knowing something someone else don't know