51–60 of 124 posts
Anki.
Anki is a good way to preserve progress made, and even make enormous amount of progress(in the medium and long term), but I don't think it was going to be a complete solution all by itself.
Step 2: Practice It
Step 3: Do It
Step 4: Teach It
Step 5: Repeat
“If you don’t use it you lose it” has been true for me.
With each step you’re evaluating yourself and repeating steps as necessary until you feel like you’re ready to move on to the next steps.
So for Cold Emails, maybe:
1. Learn - Research techniques online
2. Practice - Send some cold emails to friends or marketing colleagues for feedback, or post to a marketing / sales subreddit.
3. Send cold emails to a real contact list
4. Write about what you learned and how to do it
5. Keep finding ways to improve and new optimizations
I’ve a few different approaches I take depending on the task (and if I’m honest, my mood or levels of motivation): - a new programming language, especially something closer to a systems language, I have a standard set of things I’ll try to implement. Read/write a file. Turn a structured object into JSON, parse JSON to an object. Basic script that can be run from CLI, parses flags/args, reads stdin. Send a HTTP reques…
I do like your list and I agree, some bits that deal with CLI, web and parsing / making HTTP requests is the gist of what you need. I have debated making a project roadmap on GitHub that you can work on in any language and having a Swagger spec for an API so frontend people can implement multiple frontends and backend people can implement multiple backends.
- ebooks: libgen ... other sites
- chatrooms: IRC, discord
- forums
- documentation
2 pick a interesting project (if you're learning programming, create a software or an app, if you're learning an instrument pick a song, woodworking, a chair...)
3 have fun doing it
That's how I do it, not that I'm an example of anything, but people usually say I learn quickly.
You can skim the syntax on https://learnxinyminutes.com
Instead use a day or two on learning tooling and best practices and then try to implement a small toy project.
I’ve a few different approaches I take depending on the task (and if I’m honest, my mood or levels of motivation): - a new programming language, especially something closer to a systems language, I have a standard set of things I’ll try to implement. Read/write a file. Turn a structured object into JSON, parse JSON to an object. Basic script that can be run from CLI, parses flags/args, reads stdin. Send a HTTP reques…
When the time comes to use this new thing you will have a pretty good idea on how to handle it and you’ll only have to brush up on it a bit.
Last, but important: you never want to learn something just to learn it. Build something with it - understand why its’s useful and apply it, even on a small scale projecy
For any given atomic “skill” you can learn in the body of knowledge: Watch one, do one, teach one.