3

So what has been your strategy for "learning and remembering" the theoretical stuff after your college and study life got over?

You know, in college , we would have exams and assignments, and made notes whole year to remember stuff , their used to be syllabus telling what to learn and how much deep you should go into a particular topic...etc
How are you managing to grow after these things are not an option anymore?

Or have you stopped looking into theory and how stuff works and just look for a solution online, implement it and go onto new project?

Comments
  • 1
    I learn what I need when I'm working on a project and whatever I pick up along the way is useful :)
  • 1
    You don't need to have someone tell you what to learn to learn. Try to challenge yourself with something that you find interesting or that can help you with your current job/field of employment and you'll probably pick up a thing or two along the way.
    And regarding the actual remembering of new stuff: apply it. The best way to learn something theoretical is to find a way to apply it and see it for yourself (as long as that's possible of course)!
  • 1
    And if you really desire some high-level material to learn, search on popular computer science journals for interesting algorithms etc
  • 0
    @alexbrooklyn @NEMESISprj but how do you keep those info for the long time in your memory? Don't you like, memorize stuff?
    I have this one learning model where i don't keep much stuff in my brains but rather make an article/ project out of it and put it on internet. Such that whenever i need that thing , i can look it up. But otherwise i can almost forget it completely. Not sure if its the right learning model
  • 0
    You just don’t forget it lol.
  • 1
    @yowhatthefuck TL;DR: I don't remember everything, I hoard everything.

    I mostly just have a giant list of links (and save the sites as PDF) with a one-line abstract for interesting things I found but which I won't directly need. Same goes for folders full of pdfs categorized by field - language - general applications (ie image processing - C - Optimization - article_about_optimizing_execution_times.pdf).
    If necessary, keep a short Readme-like index of what to find where with a short abstract of why you found it interesting (forcing you to read through it at least once helps you remember some things).
    Things that you can immediately apply in your work/side-projects/etc will be better remembered since you'll only remember complicated stuff when applying it yourself.
    For all other things, just search in the correct folder/remember an article about something that generally does the same thing you need when, as my earlier example, you want to optimize execution times.
  • 1
    In my experience, you'll only need to (and will) remember very complex in-depth theory when you're actively working on it for a longer period.
    It will cost you more time to try and keep remembering everything just in case you might use it once in five years than looking it up again and taking twice as long because you have to read up. Kind of the decision of "when to change a few function declarations into a library?": once you use it more often you need something better than simply defining it locally. Which comes at the cost of having to implement it.
Add Comment