I did not because the only part I actually cared about was the bullshit clickbait title.

I said you need to understand what the code you wrote (as in, LOC that git blame will blame on you) does. Not that you need to fully understand what the code it calls does. It should be pretty obvious from context that I'm referring to copy-pasting code from stack overflow or an LLM or whatever without knowing what it does.

Are you seriously trying to equate "I don't know which instructions this code is using" to "I copied code I don't understand"? Are you seriously trying to say that someone who doesn't know how to write x = a + b in assembly doesn't understand that code?

If your job is to make websites and you make sites that don’t work on a browser that has over 100 million users you’re not doing your job.

If you actually have deep knowledge in a specialty, then you describe yourself as that specialty. ‘Full stack engineer’ coneys that you don’t have a specialty/are a master of nothing/your skills are _ shaped.

You consider calculating the hash of a few bytes to be heavy lifting?

So you’re arguing that “Object oriented” shouldn’t apply to languages that are oriented around objects?

I'm talking about C#'s unsafe keyword. It lets you do pointer shenanigans.