Leet School

{module 1}

Learning in public

Orientation15 min read

What you will be able to do

  • Write a learning log from the five prompts, and edit it into one short post.
  • Share a log on X or LinkedIn and hand in the link.
  • Plan a weekly article, and say what must never be posted.

Why it matters

Sina is learning to build web pages in Apia, Samoa, in the evenings after work. For the first month she kept her notes in a private file. When she tried to explain a lesson to her brother, she found that she could repeat the words and could not say what they meant.

In the second month she changed one thing. After each lesson she wrote five short answers and posted them where other people could read them. Now she had to write sentences that a stranger could follow. Twice in the first week, writing the post showed her that she had not understood the lesson, and she went back and read it again.

That is the reason for the learning log. Explaining is the strongest test of understanding that exists, and writing for a reader is explaining. The log also leaves a record. In six months you will be able to see, day by day, how you learned.

The idea

The daily learning log

After every lesson you write a short log. The platform asks five questions, and you answer each in a sentence or two.

  1. What did I learn today?
  2. What was hard?
  3. How did I get past it?
  4. What did this lesson change about what I believed or thought was possible?
  5. What am I looking forward to next?

Each lesson adds one more question of its own. The form then puts your answers together into one post, which you can edit before you save.

Saving the log is the last step of every lesson. A few seconds after you save, you get a short reply. It says what worked in your writing and gives you two specific things to improve in your next post. Read it. Writing is a skill you are also here to learn.

Sharing it

Every saved log has two buttons.

  • Share on X opens X with a short version of your post already filled in. X limits the length of a post, so the button shortens yours to fit.
  • Share on LinkedIn copies your full post and opens the place where you write a LinkedIn post. LinkedIn does not allow a link to fill in the text for you, so you paste it yourself.

Each log also has its own public page on leetschool.com, which looks right when the link is shared. If you would prefer your logs to stay private, you can switch the public pages off in your settings.

After you post, come back and paste the link to your post. The platform checks that the link is on the right site. Posting in public earns extra points, because it is harder and it teaches more.

Your public profile collects your logs, your articles and your projects in one place. You can switch that off too.

The weekly article

At the end of each module you write one longer article about the week. A good article takes one idea from the week and explains it to a person who was not there, with an example. Each module suggests a subject.

You publish the article twice: as a LinkedIn post and as a post on your blog. Then you hand in the text and both links. You get feedback on three things: how clear it is, how it is organised, and how well you explained your own thinking.

What never to post

  • Secrets. Passwords, recovery codes, and any key or code a website tells you to keep private. A secret in a public post is a secret that belongs to everyone.
  • Other people's private details. A client's phone number, a customer's order, a screenshot with someone's email address in it.
  • Work that is not yours, as if it were. If you used someone's code or words, say whose.
  • Answers to the questions and weekly checks. Explain the idea in your own way. Do not hand the next learner the answers.

Worked example

Here are Sina's answers after the lesson on the six-step method.

  1. What did I learn today? "A method with six steps: Understand, Break down, Plan, Build, Test, Reflect. I used it to price a bakery order by hand."
  2. What was hard? "The test step. I wanted to stop when my answer looked right."
  3. How did I get past it? "I tried the order that sits exactly on the limit, $50.00. It showed me that 'or more' includes $50.00."
  4. What did this lesson change? "I thought good programmers typed fast. Now I think they wait longer before they type."
  5. What am I looking forward to next? "Using the method on real code."

The form puts them together, and she edits the result into this:

Day 2 of the Leet School Free Track. Today I learned a six-step method for solving problems: Understand, Break down, Plan, Build, Test, Reflect.

The hard part was testing. My answer looked right and I wanted to stop. Then I tried an order of exactly $50.00, the limit in the rule, and saw that "or more" includes it. One odd case taught me more than three easy ones.

I used to think good programmers type fast. Now I think they wait longer before they type. Next: the same method on real code.

The short version for X:

Day 2: a six-step method for solving problems. The lesson that stayed with me: test the case that sits exactly on the limit. One odd case taught me more than three easy ones.

Three things make this a good log. It names one specific thing that was hard. It says what she did about it, with the real number. And it says how her thinking changed, which is the part a reader remembers.

Common mistakes

Writing a diary. "Today I did lesson 2 and then the quiz" tells the reader what you did, not what you learned. Start from an idea, not from your timetable.

Posting only the good days. A log that says "I did not understand this and here is where I got stuck" is more useful to you and more interesting to others than a perfect day.

Waiting until it is good enough. A log is three short paragraphs. Write it in ten minutes and post it. It will be better next week because you posted this week.

Letting an AI tool write it. The log is there to test your understanding. A post that you did not write tests nothing, and readers can usually tell.

Think it through

Tariq has finished the orientation module and must write his first weekly article. He has no idea what to write. How does he start?

Understand. The task is one idea from the week, explained to a person who was not there. It is not a summary of everything.

Break down. He needs a subject, a reader, an example and an ending.

Plan. Choose the idea that surprised him most. Choose one reader, a friend who has never programmed. Find one example from his own week. End with what he will do differently.

Build. Subject: the debugging loop. Reader: his friend Samir. Example: the page with the button that did nothing, and how the message in the Console found the cots mistake. Ending: "Next time something breaks, I will read before I touch anything."

Test. He reads the outline as Samir would. Does Samir know what the Console is? No. He adds two sentences at the start.

Reflect. Choosing one reader made every other choice easier. He will name the reader first next time.

At work

Writing a short update that someone will read is a skill clients pay for, even when they do not know it. A learning log is practice for the messages you will send every week of your working life.

An update that gets read has four qualities. The point comes first. It covers one idea. It has a concrete detail. And it is short enough to read while standing up.

Compare these two, written to a client:

Hi, I have been working on quite a few things this week and wanted to give you a quick update on where everything is and some thoughts I have had.

The order form now works on phones. I tested it on three screen sizes. One question for you: should the total include delivery?

The second message is your learning log in another form. It says what was done, gives the evidence, and names what comes next.

Your tasks

Task 1: Write your first log

Finish this lesson's three questions, then write your learning log for it. Answer all five prompts and the extra one. Edit the post until a friend who has never programmed could follow it.

You are done when your log is saved and you have read the reply to it.

Share the log on X or on LinkedIn, using the buttons. Then paste the link to your post back into the platform.

You are done when the platform shows your link as accepted. If you have chosen to keep your logs private, you are done when you have explained the lesson aloud to one person.

Task 3: Outline your first article

Choose one idea from this module. Write a title, the name of one reader, the example you will use, and three points in the order you will make them.

You are done when you have a title, a reader, an example and three points, and you could start writing without another decision.

Recap

  • The learning log has five prompts and one from the lesson. Saving it completes the lesson.
  • Explaining to a reader is the strongest test of whether you understood.
  • Sharing on X fills in a short version. Sharing on LinkedIn copies the text for you to paste.
  • The weekly article explains one idea to one reader, with an example, on LinkedIn and on your blog.
  • Never post secrets, other people's private details, work that is not yours, or answers.

Go deeper