2,220 karma · joined October 30, 2018
The Polya process is another thing that comes to mind. In that model, if you were picked in the past then you are more likely to be picked in the future. That's the classic competitive exclusion "rich get richer" at work.
But here's the equalizer: Every distribution of possible outcomes under the Polya process has an equal probability of happening.
That strikes me as very interesting. Basically, if you were to run history forwards from the same starting point again and again, in some of those iterations your life would turn out significanty better than others. So, there is equality for everyone in that sense, but on a case-by-case basis it's more of a better luck next time.
Looks like I need to play Group or Not Group.
But then even for addition what's the inverse of 0? -0?
Edit: you can learn the basics with typing games in a few days but then you commit and switch to it full time and your WPM drops to like 10. It takes a while to build up the muscle memory again and it's a tough experience. Like learning to walk again.
Security is fundamentally asymmetric as you have to make 0 mistakes and the attacker only has to find one.
Really incredible book.
I need to get around to reading my copy of GGS. I think the geography hypothesis has some degree of validity to it, but certainly not a complete explanation.
Don't try to get the right answer. Try to get the right interviewer.
It's not even just spaghetti but things that are very obtuse too. I often need a debugger whenever I see things in the code like if(variant.sourceId == null) and then below is the large unnamed block of code that also doesn't give any indication of what it implies. Because I have no idea what it implies, I have no idea how the data got into that state, so it's like... What case triggers this code?
I often wind up refactoring that stuff after computing an understanding of it. It usually comes out significanty easier to read and not likely you require a debugger to understand it.
So I that regard I think debuggers enable unnecessarily difficult to understand code to hang around.
I know there is cyclomatic complexity. Mostly you can look at a method and tell "this is a clusterfuck" without needing to break out a specialized tool. I still feel like a lot of devs don't appreciate the simple philosophy of "don't make me think."
Im sort of taking the approach of learning the definitions of things via Anki in a real exploratory way. Just read about something that takes my fancy then I keep finding I run into definitions I've learned before and this time something that was previously gibberish made more and more sense.
Recently I read the paper posted here about how an optimal regulator needs to model what it's trying to regulate. I was amazed at how much more of it I had access to due to learning some definitions here and there.
I've picked up a Rubik's cube lately and am learning group theoretic concepts to help me solve it. I'm finding it a neat way to engage with the maths in a practical way too!
A common theme I have noticed is whatever it is, getting a geometric understanding of it aids intuition significantly. Others have mentioned the 3Blue1Brown videos. They are an excellent example of this.
These HN threads always bear out great resources and I've made note of (and acquired) a few of these, so I'll list them here.
Burn Maths Class - https://www.goodreads.com/book/show/26195956-burn-math-class
Book of Proof - https://www.people.vcu.edu/~rhammack/BookOfProof/
The Topology Of Numbers (number theory)- http://pi.math.cornell.edu/~hatcher/TN/TNpage.html
The Evolution of Trust (game theory) - https://ncase.me/trust/
Visual Information Theory - https://colah.github.io/posts/2015-09-Visual-Information/
Information Theory For Smarties - http://tuvalu.santafe.edu/~simon/it.pdf
Abstract Algebra - https://www.youtube.com/playlist?list=PLi01XoE8jYoi3SgnnGorR...
Algebra Cheatsheet - https://argumatronic.com/posts/2019-06-21-algebra-cheatsheet...
Control Theory Basics - https://www.youtube.com/user/ControlLectures/playlists
I guess what's mysterious is which of Korean / Japanese influenced which??
Korean has a slightly more complex grammar than Japanese. Not by much but there are some forms in Korean that don't exist in Japanese. But it's remarkable how they are almost identical.
You can't have it both ways.
We've seen it plenty of times when a product comes out and people with an agenda to make money off it say "buy this, it works" and then decades later it is discovered to have been toxic or harmful in some way.
Especially given the nature of this product, skepticism should be the default position.
Most of life is deeply political in this sense.
It's not worth listening to anyone's advice. Only experiment with your own life and find what works for you or die trying.
Life is political all the the way down.
Since interviewing is a skill and interview skill is used as a proxy for job skill and interview skill is a function of recent interview experience, job experience, and your mix of personality traits, and only two of those are roughly stable. Job experience is a slowly changing dimension, but recent interview experience changes very rapidly and it has a huge effect on interview skill, and the interviewer has no way to calibrate for it. Instead they always try to calibrate for job experience. Interviewers also don't have any hope of calibrating for your mix of personality traits.
The whole thing is basically a crapshoot. But I take comfort in that. I don't ever feel bad if I get rejected. I just see the process as essentially random.
Those people who couldn't program their way out of a paper bag in the first interview probably went on to solve whatever issue it is they were having that day (nerves, not ever having heard of modulo etc) and subsequently get more practiced by at least the 3rd interview. All of a sudden they can magically program.
I just don't buy the premise that these people can't program, get rejected from every interview, give up and drop out of industry.
I'd say the vast majority of them get jobs. And you're hiring filter can't calibrate for how the previous interviews have set the current candidate up for your interview.
If you could be a fly on the wall for every interview the candidate you just hired had done, there would likely be some in which you would have assessed "this person isn't capable of doing the job".
The signal/noise ratio in hiring is abysmal.