Dave: Ths is EXACTLY how i learn things... Having a concrete goal that is achievable and has a higher purpose and learning mandatory knowledge to achieve that goal.
Thanks dude, to recall my memory what i have ever experienced before, at the moment i feel sometimes lost and could not learn any new thing. Great vid..
^^^ This.... I've found this all of my life, the best way I've learned things (e.g. BASH scripting) is as a means to another end; while you DO have some holes in what you learn and incomplete areas you're vastly more receptive to the uptake of new bits of information (e.g. techniques that are new to you, etc.) as you have a framework that you understand so it just fits in like a puzzle piece.
side effect learning looks to be what inherently happens with generalised jack of all trades approaches, when you want to do it all, but can only do something of scope, so catch a wide net and pick up various skills along the way. the challenge to me is specialisation. because technology moves and changes quickly, it’s a challenge to absorb it all. focusing on a specific thing tangents to another, as new ways of doing things are now possible and a new version of the same language changes things over time.
Yeah, side effect learning is a great way to get started quickly, not necessarily for going from advanced to expert. That said, even for that kind of rigorous/theoretical learning, the idea of “interleaving” different topics results in more durable learning (see ericksson et al).
You learn tools by using them. Then it's try, fail, repeat. The key is to keep your "motivational flywheel" moving by giving yourself credit for making progress.
How I learned docker : Bang my head against a project for 2 weeks reading a book on docker finishing my project in 2 days Honestly sometimes going at it head first is not always the best way
I learned Java similar way. I got a new job and they just gave me a broken legacy Java library and said “Fix it”. After a month I was able to write decent java
Quickest way to learn something for me, read something on a new topic. Most durable way for me to learn something break something and then having to fix it.
@@vutuananh2437 Great! In that case, pick a small CLI application that you know and like -- preferably something with a few dependencies, config files, etc. -- and try containerizing it!
Okay, so you can basically learn a lot as you said by accident - as a side product of doing projects, but then you won't know anything about best practices most probably, how would you fill that gap?
I think that's a good thing to call out; thanks. Side-effect doesn't necessarily mean "hacked together," but even if you do an amateur job on your prototype, it gives you some experience to hang best-practices on. It's easier to set up a production-ready thing once you've already got some familiarity with the tools you'll be using. That's my experience, anyway.
That was your dog saying "I am NOT a CAT!" But seriously, Linux is the OS of the Gods. Python is the _programming language_ of the Gods. There _is_ only vim and there are only *nix type operating systems. Fail to understand these and you will be lost. You can _never_ learn any of this without actually just doing it. Courses will not help you become a pro. They can give you a taste but they will never make you understand what is really going on under the hood.
I don't necessarily agree with the sentiment that courses will not help you become a pro. They will not *make* you a pro but they definitely help you to become a pro. Something many people lack when "learning" Linux is a basic idea of what everything does. I learned Linux "the hard way" - by doing things yet there are many things that took me longer to understand than they should have. Things you don't necessarily need to accomplish something but that make your day to day life easier. Take this example: Many people add random print statements to their code to find out where things might not be going where they should be, in a program they wrote. "The programm printed 'Boop' so it correctly evaluates that if-clause, but it still doesn't do what I want... weird - let's add another print to that function that is called inside the if-clause" This approach works but is horrendously inefficient. Had that person learned to use the debugger they'd be able to find their issue in no time. Only that in most cases the debugger remains an enigmatic tool that many people seem to ignore - until you tell them about it and show it to them. Many courses take the time to do exactly that. They also go into basic theory - the foundations of whatever you're studying in that course - and explain why things are the way they are. Also I'd say courses are vital for introducing you to a topic -as you said, they give you a taste. They show you what's out there and where to look. They won't *make* you a pro, but they definitely help you becoming one. You just shouldn't solely rely on them, neither should you rely solely on a college or uni education. Practice makes perfect and setting a goal to achieve something - using the technique of side-effect learning mentioned here is part of that practical learning process.
Exactly how I learn things and how to keep them in my head for a long time.
Dave: Ths is EXACTLY how i learn things... Having a concrete goal that is achievable and has a higher purpose and learning mandatory knowledge to achieve that goal.
This is the only way I can code. I need a purpose to learn it
Thanks dude, to recall my memory what i have ever experienced before, at the moment i feel sometimes lost and could not learn any new thing. Great vid..
^^^ This.... I've found this all of my life, the best way I've learned things (e.g. BASH scripting) is as a means to another end; while you DO have some holes in what you learn and incomplete areas you're vastly more receptive to the uptake of new bits of information (e.g. techniques that are new to you, etc.) as you have a framework that you understand so it just fits in like a puzzle piece.
To learn IT, READ and PRACTICE. There never had been any secret about this.
side effect learning looks to be what inherently happens with generalised jack of all trades approaches, when you want to do it all, but can only do something of scope, so catch a wide net and pick up various skills along the way. the challenge to me is specialisation. because technology moves and changes quickly, it’s a challenge to absorb it all. focusing on a specific thing tangents to another, as new ways of doing things are now possible and a new version of the same language changes things over time.
Yeah, side effect learning is a great way to get started quickly, not necessarily for going from advanced to expert. That said, even for that kind of rigorous/theoretical learning, the idea of “interleaving” different topics results in more durable learning (see ericksson et al).
You learn tools by using them. Then it's try, fail, repeat. The key is to keep your "motivational flywheel" moving by giving yourself credit for making progress.
How I learned docker :
Bang my head against a project for 2 weeks
reading a book on docker
finishing my project in 2 days
Honestly sometimes going at it head first is not always the best way
I learned Java similar way. I got a new job and they just gave me a broken legacy Java library and said “Fix it”. After a month I was able to write decent java
Thank you
Black hoodie only available in Small size. Is it just out of stock ? I neeeeed oooone !!
I cant see the merch....
I can see the merch images on iOS RUclips app.
Great vid 🙂
Can't see any merch suggestions on Android app.
Quickest way to learn something for me, read something on a new topic. Most durable way for me to learn something break something and then having to fix it.
Merch thing shows up for me.
Using qutebrowser's built-in adblocker.
What project do you suggested if I'm learning Docker ?
What skill are you already good at?
@@tutoriaLinux I know things about Linux, Network , Visualization
@@vutuananh2437 Great! In that case, pick a small CLI application that you know and like -- preferably something with a few dependencies, config files, etc. -- and try containerizing it!
@@tutoriaLinux Thank you :D
Okay, so you can basically learn a lot as you said by accident - as a side product of doing projects, but then you won't know anything about best practices most probably, how would you fill that gap?
I think that's a good thing to call out; thanks. Side-effect doesn't necessarily mean "hacked together," but even if you do an amateur job on your prototype, it gives you some experience to hang best-practices on. It's easier to set up a production-ready thing once you've already got some familiarity with the tools you'll be using. That's my experience, anyway.
Hello
That was your dog saying "I am NOT a CAT!"
But seriously, Linux is the OS of the Gods. Python is the _programming language_ of the Gods. There _is_ only vim and there are only *nix type operating systems. Fail to understand these and you will be lost.
You can _never_ learn any of this without actually just doing it. Courses will not help you become a pro. They can give you a taste but they will never make you understand what is really going on under the hood.
is it a good idea to learn C just to get a better grasp of Linux?
@@nald420 No. Learning C to better understand Linux is like learning automotive engineering to become better at driving a car.
I don't necessarily agree with the sentiment that courses will not help you become a pro. They will not *make* you a pro but they definitely help you to become a pro. Something many people lack when "learning" Linux is a basic idea of what everything does. I learned Linux "the hard way" - by doing things yet there are many things that took me longer to understand than they should have. Things you don't necessarily need to accomplish something but that make your day to day life easier.
Take this example:
Many people add random print statements to their code to find out where things might not be going where they should be, in a program they wrote. "The programm printed 'Boop' so it correctly evaluates that if-clause, but it still doesn't do what I want... weird - let's add another print to that function that is called inside the if-clause"
This approach works but is horrendously inefficient. Had that person learned to use the debugger they'd be able to find their issue in no time. Only that in most cases the debugger remains an enigmatic tool that many people seem to ignore - until you tell them about it and show it to them. Many courses take the time to do exactly that.
They also go into basic theory - the foundations of whatever you're studying in that course - and explain why things are the way they are.
Also I'd say courses are vital for introducing you to a topic -as you said, they give you a taste. They show you what's out there and where to look. They won't *make* you a pro, but they definitely help you becoming one. You just shouldn't solely rely on them, neither should you rely solely on a college or uni education. Practice makes perfect and setting a goal to achieve something - using the technique of side-effect learning mentioned here is part of that practical learning process.
@@Skyfox94 thanks for the output