What is your favorite way to learn a new language, product, or tool?
For me, I prefer hands-on, with nearly all self discovery and as little guidance (written or instructor-led) as possible.
This helps me understand if something will be intuitive for me (and therefore I can budget a smaller amount of time or non-focused time) or if I need to dedicate a significant amount of focused time and energy, or even find instructor-led or curated options for learning.
How do you learn? Or maybe the better question, how do you prefer to learn?
Top comments (27)
I attack it by four different angles who will hopefully converge
First off, loving this topic!
I think like you I'm a hands-on learner, but on the contrary, I really prefer to get guidance and have someone show me how to do something if possible.
I'd prefer to have the person with me in person showing me how it's done, but if it's over video call that's okay too. I suppose I can also generally learn from someone typing instructions and guidance to me over Slack, but if it's a multi-step kinda process and/or something more visual, I really prefer to work through it with them.
I think this is my preference because a) I like the opportunity to ask questions on the fly and b) I have a pretty good memory for experiences. On the latter, I notice that if I'm on call with someone and we chit-chat a bit about something, then they help to teach me whatever the thing is I'm learning, I'll kinda group the two things together in my mind and it helps me to recall it.
Depends on what I am learning
Your tool examples are great. Unity is huge and has entire university courses dedicated to only parts of the functionality.
Postman is my favorite experience and I'm glad you highlighted it here. You can get it to work quite easily by working through the UI. Want more powerful features and functionality? If the UI isn't guiding you, they have great content built by people at Postman and the community.
Go for written tutorials rather than video tutorials.
That way we get to learn a lot more by exploring related things. But in case of videos, we just follow what is being done there and we only get a high level understanding.
A well written step by step guide/ tutorial is better than video tutorials.
Also, we get a clear understanding when doing hands on with written tutorials.
Only if the written tutorial clearly explain all steps. There are many written tutorials with unclear steps because of our little knowing of the background.
So, written tutorials for pace and video tutorials for clarity.
I really like written tutorials more than videos too. I find myself having to pause videos almost constantly because they go too fast if I'm trying to learn something for the first time.
I tend to be a "sandbox learner" :-) and I use simple quick-start examples illustrating the concepts, and, later on, minimal projects with increasing complexity. This can be based on video courses, books, articles. Usually I focus on leading examples and I learn self-paced, "without supervision" :-), this suits me best. This way I learned in the past 4 years the technologies such as Git, Bitbucket, Docker, Ubuntu, GCP/GKE ...
Ooo now I have some questions! When you say sandbox learner, do you prefer to learn things like Git in a browser-based experience and then apply that knowledge to Git on your local machine? I'm always trying to find a good balance between easy, safe, and close to the real thing.
Yes, good question … After viewing some video tutorials it was doable for me to install Git + Git Bash locally on Windows 10, and to open a personal account on Bitbucket. This way I created a minimal sandbox env to learn Git commands such as git clone, git status, git add, git commit, etc … thus no GUI at all, and this is also suggested in Git tutorials as best practice for learning Git. Next logical step was to invite someone from my team to test code maintenance and collaboration scenarios using cloud repos in Bitbucket, git branches etc.
If there is a course or tutorial with title "Learning {tech} in 6 hours", it's totally normal if you're not finishing it in 6 hours.
Just spend the first hour or the first section, not more than 1 hour. Then spend about a day or even a week to build something with everything you know from the first hour of tutorial if possible. This can be a small project that you can save in cloud drive, github gist, note, etc.
Continue the next hour of tutorial with the same step. The bigger the project you build, to may need to store it into git repository.
Yes! This is so critical for anyone at any level. Sometimes this is equivalent to a buzzword for SEO and other times it's a bad estimate from someone who may already have knowledge or experience in the areas covered.
I love how you broke it down. This is great advice!
I do learn while doing. I do absorb 20-30% from a course or any source and then go for implementation. And then I go for 50% and I do until 80-90%.
Then I do work on Good Projects and I do share all my learnings on lovepreet.hashnode.dev/
... long time ...
Technology became obsolete, return to 1. 😁
But usually most dev tech has some kind of examples on their website that I look at. From that I can usually gauge whether I can implement it in a project or not and if it's better than the current tech that I'm using or not. When it's better I either try to implement it into an existing hobby project or start a new one. Along the way i use google/stack overflow to solve any issues i run into. If i can't find solutions immediately, it goes on the backlog as "non mature tech".
Relatable on so many levels 🤣
Build stuff while reading documentation
I learn best by just jumping in and writing full programs in the new language. Mostly, writing cli tools first and then moving on to graphical items as I learn the new language. I rely on the online docs to teach me everything I need to know about a new language. Sometimes I buy a book.