A month ago I decided to learn in public. The idea is simple: instead of studying quietly and showing people a finished project at the end, you post what you are learning every day, mistakes included, while you are still bad at it.
I picked Python automation, a topic I knew almost nothing about, and posted one short update every day for 30 days. A screenshot, two or three sentences about what I tried, and one thing that went wrong. That was the whole format.
People told me it would change everything. It changed three things. The rest was noise.
1. Strangers corrected me, fast
This was the single best part, and it was not close.
On day 6 I posted a script that used a loop to check if a file existed, and someone in the comments told me there was a built-in function for it. On day 11 I posted code that read a whole spreadsheet into memory, and two people explained why that breaks on big files. On day 19 I made a mistake with timezones that would have taken me hours to find alone, and a stranger spotted it in about four minutes.
I counted 14 corrections across the 30 days. Fourteen times someone who knew more than me stopped me from practising a mistake. The catch: post cropped screenshots of just the code, not your whole screen. People help when helping is easy.
2. The streak kept me going on bad days
I am not a disciplined person. I know this about myself. Left alone, I study for four days, skip a week, and then feel guilty enough to start over. That cycle had repeated about five times before this experiment.
By day 30 I had written code on 30 consecutive days. That had never happened before. The streak did not make me talented. It made me consistent, which turned out to be the thing I was actually missing.
3. The posts became a portfolio without me trying
I did not plan this part. I was not trying to build a portfolio. But after 30 days I had 30 dated posts showing a complete beginner learning automation from zero, with real code, real errors, and visible progress. When I applied for a part-time support role in week four, I linked to the thread instead of writing a cover letter about my passion for learning.
The hiring manager mentioned it on the call. He said it was the first time an applicant had shown him their learning instead of just claiming it. I did not get that job, but I got to the interview stage, and for someone with no experience, that was the hard part.
What flopped
Not everything worked. Three things flopped clearly enough that I want to name them.
First, the likes. My posts averaged about 8 likes and zero comments on most days. The corrections I described above came from maybe six people total, on six of the thirty days. If you measure learning in public by engagement, it looks like a failure. The value was concentrated in a handful of comments, not spread across the month.
Second, the time cost. Writing the daily post, taking a clean screenshot, and answering comments took about 20 minutes a day on top of the actual studying. Over 30 days, that is 10 hours spent on posting instead of learning.
Third, the performance feeling. Around day 12 I caught myself choosing easy topics because they made better posts. A clean little script photographs well. A confusing afternoon reading documentation does not. If you are not careful, learning in public quietly turns into performing learning, and those are not the same thing.
The exact routine, so you can copy it
Here is what I actually did, stripped down to the parts that mattered.
Every evening, after studying, I wrote three lines in a notes file: what I tried, what worked, what went wrong. Then I took one cropped screenshot of the code, not my whole screen. Then I posted the three lines plus the screenshot, in that order, and I went to bed. Total time: 15 to 20 minutes.
Once a week, on Sundays, I read back through the week's posts and wrote one line about the pattern. Week two's pattern was that I kept making the same file-path mistake. Those weekly lines were the most useful thing I wrote all month, and they took five minutes each.
The honest downside
Thirty days is not long enough to learn a skill. I can now write basic automation scripts, and I understand files, loops, and a handful of libraries. I am not job-ready. Anyone who tells you a month of posting makes you hireable is selling something.
Would I do it again
Yes, but differently. I would post three times a week instead of daily, because daily posting cost 10 hours and most days added nothing. I would keep the Sunday review, because that was the best part.
Three things worked: fast corrections from strangers, a streak that kept me consistent, and a portfolio that built itself. Everything else was decoration. If you try it, optimise for those three, and let the likes take care of themselves.
Top comments (0)