Tiny Experiment #2: Work through Dead Simple Python every morning for all of April
As a result of my unofficial experiment to read every morning for the last month or so, I found myself programming less. One takeaway from the experiment is that what I do in the morning ends up being the thing that I do the most. As such, it makes sense that my high priority activities should take place at this time. Though I enjoyed the quiet start to the day, my priority this year is to focus on learning Python, not read more, so the experiment I want to create should attempt to foster deeper learning with Python.
A problem that I run into with trying "to foster deeper learning with Python" is that learning Python, and improving my skills in web development, can involve a wide variety of forms. There are books, videos and tutorials to read. There are projects to build, both small and large. I can write blog posts about concepts, in keeping with Tiny Experiment #1. I can do Leetcode problems. And a problem for me specifically is that I want to do all of these things, in order to develop a well rounded understanding of the language. Additionally, I'm supposed to have a portfolio if I want to get hired, so building projects to share is basically a requirement. And solving LeetCode problems is a standard part of the application process for developers.
So how do I maneuver this landscape with limited time and a structured approach?
If I were to boil down the problems as I identify them, they would be as follows.
Learning development skills requires a wide range of approaches.
I only have so much time in the day.
I want to implement some sort of programming practice into my mornings since this is my most reliable time to work, but I don't want to neglect areas that are essential to successful learning.
Jumping back and forth between tasks/projects impedes momentum.
So with these problems spelled out, what might be a good approach to address them?
My intuition is to test that these problems are in fact true. Problem 1 may or may not be true, but I'm drawing the conclusion that if it is true, I need to focus on a wide range of approaches on a weekly basis. I think this might be wrong, at least for myself.
So a reasonable test of this would be to just focus on one thing every day for a given period of time and analyze the results.
Ok, here's the hypothesis then.
Focusing on a single project every morning for 30 days will result in more satisfying learning outcomes than jumping back and forth between different areas at random times throughout the week. Importantly, a "project" is not limited to creative development work, but rather defined as any measurable task with clear progress indicators, such as reading a programming book, building a website, or completing 100 LeetCode problems.
To test this hypothesis, I will work through Dead Simple Python every morning for all of April. On May 1, 2025, I will analyze the results of the experiment.