Cover image for Learning FAST for Devs". The 4 Deep Days Methodology ๐Ÿš€

Learning FAST for Devs". The 4 Deep Days Methodology ๐Ÿš€

pierre profile image Pierre-Henry Soria โœจ ใƒปUpdated on ใƒป3 min read
  1. Do researches in โ€œDeep Workโ€ mode for 30 minutes without interruption in the topic you need to know more.

  2. Note the best resources you found for the last 30 minutes and go deeply in the 3 very best resources you have found (it can be books, Kindle books, video tutorials). For instance, if I don't know Ruby on Rails, and I have to build a new project with it, I might go to GoRails.com (same, if I want to start learning Laravel and PHP, Laracasts.com might be a good place to start, and Egghead.io for frontend technologies).

  3. Learn these resources deeply (DONโ€™T DO ANYTHING ELSE!) for the next whole three days (with 10 minutes breaks every 50 minutes).
    Let your colleagues know that you are in a solo work training and cannot be reachable.
    Close Slack, don't check your emails, kanban/scrum boards, etc (no exception during these three days), put your phone on airplane mode.
    This is very important to avoid any interruption or thinking of something else that you could have seen in your emails, on Slack, text, news app.
    Busy. Deep Work. Don't disturb

  4. During your 10 minutes "chill out time", relax, take a cup of tea, listen to some good vibes, walk a little bit outside (without cell phones, Slack or emails!). Otherwise, you won't rest and your brain will still be actively working and you won't be as efficient as you could after your break time.

  5. Depending on the topic and what you already know, it can be shorter (or longer..).
    And SKIP everything you already know without exception. You need discipline at this stage. You'll see, it's worth it!
    You don't need to waste time here. Just do the 20% that gives you 80% of the knowledge you just need right now for the new project.

  6. Set a timer, and every 35 minutes, write down (or record yourself) what you learned (in order to see if you really work efficiency).

  7. The next day, take a small project you have previously done (or a small feature you did at work) and convert it to the new technology or language you are learning.
    Remember, it doesnโ€™t necessarily have to work if itโ€™s a feature relying on an app, but here, the exercise is to understand the new language/technology based on something you already know well. By doing that, you will understand the new stack much more efficiency.

  8. Start now a simple project from scratch with the new language. Something simple, but if possible replying with an API (so you also understand how to fetch remote data with the new language).

  9. When you donโ€™t understand something, check on the official documentation or on StackOverflow and write down the solution in order to learn more efficiency.
    Accomplishment. Succeed challenges

  10. Teach what you just learned. Doing this will structure and organize the flow of information you learned, allowing you to understand better the topic and see what you haven't learned yet and reinforced them.
    Do a 30-minute tech workshop at work (e.g. with Google Slides) or see to participate to a tech Meetup, screencast yourself coding a part of the new project while commenting on what you do (no pressure, you don't necessarily have to share it or publish it on Youtube), publish a Medium/Dev.to post, etc.
    Teach what you learn in order to remember more efficiency

And you? If your boss (or new job) ask you to build a new app or API with a new framework, language or skill you have never used before, what learning tricks would you use to be good and efficient at it in just a matter of days...? Share them here with Dev.to's community! ๐Ÿ˜Š๐ŸŽ‰


Editor guide