Learning in public: notes, experiments and the 30 Days Back to Basics series.
Two locations, seven masseuses, ~100 sessions a week. replacing paper day sheets with a system the whole business runs on. Includes a live demo.
A palindrome checker looked correct. It wasn't. It just happened to pass because a string is always a substring of itself and that's a scarier bug than one that just crashes.
A late-night session on one 'simple' exercise — reverse a string by hand — turned into five separate bugs, one after another. Here's the full bug-by-bug breakdown, and the return-vs-print lesson that showed up two days in a row from opposite directions.
A lighter day, ~2-3 hours. Three functions, one bug I made three separate times, and the moment it finally stopped happening.
First day of 30 Days Back to Basics. Variables, memory, loops, error handling and a guessing game I built entirely by hand. Here's what actually happened.
I've designed and shipped real products. But I noticed the hands-on fluency underneath didn't match the ambition. So for the next 30 days, I'm going back to raw fundamentals — by hand, no shortcuts — to rebuild the foundation under the house I've already built.
