Reminds me of the show Alias, where the premise is that there's a whole intelligence organization where almost everyone thinks they're working for the CIA, but they're not ...
People learn things in different orders. For many people, low-level CTF challenges are their introduction to computer architecture (a good way to learn if you ask me!) If so, endianness is a novel concept to them.
While I personally learned about endianness before writing my first exploit, I've definitely made endianness-related mistakes before.
I almost always get better results from LLMs by going back and editing my prompt and starting again, rather than trying to correct/guide it interactively. Almost as if having mistakes in your context window is an instruction to generate more mistakes! (I'm sure it's not quite that simple)
It's going to become the "MP3 sizzle" that young people at the time started to prefer once compressed audio became the norm on iPods and other portable music players, along with film grain and the judder of 24fps video. Artifacts imposed by the medium themselves become desirable once they become normal an associated and in fact signs of "quality", when, in fact, they are introduced noise and distortion to an otherwise more pristine or clean signal.
See also the "warmth" that certain vinyl enthusiasts sought after from their analog recordings which most certainly was mainly dust and defects in the groves rather than any actual tangible quality of the audio itself.
With vinyl warmth is the result of a deliberate process. Professional masters are done specifically for vinyl to accommodate its quirks which truly changes the sound. They have to clamp down the dynamic range and tidy low frequencies or the needle will skip. Recordings with lots of busy high frequency information also can’t be physically captured properly in the cut. The resulting master is a version that purposefully doesn’t have as many volume swings and harsh highs or boomy lows. Smooth, cohesive, warm. There are also track ordering strategies which is why ballads tend to be at the end of one side and the high energy stuff up front where there is “resolution” to serve it. The mastering engineer is adjusting each song with all this in mind.
What most people think of "vinyl sound effects" are not what the "warmth" is about. That's just playback instability and waveform aliasing caused by shoddily made players.
Good vinyl is "wait, did we have this back in 1970s" good(the recorder yes, the player not exactly, hence the prevalence of vinyl sound effects)
Figuring out how to build a project in an unfamiliar language/build system is my least favourite activity, mainly because all the people who are familiar with those tools think it's "as simple as" and don't bother to write it down anywhere. I don't plan on learning every build system ever.
It would be interesting to know what kinds of responses humans offer across different values of Y such as:
1) looked on stack overflow
2) googled it
3) consulted the manual
4) asked an LLM
5) asked a friend
For each of these, does the learner somehow learn something more or better?
Is there some means of learning that doesn't degrade us as human beings according to those in the know?
I ask as someone who listens to audiobooks and answers yes when someone asks me if I've read the book. And that's hardly the extent of my transgressions.
At least if you're copy/pasting from stack overflow you presumably glanced at the change you are copying if only to ensure you select the correct text.
That would be a great reason to include the link. Would have been good idea for me to think about that 5-10 years ago. I just did it because I thought it might be helpful and it's cheap. Woops!
Ok but I'd argue Rust/Cargo shouldn't be an "unfamiliar language/build system" for most professional programmers these days. It's like a professional plumber being unfamiliar with solder. Like, yeah, you can do a lot without soldering, but imagine a pro just straight up not having a clue about solder.
It's worth learning how to do this stuff. Not just because you then know that particular build system, but because you get better at learning. Learning how to learn is super important. I haven't come across a new project that's taken me more than a few minutes to figure out how to build in years.
> Ok but I'd argue Rust/Cargo shouldn't be an "unfamiliar language/build system" for most professional programmers these days.
This isn't even close to true. The majority of programmers will be fine going their entire career without even knowing what Rust is, let alone how to build Rust projects.
A more accurate analogy would be a plumber not knowing how his wrench was manufactured.
Rust ranks 16th on the current TIOBE (https://www.tiobe.com/tiobe-index/), behind assembly, PHP and R. It is still not remotely as popular (as "based on the number of skilled engineers world-wide, courses and third party vendors") as C or C++ (to say nothing of how dominant Python has become).
The supposed ubiquity of Rust is the result of a hype and/or drama bubble.
reply