“Flexibility is the key to stability.”
-John Wooden
“Stay committed to your decisions, but stay flexible in your approach.”
- Tom Robbins
It was Wednesday night, Day 11. I was building another chatbot and template literals finally clicked. But I was also realizing something else: the planned Friday essay schedule isn't working. To me, Friday evenings are for relaxing, enjoying, winding down from the week.
Essays typically take me at least 2-3 hours from first draft to posting. They need deep work time. And the weekend is when I actually have that time. So I have altered my weekly schedule slightly to adapt. For this project to ultimately succeed, I require a system that works with my life, not against it.
The week in review:
Day 9 (Monday) - The Clean Start:
Week 2 started strong. Completed the Variables and Data Types quiz on freecodecamp: 100%. Felt good coming off the uncertainty and trepidation of Week 1.Monday was a reset, and a renewed commitment to myself to embrace the discomfort and just keep plugging away.
Day 10 (Tuesday) - The Overwhelm:
Five new string concepts in one hour: bracket notation, template literals, escaping characters, indexOf, prompt(). My brain: "Which one do I use when?"
This is the learning curve everyone talks about. Not the difficulty of any single concept (I definitely understand theory), but the sheer volume of new things being introduced at once. I finished the lessons, but felt overwhelmed. Went to bed wondering if I was actually learning or just clicking through. How much of this can I actually retain?
Day 11 (Wednesday) - The Click:
"Build a Teacher Chatbot." First instruction: use template literal syntax to create a greeting.
I stared at it. Tried writing: let greeting = " " (backticks inside quotes). Wrong. Got stuck. Asked for help. The fix: backticks ARE the quotes, not characters inside them.
let greeting = My name is ${botName}.;
It worked. Then I used template literals six more times in the same workshop. No hesitation. No confusion. It clicked.
I am definitely noticing a pattern: Theory → Confusion → Practice → Click. This is pretty close to a universal cycle for learning anything new.
Day 12 (Thursday) - Building Competence:
Four more string methods: charCodeAt, includes, slice, substring. That's nine string methods in three days. I'm definitely NOT memorizing them. I'm just learning they exist. When I need to check if a string contains text, I'll remember "there's a method for that" and then Google the syntax.
Critical Realization: The Friday Problem:
Thursday night I reviewed my weekly project plan. Friday = essay day. One hour, 6:15-7:15pm. Write 1,200 words. Then family time.
This doesn't work for me.
Essays take me much longer than an hour. Week 1's essay took three hours on Saturday morning and I was rushing. Decent writing needs deep work time, as in two uninterrupted hours minimum. Friday evenings just don’t allow for that, and even if they did, it just doesn’t work for me.
Friday evenings are for decompressing from the brutal grind of the week. The 4:30am wake ups, the heavy workouts, the unforgiving burnout of work, the toddler care, daily work on this project, all of it. I want cold beer, Irish whiskey, a good meal, laughter, and a care free respite from my wonderful, jam packed life.
But Saturdays? Yeah, that's perfect. Fresh mind. No rush. Actual time to think and write. Same with Sunday—some weeks I'll have 3-4 hours available, some weeks zero. Flexibility is the point.
Weekdays are tight.
Weekends have space.
That's when deep work can actually happen.
New System:
Monday-Thursday:
One hour coding (freeCodeCamp)
Sustainable, consistent, keeps momentum
Friday: Flex Day
Family time prioritized
No essay pressure
Saturday:
2 hours: Write weekly essay
1 hour: Code/build
1 hour: Publish (Beehiiv, Twitter thread, schedule)
Sunday: Flex Deep Work
0-4 hours depending on energy
Some weeks: coding surge, get ahead
Some weeks: complete rest
Both valid
Total Weekly Hours:
Minimum (low energy): ~8 hours
Typical (normal week): ~11 hours
Maximum (high energy): ~17 hours
Same output. Better distribution.
What Changed:
When I do deep work (weekends, not Fridays)
How I use Sunday (flex, not fixed rest)
Pressure on Fridays (removed)
What Didn't Change:
365 day project
Weekly essays (just not on Friday)
Daily tracking
Building in public
Launching Homer Day 309
The original plan looked perfect on paper:
Monday-Thursday: Code one hour. Friday: Write essay one hour. Saturday: Build four hours. Sunday: Rest.
Clean. Symmetrical. Disciplined.
But it didn't quite fit my actual life.
365 Documented isn't about following a perfect plan. It's about building a system that works with reality.
This isn't lowering standards. I'm still writing weekly essays. Still coding daily. Still building in public. The commitment hasn't changed. The execution has.
Week 1 reminded me I can do hard things.
Week 2 reminded me sustainability matters more than rigidity. Adapt or die.
14 days in the books now. Template literals tackled. 40+ freeCodeCamp lessons done. System adjusted to fit my life.
Tomorrow (Sunday): Maybe I'll code for three hours. Maybe I'll rest completely. Both options are just fine. Both move me toward Day 365.
This is how you finish what you start—not by forcing a system that doesn't fit, but by building one that does.
Week 3 starts Monday. Same commitment. Better execution.
351 days to go.