3 ms·
From the parent post, and I quote: "What kind of problem takes 20 minutes to wrap your head around? Can you give me a working example?" I'm not against breaks,
by kelvin0 9y ago
From the parent post, and I quote:
"What kind of problem takes 20 minutes to wrap your head around? Can you give me a working example?"
I'm not against breaks, the issue here is that someone mentioned that 20 minutes is more than enough to wrap your head around anything. I gave an example where most (mortals) would require substantially more than 20 minutes. Are we talking about breaks? Or the fact that some geniuses are able to figure out everything under 20 minutes?
- archagon 9y agoParent poster here — just FYI, I certainly did not say that "20 minutes is more than enough to wrap your head around anything". Was only looking for examples to assuage my curiosity.
- kelvin0 9y agoI stand corrected. However it is a weird question to me and this mislead me into wondering how could someone not ever encounter any problem or task which takes more than 20 minutes to grok. Out of curiosity, what is it you do professionally? Do you get bored of it?
- archagon 9y agoWhat I meant was, there's often talk on HN about how distractions during programming will tear down your "mind palace" and force you to build up your mental model from scratch. There are certainly problems I've dealt with that take more than 20 minutes (or even days) to grok, but almost none where I couldn't talk to someone and then jump right back in unless I'm actively learning/researching/debugging (which is maybe 10% of the time). With most of my work, I only have to deal with local functions and behaviors without having to run the whole stack in my head. Everything else is on paper or in my notes. But it seems that many others don't operate this way, and I'm very curious about this division.