103 karma · joined May 30, 2013
Complete shamelessness all around.
One thing that I am glad to have been taught early on in my career when it comes to debugging, especially anything involving HW, is to `make no assumptions'. Bugs can be anywhere and everywhere.
One possibility on origin (totally made up by me) could be that there were large stones lying around already as debris from e.g. earthquakes, celestial events and such and some groups took advantage of this and later people iterated upon it.
I have a weak memory in general, but I always remember the most mundane things in my life that I had no idea I still contained in my brain, triggered by a specific smell.
Another example is that when I moved to a new street, while crossing one road, I stumbled upon the edge of tram road and almost fell. Two years and counting, my brain always brings this memory up while passing the same point on the road..
I hate this a lot. It's gotten so bad the last couple of releases to the point that I try and use VS Code more in lieue of VS except debugging.
How they could let such fundamental functionality get broken is beyond me.
It's moot.
I don't know this for a fact, but, I'm thinking there must be a lot of books on public speaking that tout this "trick".
Once, I noticed that an exec started constantly prefixing her every answer with "Yeah that's a great question" and I said to myself, huh she must have just finished some leadership book!
Of course, it quickly becomes pretentious, if used on every mundane question.
Upon research and asking around, I understood that it's more of a false positive. A more paranoid person may have reacted differently in such a scenario. So, consistency alone may not always suffice.
It's not like there was no garbage output before, but it's the scale at which it can be done nowadays that is the key, I think.
Joking aside, of course, the ingenuity lies in finding a fitting solution to problem at hand, as well as knowing how to apply it.
As an example, consider a pointer to a const object as a function param in C++: I can cast it away in a second and modify it as I go on my experiments.
Any thoughts on this? How much of an extra friction would you say is introduced in Rust?
Not strictly similar, but this brings to my mind Graham Greene's masterpiece, The Power and the Glory, and his 'whisky priest'. Easily one of the best novels that I've ever read, so highly recommended to give it a look.
> Rewinding to the beginning of VHS tapes was honestly so long that nobody really forgot.
Hmm, if it took so long, wouldn't it have caused the reverse effect? That people would ignore it out of laziness? Maybe I'm too spoiled! :D
Being on the engineering side of things without much knowledge/focus on programming languages theory and the mathematical nature of computation, one feels as if all the niceties we have in popular PLs are just laws of nature that we just had to discover, whereas in reality they too had to be derived, tried, improved first. But then you study something like this and expect to be able to finally connect the dots and yet, it's still not immediately obvious how we arrived here!
Let's say you're a mayor who needs to increase the price of a public utility by 10%, what do you do? You announce that this price will be increased by 30%. People get furious, protests ensue (sometimes, it's even desirable if riots start) against such an outrageous increase! What to do? You should be as invisible as possible during this turbulent period and let others take all the heat, only to come out at the end announcing that yes, the people have spoken, and as a result the increase will be limited to 10%. Now, the people are happy; it's democracy in action, they have the power! The mayor is happy; he's got his increase happen. Happy ending.
*Your link misses a 'g' of .org