1,309 karma · joined February 22, 2017
https://stc.sh/
If we hire people based on IQ scores/things that correlate with IQ scores, we should not be surprised if high IQ leads to better outcomes.
correlation != causation
If IQ tests were presented in, say, a physics context as a serious experiment, the presenter would be laughed out of the room. Taking them seriously and uncritically indicates nothing less than a complete lack of understanding of how the scientific method is to be carried out and how its results are to be interpreted.
https://en.wikipedia.org/wiki/W._Edwards_Deming#Seven_Deadly...
/"<CR>xnx
(or similar) in vim to delete the quotes on a multi-line block. Even that is annoying. But with the unicode quotes I have to do a bit more conscious searching, which is a distraction.Of course, the fact that the text is modified in any way is user-hostile. I don't mind re-typing a code example (since I'm trying to learn it), but I like to copy-paste sometimes (e.g. data literals).
I paid for a DRM-free ebook that's meant to be copy-pasted. We have a universal paradigm for how plaintext copy works. Apple charges a premium for good design. Ebook readers are generally supposed to get out of your way and let you focus on content. There is no reason for Apple Books to have this behavior.
“ghci> putStrLn (pretty 10 value)”
Excerpt From: Bryan O’Sullivan, John Goerzen, and Donald Bruce Stewart. “Real World Haskell.” Apple Books.
When you only copied: ghci> putStrLn (pretty 10 value)
Note that the quotes around your actual selection aren't even the ASCII quote character; you get horrid unicode quotes that are easy to miss if you're just trying to run a bit of code in your REPL. This isn't even a DRM ebook, so it's not like Apple is being compelled by contract to insert a citation. It's awful, user-hostile behavior that removes one of the main advantages of digital-vs-hardcopy coding books (copy/paste), and AFAIK there's no config that lets you disable it.I requested delivery-with-signature on a $4k iMac and it got delivered to another house three blocks away. They didn't ask for the signature (though they were supposed to); they just left a $4k computer on the curb. It was marked as delivered. I'm lucky to have an honest neighbor who brought it to my doorstep (no thanks to Apple and their logistics partners).
In vi and Word, you're not worried about state changes outside of saving the current state and, possibly, undoing some number of steps. In a VCS, you might need to check out, merge, or compare arbitrary states from the history, and doing this inherently requires a deeper understanding of how the history is stored. A good VCS should expose these internals in a clear way. In my experience, working with even 1 teammate immediately requires you to have some mental model of how your VCS deals with merging different histories.
That said, it's up to the VCS's interface to make these things clear. Git's mental model is simple enough, and the porcelain can do some of this stuff very well, but CLI is arcane; I end up storing extremely common functions as shortcuts because I'd never remember them or want to type them even though I use them dozens of times a day.
This is true at the largest scale, but the math classes that most people take are directly applicable to (and often were developed partly to solve) physical problems. I, too, found the high school presentation of math dry and boring until I took a good physics class, and I was amazed by how much of the math I learned was directly useful for that subject.
Unfortunately, the dry treatment math gets in high schools also usually fails to highlight the beauty and subtlety of pure math. I didn't realize how much I loved pure math until I took my first proof-based analysis class after junior year of college.
I think we're seriously failing both the applied and pure camps of students with the way we currently present math. The fact that it took me till nearly the end of college to really like it, despite my proclivity towards the abstract and technical, really drove this point home for me.
You need to slap a decode anyway on reads from subprocesses in python3, and files open in Unicode mode by default. Wouldn't that fix the majority of silly UTF-8 compat bugs? Or am I missing a class of bugs that's not avoided automatically by python3 strings?
Specifically, if you're really concerned about a delta, removing the origin is good for visualization; it lets you just see the difference between two trends (in particle physics, you can show an energy excess this way). Likewise, for exponential phenomena, log plots are the correct choice, since uncertainty will be magnified for larger values. In both cases, of course, you need to include error bars, but that is always true. But I don't think you can "instantly distrust" someone who is using these techniques when they are valid.
What I really miss is upgradeable RAM and SSD. Still using a 2010 MBP because I was able to upgrade it; that's no longer possible.