{"id":11795,"date":"2026-11-09T22:30:00","date_gmt":"2026-11-09T22:30:00","guid":{"rendered":"https:\/\/www.cotocus.com\/blog\/?p=11795"},"modified":"2026-11-09T22:30:00","modified_gmt":"2026-11-09T22:30:00","slug":"faq-what-i-learned-this-week","status":"publish","type":"post","link":"https:\/\/www.cotocus.com\/blog\/faq-what-i-learned-this-week\/","title":{"rendered":"Questions Answered: Writing Up What You Learned This Week"},"content":{"rendered":"

Our training sessions keep producing the same question from people who have just finished a tricky topic: should I write about it now, or wait until I really know it? Our answer is nearly always “now”. A short “what I learned this week” write-up, composed before the puzzlement has faded, ranks among the most efficient study tools we know. Below are the questions we hear most, answered the way we would answer them over a cup of tea.<\/p>\n

What exactly is a “what I learned this week” write-up?<\/h2>\n

It is a short, plain-language note explaining one thing you worked out recently, aimed at someone who has not worked it out yet. It is not a tutorial from an authority and not a diary of your whole week. One lesson, one reader, one page. Think of it as the note you wish someone had slipped under your door at the start of the confusion.<\/p>\n

Why bother if I can just read the documentation again?<\/h2>\n

Re-reading documentation confirms that the words are familiar. Explaining a concept confirms that you can rebuild it. Try describing a pipeline stage or a deployment step to a beginner in plain words, and the difference shows within a minute: the places where you hesitate are the places you only half understood. The write-up works like a spot-check for your own mental model.<\/p>\n

Do I need to be experienced to do this?<\/h2>\n

No, and being slightly ahead of your reader is actually an advantage. People who learned something yesterday still remember the misleading error message, the term nobody defined and the step the guide skipped. Veterans have lost those memories. If you are working through a roadmap such as our stage-by-stage plan for machine learning delivery<\/a>, each stage you finish is a fresh topic that someone else is about to start.<\/p>\n

How long should the note be?<\/h2>\n

Long enough to cover one idea and short enough to finish in a sitting. Roughly five to eight short paragraphs works for most technical topics. If you cannot stop writing, you probably have two posts. Split them and publish the second next week. A tight note also respects the reader, who is often reading on a phone between other jobs and wants one clean answer rather than a survey of the field.<\/p>\n

What should I include?<\/h2>\n