Live data from Hacker News

The more you learn, the faster you can learn

pranay.gp

31–40 of 103 posts

Re: The more you learn, the faster you can learn

#31
Relying on fast estimations is one of the most powerful aspects of the way our brains work. But applying the skill of finding and applying fast estimations exclusively to every topic--like reading SparkNotes over an original piece--is a good way to eventually know very little.

Suppose any rate of decay in the things you retain. If your starting point is already small, losing any of it comes at a high cost. At least when pursuing mastery of a subject, you are repeatedly faced with new ways of understanding the basics, to the point that they are innate and automatic. You might forget small specifics which you can later find in your known references, but without mastery you might instead forget the basics--and relying on a reference for those basics means it's much less clear when they are aptly applied.

I would hazard a guess that that's why people have always tended to master only one or a couple skills, but people congregate and work in complement with others who have mastery over other skills. The community is the entity with knowledge over many domains--not the individual who learns tons of surface material. And simultaneously, everyone does learn a little bit about a lot of topics from time to time. But that balance is important--so I wouldn't personally weight so heavily the cursory synthesis portion of it as OP did.

--

Also, a little advice to OP. Drop some of the grandiose introduction. 100% of the links I clicked in the first paragraph were more disappointing than their descriptions led me to anticipate.

Re: The more you learn, the faster you can learn

#32
post #14

“I left an important part out of the process above - how do you actually find the best resource. I don’t know. That said, I’ve gotten “lucky” enough times that I think I know how to optimize for finding it.” Pro tip: No, you don’t. I’m game to explain it over coffee to the author, who seems to be in the Bay Area, but this writing reads a lot like someone who just started to scratch the surface on abstract learning an…

Could you explain it in a blog post for those of us that don't live in the bay area?

Re: The more you learn, the faster you can learn

#33
post #5

This describes me pretty well. I'm a dedicated learner, and I think it's what I do best. I don't master topics. Even the information about the thing can be a distraction. It's about synthesizing info into your working knowledge. Everything is reference. CSS is a great example. Do I know everything about it, even after 10 years? Nope. But I know it well enough that a quick reference is all I need for any problem. Prog…

"The determined Real Programmer can write FORTRAN programs in any language." - Ed Post, Real Programmers Don't Use Pascal , 1982. There is a hell of a lot more difference between the various programming languages than their syntax. Natural languages as well - you can render idiomatic English in any language, and if you don't care very much about getting your intended meaning across (and your listeners are both patien…

100% agreed. You can write C-style code in JavaScript, but it won't be idiomatic C and it won't be idiomatic js.

Syntax is a very minor piece of the programming language pie. If Python, Haskell, and Rust all shared the same syntax an expert Python programmer would still have a hell of a time getting anything done in either of the other two languages.

Re: The more you learn, the faster you can learn

#34
post #28
post #14

“I left an important part out of the process above - how do you actually find the best resource. I don’t know. That said, I’ve gotten “lucky” enough times that I think I know how to optimize for finding it.” Pro tip: No, you don’t. I’m game to explain it over coffee to the author, who seems to be in the Bay Area, but this writing reads a lot like someone who just started to scratch the surface on abstract learning an…

I feel your tone is slightly too condescending, but I have to agree with the general statement. I'm responsible for hiring in my small department, and the OPs blog post would be a red flag. We appreciate if candidates show they can learn quickly, but it's not useful to us in isolation. You already need to have a good base set of skills (CS, physics) but more importantly the humility to accept that with 5 years of exp…

Ha! I wouldn’t be surprised if you found it altogether too condescending...

I generally find myself being a little more brutal with people who sound/read like me 18-20 years ago, partly because I think that being hit over the head can actually do some good. It certainly helped me, and I’d have done better to listen more quickly rather than having the echoes of those much wiser than me take decades to sink in.

I strongly favor raw learning ability over knowledge when hiring for most positions. It’s incredibly valuable to be able to transition from one space to another over the span of 3-12 months (depending on the domain). Some badges are harder to earn (e.g. mathematics, physics, hardware, distributed design), but I generally feel okay taking someone who is an expert in one space and pointing them at another space that relies on the same fundamentals if they seem like they can learn.

I do, however, prioritize two things above learning proficiency when hiring:

1. Accurate self-assessment. If you can’t understand where you are, you’re going to be a constant headache. 2. Not an asshole. An asshole can destroy a team, even if they’re brilliant.

I want someone to be able to learn deeply quickly, though. Generally, if they have that ability, they’ll have real depth in areas of prior learning. For candidates at the Senior Engineer levels and above, I’ll spend at least an hour or two before the interview reading their publications or digging in on their areas of stated expertise so I can ask questions probing to their edge (or mine). Sadly, I hit the candidate edge first for roughly 80% of candidates, and it strongly correlates to no-hires.

Re: The more you learn, the faster you can learn

#35
Interesting post! It's almost exactly what I've found that has worked well for me. Putting in the three or four hours at the beginning of the process of learning something to find the best resources is essential.

That being said, I do think the importance of mastering one or two things should not be overstated, and was kind of ignored in your post. Let me elaborate: for me my deepest skill has been 3D modeling and rendering: it's been about six years of pretty consistent practice, doing motion graphics, general modeling, animation, color theory, and really just trying to absorb all the knowledge I can about this specific passion. This process has been super useful for a couple reasons, and kind of worked to snap me out of the "generalist" learning mindset. For example, I've found the learning curve over time for 3D modeling is pretty generalizable to other skills I learn: because I've sunk so much time into it, and have had to push through plateaus, and grind over hills, and realize when I'm just coasting, whenever I am learning other things, I recognize the emotion swing and know roughly where in the learning process I am. Similarly, the fluency I have with my 3D modeling tools (pretty much all the hotkeys burned into muscle memory) gives me something to strive for when learning other tools and skills. I know what fluency feels like now, and I know when I'm lacking in it.

For me though, the most important thing about pursuing mastery of one or two things instead of full generalization, is that it teaches you patience. Genuine patience. Something I feel is becoming a lost art in our modern time. Seeing how far you've come after six years of working at something, and then looking at your inspirations and seeing how far you still have to go, is a feeling that can either break you, and make you give up, (if you are impatient), or can help you, as you have the choice to just keep grinding away and choosing to be patient. 3D modeling and animation is a ten year (minimum) goal for me, and it's served as a wonderful learning experience for me in many, unforseeable ways.

To tie it back to your post, I take this "ten years" mentality to almost everything I choose to learn nowadays: I try to stay away from the fancy new frameworks and toys, and try to learn fundamental things that I can spend ten years learning and still have space to grow.

Re: The more you learn, the faster you can learn

#36
post #5

This describes me pretty well. I'm a dedicated learner, and I think it's what I do best. I don't master topics. Even the information about the thing can be a distraction. It's about synthesizing info into your working knowledge. Everything is reference. CSS is a great example. Do I know everything about it, even after 10 years? Nope. But I know it well enough that a quick reference is all I need for any problem. Prog…

"The determined Real Programmer can write FORTRAN programs in any language." - Ed Post, Real Programmers Don't Use Pascal , 1982. There is a hell of a lot more difference between the various programming languages than their syntax. Natural languages as well - you can render idiomatic English in any language, and if you don't care very much about getting your intended meaning across (and your listeners are both patien…

Eh... once you know a handful of languages, it's fairly easy to adjust to a new one. If I have experience in C++, C#, Ruby and Javascript, do you really think Java is going to blow my mind? Or I won't be able to write decent Python? I'm sure I'd pick up a few tricks and my code would get idiomatic but I am going to be 90% there from day one.

Re: The more you learn, the faster you can learn

#37

Earlier quoted context omitted.

"The determined Real Programmer can write FORTRAN programs in any language." - Ed Post, Real Programmers Don't Use Pascal , 1982. There is a hell of a lot more difference between the various programming languages than their syntax. Natural languages as well - you can render idiomatic English in any language, and if you don't care very much about getting your intended meaning across (and your listeners are both patien…

Eh... once you know a handful of languages, it's fairly easy to adjust to a new one. If I have experience in C++, C#, Ruby and Javascript, do you really think Java is going to blow my mind? Or I won't be able to write decent Python? I'm sure I'd pick up a few tricks and my code would get idiomatic but I am going to be 90% there from day one.

I'm pretty sure Erlang, Prolog and Forth would blow your mind.

Re: The more you learn, the faster you can learn

#40
post #37

Earlier quoted context omitted.

Eh... once you know a handful of languages, it's fairly easy to adjust to a new one. If I have experience in C++, C#, Ruby and Javascript, do you really think Java is going to blow my mind? Or I won't be able to write decent Python? I'm sure I'd pick up a few tricks and my code would get idiomatic but I am going to be 90% there from day one.

I'm pretty sure Erlang, Prolog and Forth would blow your mind.

Alternatively you can just grossly misuse them.
Post reply on HN