The modern parent’s nightmare isn’t monsters under the bed; it’s the soft, blue glow emanating from under the bedroom door at 2:00 AM. As I’ve explored before in Your Child is Still Awake, raising children in an era of ubiquitous AI is a constant battle for balance. I previously built a web app to remotely control Firefox, creating a digital "safe zone." But recently, a dark reality set in: blocking content isn't enough if the machine can be turned on in the night. Your Child is Still Awake blocking content isn't enough if the machine can be turned on in the night. I discovered my son’s computer was breathing to life late into the evening. While the "dangerous" sides of the web were locked away, the lure of "harmless" entertainment—quizzes and educational games—was still enough to steal his sleep. I didn't want to go full "Luddite," but I needed his freedom to have a definitive bedtime. The Goal: Precision Power Management I needed to evolve my app into a Remote Power Management system. The requirements were non-negotiable: Remote Power Management system Granular Control: Define precise "uptime" windows for every day of the week, down to the minute.
Active Alerting: If the PC is switched on during restricted hours, I need an immediate email alert (User, Hostname, and Timestamp) and ensure it turns off right away.
Flexibility: Support multiple ranges per day (e.g., off during school, on for homework, off for dinner).
Override Capability: A "maintenance hook" to pause shutdowns when I'm actually working on the machine. Granular Control: Define precise "uptime" windows for every day of the week, down to the minute. Granular Control: Active Alerting: If the PC is switched on during restricted hours, I need an immediate email alert (User, Hostname, and Timestamp) and ensure it turns off right away. Active Alerting: Flexibility: Support multiple ranges per day (e.g., off during school, on for homework, off for dinner). Flexibility: Override Capability: A "maintenance hook" to pause shutdowns when I'm actually working on the machine. Override Capability: The Tech Stack Overhaul Implementing this required a deep refactor of three layers: Backend: Logic to handle "0 to many" time ranges per day.
Linux Client: System-level hooks to manage shutdowns and prevent "uptime hijacking."
Frontend: A UI overhaul to make managing complex schedules intuitive. Backend: Logic to handle "0 to many" time ranges per day. Backend: Linux Client: System-level hooks to manage shutdowns and prevent "uptime hijacking." Linux Client: Frontend: A UI overhaul to make managing complex schedules intuitive. Frontend: I decided to pit two titans—Claude and Gemini—against each other using their free tiers to see which handled this refactor better. Claude Gemini Round 1: Claude – The Overzealous Architect Claude is a developer favorite for a reason. When I fed it my requirements, it responded with a massive "drop" of code: Shell scripts, Systemd services, timer files, test scripts, and installation scripts. The Issues: The Issues: The Logic Hallucination: The requirements included a "shutdown hook" to pause the power-off. Claude misinterpreted this, refactoring it into a feature that shifted the start time of the uptime window instead.
Over-Engineering: It designed an overly complex Systemd timer architecture threating the mid to long-term maintenance.
The Velocity Trap: On the free tier, Claude’s verbosity and velocity were a bottleneck. It insisted on regenerating every single file for minor changes, hitting rate limits, and requiring several minutes for each iteration. The Logic Hallucination: The requirements included a "shutdown hook" to pause the power-off. Claude misinterpreted this, refactoring it into a feature that shifted the start time of the uptime window instead. The Logic Hallucination: start Over-Engineering: It designed an overly complex Systemd timer architecture threating the mid to long-term maintenance. Over-Engineering: The Velocity Trap: On the free tier, Claude’s verbosity and velocity were a bottleneck. It insisted on regenerating every single file for minor changes, hitting rate limits, and requiring several minutes for each iteration. The Velocity Trap: every single file Round 2: Gemini – The Agile Iterative Partner I switched to Gemini. The experience was the polar opposite. The Wins: The Wins: Precision: Gemini didn't bury me in files I didn't ask for. It focused exactly on the snippet I needed.
Speed: The generation was lightning-fast, which is crucial when you are in the "flow state" of refactoring.
Frontend Mastery: The biggest hurdle was the CSS/HTML/JS refactoring for the new scheduling UI. Gemini helped me iterate on the look and feel, ensuring the "0 to many" time ranges worked perfectly, including an appealing look and feel for the front end. Precision: Gemini didn't bury me in files I didn't ask for. It focused exactly on the snippet I needed. Precision: Speed: The generation was lightning-fast, which is crucial when you are in the "flow state" of refactoring. Speed: Frontend Mastery: The biggest hurdle was the CSS/HTML/JS refactoring for the new scheduling UI. Gemini helped me iterate on the look and feel, ensuring the "0 to many" time ranges worked perfectly, including an appealing look and feel for the front end. Frontend Mastery: Pro-Tip on Prompting: Pro-Tip on Prompting: Pro-Tip on Prompting: Success here required "smart" prompting. I initially started with overly complex, multi-layered prompts that led to hallucinations.
The breakthrough came when I reverted those changes and pivoted to a step-by-step refactoring strategy: Analyzing the code structure first and then requesting surgical updates was the key to success. Success here required "smart" prompting. I initially started with overly complex, multi-layered prompts that led to hallucinations. The breakthrough came when I reverted those changes and pivoted to a step-by-step refactoring strategy: Analyzing the code structure first and then requesting surgical updates was the key to success. step-by-step refactoring strategy Gemini acted less like a distant architect and more like a pair-programmer, helping me finalize the API, Linux cahnges and front-end in real-time. The Result: 6 Hours to Peace of Mind After six hours, the feature was live. Today, the system doesn't just block sites; it enforces the most important thing a growing child needs: rest. rest. Real-World Output: The Access Violation Alert If the system is accessed outside of the allowed window, I get an automated alert that looks like this: ⚠️ Access VIOLATION! - 2026-02-17 03:18
System Auto-Shutdown Alert

Current day: 2 (Tuesday) | Time: 03:18 

Configured Ranges: 07:30 - 21:30
✗ Outside all configured time ranges. Next window: 07:30

Hostname: Family-PC-01
The system will shutdown in 60 seconds. ⚠️ Access VIOLATION! - 2026-02-17 03:18
System Auto-Shutdown Alert

Current day: 2 (Tuesday) | Time: 03:18 

Configured Ranges: 07:30 - 21:30
✗ Outside all configured time ranges. Next window: 07:30

Hostname: Family-PC-01
The system will shutdown in 60 seconds. The Control Center: Dashboard and Visibility The frontend overhaul focused on "glanceability"—the ability to see exactly what restrictions are active without digging through menus. Key Dashboard Features: Key Dashboard Features: Real-Time Uptime Metrics: A quick-glance counter showing the total hours the computer is permitted to be powered on for all days of the week.
Dynamic Range Breakdown: A detailed view of today’s specific time windows (e.g., 07:30–08:30, 16:00–21:00), allowing for easy verification of "freedom windows."
Firefox Access Sync: A dedicated status indicator for the browser's "Safe Zone." Outside of these specific hours, any restricted websites will only be allowed in the next time range. Real-Time Uptime Metrics: A quick-glance counter showing the total hours the computer is permitted to be powered on for all days of the week. Real-Time Uptime Metrics: Dynamic Range Breakdown: A detailed view of today’s specific time windows (e.g., 07:30–08:30, 16:00–21:00), allowing for easy verification of "freedom windows." Dynamic Range Breakdown: Firefox Access Sync: A dedicated status indicator for the browser's "Safe Zone." Outside of these specific hours, any restricted websites will only be allowed in the next time range. Firefox Access Sync: Granular Scheduling: Power and Browser Control Granular Scheduling: Power and Browser Control The core of the refactor was the scheduling engine. The interface now allows for high-precision management of the computer’s lifecycle and the browser’s "Safe Zone." 1. System Power Configuration The scheduler supports 0 to N time ranges for every day of the week. 0 to N time ranges Precision: Configure access windows with 1-minute accuracy.
Total Lockdown: Setting zero ranges for a specific day completely prevents the computer from being used, providing a "digital detox" by default.
Dynamic Flexibility: Easily split time between morning sessions and evening homework hours. Precision: Configure access windows with 1-minute accuracy. Precision: Total Lockdown: Setting zero ranges for a specific day completely prevents the computer from being used, providing a "digital detox" by default. Total Lockdown: Dynamic Flexibility: Easily split time between morning sessions and evening homework hours. Dynamic Flexibility: 2. Firefox "Safe Zone" Synchronization Located at the bottom of the configuration screen is the Firefox access logic. This defines exactly when a child can visit "restricted but temporarily allowed" sites. Comparison: AI Coding Assistants (Free Tiers) Feature

Claude

Gemini



Accuracy

Prone to "over-thinking" logic hooks.

Strong at following iterative logic.



Speed/UX

Slow; regenerates entire blocks.

Extremely fast; great for "fixes."



Best For

Scaffolding a project from scratch.

Rapid refactoring and UI/UX iteration. Feature

Claude

Gemini



Accuracy

Prone to "over-thinking" logic hooks.

Strong at following iterative logic.



Speed/UX

Slow; regenerates entire blocks.

Extremely fast; great for "fixes."



Best For

Scaffolding a project from scratch.

Rapid refactoring and UI/UX iteration. Feature

Claude

Gemini Feature Feature Claude Claude Gemini Gemini Accuracy

Prone to "over-thinking" logic hooks.

Strong at following iterative logic. Accuracy Accuracy Accuracy Prone to "over-thinking" logic hooks. Prone to "over-thinking" logic hooks. Strong at following iterative logic. Strong at following iterative logic. Speed/UX

Slow; regenerates entire blocks.

Extremely fast; great for "fixes." Speed/UX Speed/UX Speed/UX Slow; regenerates entire blocks. Slow; regenerates entire blocks. Extremely fast; great for "fixes." Extremely fast; great for "fixes." Best For

Scaffolding a project from scratch.

Rapid refactoring and UI/UX iteration. Best For Best For Best For Scaffolding a project from scratch. Scaffolding a project from scratch. Rapid refactoring and UI/UX iteration. Rapid refactoring and UI/UX iteration.

This story contains AI-generated text. The author has used AI either for research, to generate outlines, or write the text itself. 

The 2 AM Blue Glow: How I Built a Linux 'Digital Curfew' to Reclaim My Son’s Sleep

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Firefox Managed Session Controller Earns a 36 Proof of Usefulness Score by Building an Open-Source Digital Wellness Tool

Why the “Junior Ghost Town” Could Be Tech’s Biggest Long-Term Risk

DeepMind’s Gato Shows How One AI Can Learn Everything at Once

Firefox Managed Session Controller Earns a 36 Proof of Usefulness Score by Building an Open-Source Digital Wellness Tool

Stop the Slop. Start Coding Smarter with AI

Lessons on Developer–AI Collaboration From 580 GitHub Conversations

Firefox Managed Session Controller Earns a 36 Proof of Usefulness Score by Building an Open-Source Digital Wellness Tool

Why the “Junior Ghost Town” Could Be Tech’s Biggest Long-Term Risk

DeepMind’s Gato Shows How One AI Can Learn Everything at Once

Firefox Managed Session Controller Earns a 36 Proof of Usefulness Score by Building an Open-Source Digital Wellness Tool

Stop the Slop. Start Coding Smarter with AI

Lessons on Developer–AI Collaboration From 580 GitHub Conversations

Light-Mode

Classic

Newspaper

Minty

Dark-Mode

Neon Noir

Minty

HN StartUps