Post by Nnenna Ewa

When your code is breaking and your brain is on fire — how do you actually stop to take a screenshot? 🛑 I've been thinking a lot about Learning in Public, but I'll be honest: I'm stuck in a tug-of-war with it. One look at my coach, Solomon Francis Jeremiah's documentation and I felt properly humbled 😂. Here's the loop I keep falling into — when I'm deep in a project, errors flying, 15 tabs open and my notepad a mess of half-thoughts, my brain splits in two: 💨The Engineer: "Keep digging. Stop now and you'll lose the thread." The Content Creator: "This error is gold. Capture it!" I almost always default to survival mode — fix the problem, save nothing. By the time I reach a solution, the magic is gone. The messy middle — where the real learning happened — is buried in the rubble. And that middle is exactly what you need to replicate for mastery. I'm realising that documenting efficiently isn't just admin — it's a core technical skill that needs its own system. So I'm asking: my tech bros and sis's, how do you do it? 🎥 Screen record and clip later? 📝 Messy scratchpad, cleaned up weekly? 🧠 Sheer discipline? Drop your secrets below. 👇 My wonderful ABC OF CLOUD COMPUTING (CLOUD COMPUTING EMPOWERMENT) community — thank you for reminding me that showing up with an unfinished blueprint still counts. Shout out to the AWE-MAZING Team members Ernest Quaye Dadson Sandra Eboka Aishat Oshileye Marie-Grace E. Bolutife Oyedeji Kieshaun Lightbourne and the Bosses Boss Situk Ime Udoakpan It's a huge privilege, figuring it all out with you all. 🧩 #LearningInPublic #BuildInPublic #TechJourney #CloudEngineering #WomenInTech #Documentation #ProfessionalGrowth