I have lived with my grandparents for the majority of my life. My grandpa isn't the most intellectual person on this planet. Yet, since I've grown up I've always seen him as my intellectual equal and because of that he always listened to when I had understood a new concept.
I am sure that because of this 'in-built mechanism' in my family structure I got set up to be 'naturally talented' at explaining things since I was always used to put things into simple terms subconsciously.
What I am learning from this is that when I have a kid, I have to act like an 8 year old so that he/she will experience the same blessing as I did.
I still thank my grandpa for listening to my (most of the times) very long-winded and convoluted explanations, forcing me to simplify until I had a feeling he understood me well enough.
Apply it to people who you disagree with politically. Apply it to your relationships at home and work. It's basically what Fred Rodgers, Dale Carnegie, Marshall Rosenberg (and hundreds of others) all talk about.
--
This is not a novel concept, and it’s just a bit of fortuitous branding that Richard Feynman’s name got attached to it, but the Feynman technique is a framework for learning new things. It’s very simple:
1. Pick a concept you want to learn, such as “what is company stock?”
2. Ask some very practical questions, like:
- “What is it?” - “Why do we need it?” - “What alternatives are there?” - “When did it come about?” - “Who uses it?” - “What are its various forms?” - “Where is it commonly used?”
3. All of these questions will invariably branch out into even more jargon and concepts, such as “equity,” “preferred stock,” “voting rights,” “limited liability” and so on.
4. Repeat #2 for each of those branches. By the end, you should know the first principles so well you could teach the concept to a college freshman.
Three things about this framework immediately jump out at me:
(1) Learning something deeply is necessarily a lot of work. It’s not like you’re just answering “what is X.” You’re asking ten questions about it, each trying to get at it from a different angle, and then asking ten questions about each of those underlying concepts. The bottleneck to knowledge then is not so much ability, but effort.
(2) Learning something deeply is largely a function of the questions you ask. The greater “coverage” your questions span on the concept surface area, the better you will understand it. In this framework, asking good questions is a necessity.
(3) Questions are also where new insights come from. Once you understand all the factors which compose “company stock,” you’re able to toggle individual factors on and off, and ask questions such as: “can you have stock with unlimited liability?” or “what would stock in people look like?”
.
[1] https://alexpetralia.github.io/2017/12/25/NL-2017-12-25.html
This is the truth and it makes me struggle when I want to learn something but not so deeply. When learning a new concept, I often find myself dfs the tree and end up somewhere very far in a single branch without gaining the comprehensive understanding of the concept.
Here is the youtube channel link: https://m.youtube.com/user/Sepharoth64
Video on a.recall and s.repetition: https://m.youtube.com/watch?v=ukLnPbIffxE
[1]: https://www.goodreads.com/book/show/18770267-make-it-stick
> without [computer] slides
Are other types of slides allowed?
I could do my maths/stats stuff with a whiteboard or flip-chart for occasional images.
How do the biologists or ecologists get on? Actual (large, paper) charts?
I've had profs in college who were brilliant but couldn't teach, and profs who could teach but weren't brilliant (didn't produce much original research).
I wouldn't say the former group "didn't know their material well", but they didn't build up the material systematically. Pedagogy was neglected. Explaining things is an art that not every has the inclination to master (but they should).
I once had a professor who was new to teaching. It was a very painful experience and the entire CS class spent every lecture murmuring among themselves how terrible the lecture was. I gave him the benefit of the doubt and waited to 2 weeks to see if the lectures would improve. They didn't. At the end of one lecture I went and spoke to him and told him directly he was by far the worst teacher I had encountered at University and that as students we expected higher quality instruction.
From the next week on he was a good lecturer. It was a total transformation. I was seriously impressed. I guess he just never really thought about the pedagogical side of things before but to get such a rude wake up call really jolted him into action and he actually had a pretty good capacity to teach after that.
But what would be the best is if you are allowed to skip ahead lectures, etc at your own pace. The competitive incentive here would have been a big extra motivator.
Of course, you cant blame stagnating scientific discovery, stagnating prosperity, and soaring academic costs on the Academic Complex. Teachers, especially, are beyond reproach.
---
So what if—just another fancy idea of mine—what if Chomsky cannot find anything in my work that goes "beyond the level of something you can explain in five minutes to a twelve-year-old because" because, when he deals with continental thought, it is his mind which functions as the mind of a twelve-year-old, the mind which is unable to distinguish serious philosophical reflection from empty posturing and playing with empty words?
--Slavoj Žižek
https://www.versobooks.com/blogs/1365-some-bewildered-clarif...
This is a large understatement. In our industry, if you're not learning you are drifting backwards rapidly.
I aim for twenty hours a week of (unpaid) reinvestment and learning. Some weeks I still feel like that's not enough to stay current.
Does anyone else feel the same way?
It didn’t work for me at all, and ended up basically killing every joy in my side projects. If I missed a scheduled hour (because I was doing something else fun) I felt like a failure. I could only focus on “I should be working on x” instead of actually thinking about x.
These days I try to not worry too much about what I should learn/produce, and rather work on what interests me at the time. I’m probably not learning at the most effective rate, but at least I’m having fun.
I'm pretty sure this isn't true. Most of the "new" things in the industry are just rehashes of old things with a different coat of paint and some added abstractions to slow it all down.
And this doesn’t even touch on learning outside of ones field, which is great for well-roundedness and for discovering parallels one doesn’t necessarily find within a single domain.
If you're going for excellence in your world, which is usually the goal of the staff programmer, you're better off focusing on the details of the world you're in - new libraries, releases, details of governance etc. Yes you should learn new languages now and again, to dip your toe in other worlds; that's foundational and good and keeps you agile. But most of the stuff you see on HN isn't foundational, and so you don't really need to pay attention to anything not happening on your world.
Standing still as rotting is bad obviously, but to me, just seek things that provides a sense of eager. Be it walking, boxing.. "make it" passionating (as in seek what tickles that sense). If semiconductor physics does that, enjoy it. But the emotion is what motivates me now. I think it's more important to replenish that than learning. You'll learn later when you're fulfilled, and probably 10x times better and faster.
If you have just graduated yes you probably need to catch up especially if you are after a highly paid job, but for the more experienced one, no you don't have to be that anxious about it.
At some point I found my self spending more time on readying newsletters that were landing on my mail daily or weekly. Besides knowing what was that weeks' famous frontend library, it was adding zero to my foundational knowledge. I did felt that way. I just learned to let it go.
Now I am gradually trying to find my pace. The state were I can be aware of what's happening in the industry but also spend enough time on things that matter.
Staying current is overrated. You'd be better off spending most of those hours on CS fundamentals, written and oral communication skills, and probably exercise.
Many web developers have no choice but to chase fads. The whole industry is based on fad-chasing, after all.
1) Write down the problem
2) Think real hard
3) Write down the solution
In other words, the "draw the rest of the fucking owl" of general learning/problem solving.
* write down the name of a concept
* write down an explanation of the concept in plain English, identifying the bits you don’t know
* review the explanation, going back to source material if there is something that you haven’t yet explained, and repeat step 2
* simplify the language and rewrite bits where you have paraphrased the source material
[0] https://collegeinfogeek.com/feynman-technique/
[1] https://mattyford.com/blog/2014/1/23/the-feynman-technique-m...
[2] https://mystudentvoices.com/feynman-technique-learn-and-reta...
1) Write down the problem
2) Frame it in such a way as to pique Feynman's curiosity
3) Wait for Feynman to tell you how he solved itIn fact this is kind of a subtle point. There are two functions that teaching it to a third party is performing. The first is that of burning the material into your memory and the second is getting to an exposition that the third party understands.
Well... the second part is not necessarily necessary. It depends on your goals, but let's say you are only trying to further your own understanding then perhaps all that is really required is getting the material into your memory in a robust way. Just explaining it out yourself enough times to actually wire all the nuerons up in a complete graph is massively beneficial.
Key. Teaching is a learning process for both teacher (who must condense and reduce to essentials, and so integrate) and student.
If the child is old enough to ask good questions (and is encouraged to), so much the better. The feedback is valuable, and the teacher can continue to reduce/integrate at a somewhat higher level.
Is this some odd kind of hyperbole about teaching techniques? I don't see that it's helpful.
If I'm struggling with it, the odds of a toddler being able to comprehend it are slim to none.
The kernel trick? Quantum computing? Even good old eigenvectors? (Or, heaven forbid, genuinely advanced mathematics?)
The best professors in the world couldn't convey these things to a 2 year old, and not for lack of understanding.