As someone who teaches in tech, I am always interested in learning ways that educational material can be improved. Part of that is understanding how people are currently using the material at their disposal. So let's talk about how you are using your coding courses, tutorials, blog posts, and everything else out there.
Sidenote: I have written about this a little more here, but I'm positive I am missing all sorts of things others are doing so I'm creating this #discuss post to hear what is working for you!
Here are some ideas to get the conversation starts:
How do you practice what you are learning?
Do you just code along with the tutorial?
Do you create your own app afterwards?
Do you do the entire tutorial first, then create an app, or build an app that is different from the tutorial using it as a guide?
How often do you reference the same resource?
I am possibly at an odd extreme here; not only will I reference some blog posts and tutorials more than once, but I'll even find myself referencing articles that I wrote because I forget things after not using them long enough.
How often do you find yourself reusing resources?
Do you bookmark the great ones? How do you organize your collection of tutorials?
What courses or tutorials do something awesome that allows you to learn more easily?
For instance, a really small detail in the React tutorials is the highlights on changed lines: https://reactjs.org/tutorial/tutorial.html#passing-data-through-props
It is subtle, but goes a long way in making it clearer what changed.
Or another awesome idea is having a mentor. Sites like Exercism.io do this, but it is incredibly hard to scale.
Everything from themed courses (eg Rails for Zombies) or learning through a game - I want to hear what has made your learning experience better and how.
How do you learn to go beyond the tutorial?
One of the biggest complaints against tutorials and courses that hold your hand is that you aren't "learning to code on your own." How do you escape this position and learn to go beyond what is taught in a tutorial?
Do you add new features to whatever you build in the tutorial?
Do you try implementing the same feature using different libraries or approaches?
Top comments (9)
Hi Jon,
I find myself trying to appy all of the methods you have described. An additional thing I'm doing now to solidify what I'm learning is to create my own comment-quizzes and then do those quizzes a couple of times a week.
for example, here is a comment-quiz about JS fundamentals
I have found that first you figure out a good pattern for the way you learn best, and after that it comes down to 2 factors, DISCIPLINE and staying MOTIVATED.
Discipline and motivation are 2 things that sometimes go well for me, and other times I struggle. I personally bounce between "I'm doing well" and "I know I'm slacking", on a regular basis. I believe everyone does. They key is consistency, which is not so easy to maintain.
For inspiration, I will end this post with this quote:
wow I will use your quiz if you don't mind 😊
That's just fine. Here is the same quiz answered, so you can compare.
Github Gist
One of the problems I've had was completing tutorial/courses. I started writing notes and posting them on Instagram which I wrote about in this blog:
dev.to/grepliz/a-review-of-javascr...
Writing notes have helped make the content stick better for me. I have frequently gone back to tutorials as a reference too.
I tend to want to code along with the tutorial but sometimes I just need a quick overview. I also like coding my own side/learning projects.
Any ideas what makes completing hard? It sounds like you get a good start and notes are also a great idea, so I'm wondering if you lose interest or if you get to a point where you feel like you know enough to do what you set out to do so the tutorial gets the back seat.
I think it's a little bit of both. I also think it was from starting too many things at once. So I kind of a have a new rule that (unless it's for work specifically), I will only do 1 tutorial series/course at a time.
Makes sense, and probably a good rule to consider :)
Good question! One that to me is a full time concern.
When learning a new subject, i always start by collecting links.
Once i have a nice collection thats hard to sort through, then i put that link collection in a new github repository, like the beginning of an awesome list.
Then i turn those lists into pages that i continually reference and update.
A good matured example of this is my work around learning github pages, with a ton of related info, that is continually growing to become more pages:
infominer.id/web-work/github-pages...
infominer.id/web-work/github-pages...
infominer.id/web-work/static-site-...
So the more i learn the easier it is for me to remember and/or share with others.
As you said, there are always details that need to be brought to attn, and i can copy sections over w the link as necessary.
Its an easy, fairly passive, form of content creation that is just part of my workflow now.
This is a nice way of making notes that are easy to reference in the future. Thanks for sharing!