Balancing High School, Student Leadership, and Shipping Production Code

The most common question people ask me on LinkedIn is: *"How do you run software products for 100,000 users, serve as class president, write a book, and still pass AP classes?"*

The honest answer: I don't multitask. Multitasking is a trap that produces mediocre grades and buggy software. Instead, I treat my week like a partitioned hard drive.

The Three Strict Compartments

#### 1. The School Citadel (7:30 AM – 3:15 PM) When I walk through the school doors, my code editor stays closed. I don't look at deployment logs or respond to customer tickets between chemistry and history class. Being physically present matters. If I'm leading a student council meeting during lunch, my classmates deserve 100% of my attention.

#### 2. Deep Work Block (4:00 PM – 6:30 PM) The moment I get home, I close all messaging apps, put on instrumental music, and enter a 150-minute focused coding sprint. This is where high-leverage engineering happens: refactoring database schemas, shipping new features, and fixing production edge cases.

#### 3. Writing and Editorial (8:00 PM – 9:30 PM) After dinner and school assignments, I dedicate 90 minutes to writing. Whether it was drafting chapters for *Built Young* or writing field notes for this blog, keeping writing separate from coding prevents cognitive fatigue.

"Productivity isn't about grinding for eighteen exhausting hours. It's about protecting two uninterrupted hours of deep flow every single day."

Asynchronous Systems That Save My Sanity

When you cannot pick up phone calls during third period, your systems have to work asynchronously by default:

• Automated Sentry error alerts: If an exception spikes, automated webhooks tag issues with reproduction details so I can fix it in ten minutes after school.
• Public status pages and self-serve FAQs: 95% of support questions are answered by concise, interactive documentation before anyone sends an email.
• Strict email batching: I check inbound emails twice daily: at 3:30 PM and 7:45 PM. Urgent things are rarely as urgent as people pretend.

Key Takeaways

• Never code during class: Splitting your brain between a teacher's lecture and CSS layout bugs ruins both.
• Protect your evening deep-work window: Consistency beats marathon weekend sprints every single time.
• Sleep is non-negotiable: Burning the midnight oil is a debt with compounding interest. Eight hours of sleep keeps your code clean and your patience intact.