Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trial
John Rothra
6,711 PointsCSS: Remembering It All - Read, Re-Read, Code, Re-Re-Read
Wanting to see if I'm alone in this.
I've found that, even though I went through the lessons, there are many things I forget weeks later. I'll look at my site (I use WordPress which isn't always the neatest once you add plugins, but I digress), see a problem or something in the code that's unclear, and then realize that issue was covered four weeks ago in some lesson. However, I can't remember exactly which lesson (maybe it was just a small comment in one video).
Here's what I've found to be helpful:
- When I have a question, read.
- Read some more, even re-reading the same article
- Playing with the code, trying things
- Re-re-reading stuff
Like with any training, recall isn't going to be there at first, but only after re-encountering something repeatedly. I hold an PhD, but despite that degree, I can't recall everything from every seminar I took. I have to do research to refresh my memory.
Anyone else encountered this?
2 Answers
Daniel Gauthier
15,000 PointsHey John,
The method I use to remember things I'm learning involves three pieces.
The first piece is theory, which I approach using a traditional note taking fashion. I maintain a document for every topic I learn about that includes questions about -why- we do this or that, as well as core concepts, then paraphrase the answers in order to condense them.
The second piece is for the grind, which is the number one way I know to learn how to apply any coding I learn. I develop my own 'code challenges' which I keep in an organize pool. Every day I'll do a few of them chosen at random just to stay sharp and see what pieces I may need refreshers on. These are focused on the small things, like assigning background colors in css, or creating a simple loop in JavaScript to accomplish the problem presented by the code challenge.
The third piece is for the heavier stuff. I've been developing a "Techniques Collection" which is organized in such a way that whenever I see an advanced technique that is beyond the scope of a simple code challenge, I'll add it to the Techniques Collection. These are like self tutorials explaining a technique for future reference and giving step by step instructions on how to utilize the technique. An example of what would be classified as a technique rather than a code challenge would be "How to Add a Lightbox".
The core concept of it all is just creating a library of content for myself as I learn, which helps solidify what I've learned and prevents the need to scramble for things I remember seeing but can't remember where.
John Rothra
6,711 PointsThe best advice overall that I can think of to remember something: find what helps you and use it. It may be what I use, what Daniel uses, a mix of them, or something else.
Luke Pettway
16,593 PointsLuke Pettway
16,593 PointsDaniel this is all really great stuff!