Learn Something New Every Week

Learn Something New Every Week

My new side project(ish).

Colleges and universities are great environments to learn new skills and techniques in. Course instructors prepare learning goals, concepts and projects such that students get to learn a lot of information and develop strong skills in a short period of time. I’ve had many friends tell me that constant learning is quite difficult once you graduate and start working, which is why people stop. Can’t let that happen.

As I transition from graduating to working, I have put together a framework that allows me to sample and learn new skills and concepts quickly. The framework is titled ‘Learn Something New Every Week’ (I know, no points for creativity). That’s as self explanatory a title as any.

The concept is simple: I pick a topic or skill to learn (academic or nonacademic) every week, and learn as much as I can about it in a week (about an hour a day). I also have to build something with what I’ve learnt. For instance, if I pick a particular form of dancing as a skill, I need to end the week with some sort of finished version of a choreographed dance. Don’t hold your breath, dancing isn’t very high on my list. For now. ;)

Given that there is such a wide variety of skills and concepts to pick from, what do you pick? The answer is simple… you pick anything you want to try. The idea is not to enhance your portfolio or learn shiny new skills that look good on resumés (although that may end up being a nice side effect). The idea isn’t even about picking something that is ‘useful’ to you in your daily life. The idea is to pick something you’re excited about. Want to learn how to cook? Go ahead. Want to learn functional programming languages? Be my guest. Want to learn how to write well? Let’s do it. One of my favorite quotes from a TED talk captures this idea perfectly. It goes something like this:

We don’t learn or teach things because they might be useful tomorrow, we do it because they’re delightful today.

- Grant Sanderson (the creator of 3blue1brown)

The principles/rules of LSNEW are simple:

  1. You have to make something

  2. You only have a week

Why the strict week-long schedule?

Well, in my experience a week is short enough that trying something new does not need immense commitment, which makes starting easier. The short duration also allows you to ‘sample’ many things. Only by sampling many things will you find the things that you enjoy the most. Another advantage is that in case you don’t enjoy a particular skill much, you haven’t lost much time at all. At the same time, if done right, a week is also long enough to make progress and actually build something non-trivial in most cases.

Why do you have to make something?

Trying to learn a skill by making something is always better than trying to learn a skill with no goal. It’s always better to learn by synthesis rather than by analysis.

Don’t dissect the frog, build it. - Seymour Papert

The first week I tried this, I wanted to learn how to build a website. The ‘outcome’ or goal was to build a personal website within that week. Of course, I couldn’t implement everything I wanted to, but those things turn into follow-ups which I can work on in the future. The week is enough to get started and get upto speed. Any extra tasks turn into follow-ups, and follow-ups are much easier to tackle as compared to starting from scratch. In the case of my web-dev week, I was able to put together a bare-bones website within the week, and my follow ups looked something like this:

follow-ups

Speaking of the mechanisms of how I like to work through the week, let’s take a look at exactly how I like to do this. I break down the week into 3 parts: preparation, process, and termination.

1. Preparation (day 0):

The idea is to take a day 0 (Saturday?) and put together some thoughts that make learning much easier over the week. For me, this involves the following steps:

  1. Pick the topic: this is easy enough. I constantly find myself wanting to learn something or the other and I keep a running list. The list looks something like this right now: list

  2. Decide the outcomes: what will you build? Be specific. Here’s an example of outcomes from my web-dev week. outcomes

  3. Collect resources: learning something academic? Find blog posts or books. Learning how to cook? Pull up a list of recipes you will try. The idea is to make day 1 as easy as possible.

  4. Make a road map: a plan of how you will get to your outcome. This map is tentative and it’s okay to change things as the week goes on. For me, that looked a little like this: plan

2. Process (day 1 - day 7):

Jump in and begin! I have noticed a few things that make this process easier:

  • Leave things slightly unfinished everyday so you can pick up right where you left off

  • Keep a running log of notes and things you learn

  • Try to stick to the roadmap as much as possible!

3. Termination (day 7):

List your follow ups and summarize your learning.

A week is not enough for certain projects or skills. If you enjoyed anything you learnt in the week and you can see immediate follow ups, list them out! As for summaries, I like to make a 1-page write-up explaining exactly what I learnt in super easy to understand terms. The idea here is that you learn best by teaching. When you write a simplified summary, you’re forced to think about how you would describe everything you learnt to someone else, i.e, you’re teaching.

I also decide what I would have done differently to make learning easier. As you learn new things, you also get better at learning. Answering this question improves how you will learn things the next week, and so on.

And that’s it! That’s how I like to learn and sample new skills and concepts.


Again, the idea is to simply learn something you want to learn rather than what you think may be useful or will pay off professionally. Another quote to drive my point home…

People ask me, ‘What is the use of climbing Mount Everest?’ and my answer must at once be, ‘It is of no use.’ There is not the slightest prospect of any gain whatsoever. Oh, we may learn a little about the behavior of the human body at high altitudes, and possibly medical men may turn our observation to some account for the purposes of aviation. But otherwise nothing will come of it. We shall not bring back a single bit of gold or silver, not a gem, nor any coal or iron… If you cannot understand that there is something in man which responds to the challenge of this mountain and goes out to meet it, that the struggle is the struggle of life itself upward and forever upward, then you won’t see why we go. What we get from this adventure is just sheer joy. And joy is, after all, the end of life. We do not live to eat and make money. We eat and make money to be able to live. That is what life means and what life is for.

- George Mallory, a mountaineer who led early British expeditions to Mount Everest in the 1920s, on the joy of climbing

I have spent about 3 weeks trying this, and it’s been going okay so far. The process changes from week to week, and I know I’m definitely not doing things in the best way. Please let me know if you have any suggestions or questions!

I do hope that one day I can do this with many people, where people learn things and share exactly what they learnt and the outcomes of what they learnt. This creates accountability and adds a community aspect to the whole process, and I would love to do this with other people. Again, let me know if you want to try this!

Here’s hoping to many many more weeks of constant learning!