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 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?
The whole point is that random character sequences are often valid Perl
When I read the headline I also assumed “valid Perl program” meant it did something interesting. I was expecting to read an article about an interesting image to text conversion process that produced non-trivial Perl programs.
I assume you’re implying my confidence is due to having limited competence and thus overestimating my competence? The fact that I have imposter syndrome when I imaging trying to be a professional electrical engineer (despite having a degree) seems counter to your presumed argument.
One of the reasons I love Go is that it makes it very easy to collect profiles and locate hot spots.
The part that seems weird to me is that these articles are presented as if it's a tool that all developers should have in their tool belt, but in 10 years of professional development I have never been in a situation where that kind of optimization would be applicable. Most optimizations I've done come down to: I wrote it quickly and 'lazy' the first time, but it turned out to be a hot spot, so now I need to put in the time to write it better. And most of the remaining cases are solved by avoiding doing work more than once. I can't recall a single time when a micro-optimization would have helped, except in college when I was working with microcontrollers.
firelizzard
joined 2 years ago
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.