The UI is aggressively yellow (sorry about that lol), but the logic for the randomized character strings is solid. I even had to fix a dumb mistake where I named my main file just ‘.html’ and GitHub wouldn’t host it. It’s simple, but it’s mine
Spent this session cleaning up the project structure for PasswordMaker-Lite. I realized I accidentally named my main file just ‘.html’, so I renamed it to ‘index.html’ so GitHub Pages can actually recognize it as the entry point for the site. I also spent some time tweaking the slider code so the length updates properly while dragging. It’s a small update, but I’m learning how GitHub and simple JS logic interact. Total work: 26 mins.🧟♂️🧟♂️🧟♂️
Log in to leave a comment
Started working on GenKey today. The HTML and slider UI are done, and the JS is already hooked up. Next step: polishing the generator logic and the copy feature. 🧟♂️
Log in to leave a comment
I built Buddy Pomodoro because I realized I was often ‘doing Pomodoro’ but actually just staring at my screen or getting lost in distractions. This isn’t just a timer; it’s a tool for accountability. After every focus block, it requires a quick check-in to log what was actually accomplished and what got in the way.
The biggest challenge was moving from a static UI to a fully persistent system using localStorage so that no data is lost if the tab closes. I’m particularly proud of the ‘I’m drifting’ button—a feature I built for my own distracted brain to provide a tactical reset when things get overwhelming. It’s built with vanilla JS and a modern dark theme, keeping things fast, private, and focused.
Pushed through the finish line! 🚀 Just finished the complete logic for Buddy Pomodoro. I implemented the full timer cycle with automated focus/break switching and a ‘Panic’ mode for quick resets. The biggest win was getting the LocalStorage persistence layer solid—now focus blocks, streaks, and check-in logs stay saved even if the browser closes. Also hooked up the AudioContext for a custom beep notification and built the history UI to track progress throughout the day. It’s officially alive and functional! 💻🍪🔑
Log in to leave a comment
Focusing on that ‘Caffeinated’ sidequest. Got the core logic moving today for Buddy Pomodoro. Tbh, setting up the state variables and the vanilla JS selectors felt a bit caveman-style, but it works! 😂 I successfully implemented the basic LocalStorage persistence for saving settings like the goal and focus/break times, which feels like a huge foundation.
Log in to leave a comment
Woke up still tired, but Buddy Pomodoro is ALIVE! Alive I tell you! 🧟♂️ Tbh, the fatigue is definitely still real today. Operation Sueño was only moderately successful. But, I woke up thinking about how I actually got the JS logic working for Buddy Pomodoro. Start, pause, reset, modes, all persistent in LocalStorage! Knowing that core logic is done and saved is a huge relief. It was a brutal push but so worth it.
Log in to leave a comment
Finally got the base structure down for Buddy Pomodoro. Set up the repo and got the HTML and CSS deployed. Tbh I’m super tired and the fatigue is real today, so I need to crash. Tomorrow I’m tackling the JavaScript timer logic. 😴
Log in to leave a comment
What did you make?
I built a Chladni Resonance Visualizer that simulates acoustic standing waves on a metal plate. It uses 12,000 sand particles that organize in real-time to form geometric patterns based on adjustable harmonics.
What was challenging?
Optimization and debugging. I fought a “Syntax War” against silent crashes—like mistyping Math as Match—and had to implement Float32Array to keep the physics engine running at a stable 60 FPS.
What are you proud of?
Creating a physics engine from scratch without external libraries. I’m particularly proud of the custom motion blur effect and the hidden performance HUD used to monitor the system.
**Update: Surviving the Syntax Trenches 🛠️
**
Today’s session was a brutal reminder that the JavaScript engine has zero mercy. I spent hours fighting a blank canvas, trying to figure out why my physics loop was silently crashing.
The culprit? Invisible syntax errors. A rogue space in an array variable (pos Y instead of posY) and a hallucinated typo calling Match.abs() instead of Math.abs(). Those tiny mistakes completely derailed the trigonometric equations for the Chladni standing waves.
I stripped out all the distractions and went back to the raw, pure source code. Debugged it line by line until the math finally clicked. Now, the engine is successfully calculating 12,000 particles through the Float32Array and rendering the geometric nodes correctly.
No extra fluff, just raw code and pure physics finally working as intended. On to the next step.
Log in to leave a comment
Day 2 Progress: UI Layout & Math Engine Initialization
Current Status: Reached fatigue limit for the day. There is a minor DOM rendering bug preventing the Canvas from drawing the particles properly, but the math logic is solid. Will debug the canvas render loop tomorrow and finalize the project for shipping. 
Log in to leave a comment
Starting the Chladni Visualizer
This is the beginning of my Chladni Resonance visualizer! I’ve set up the basic interface design, including the title and initial controls. The next step is to implement the main physics engine to calculate and display the standing wave patterns.
Log in to leave a comment
I built Terminal Zero, a C2-style terminal simulator. After a total crash at 2 AM and a 6-hour marathon, I had to rebuild the entire system and hot-patch the kernel via the console to get it back online. I’m proud of the 64-block RAM engine and learning that in development, persistence is everything. Session validated and locked in.
After a 5h 50m deep-dive session, the Terminal_Zero core logic is now fully operational. This milestone focused on building a functional command parser and a simulated memory management system from scratch.
Log in to leave a comment
Initial setup complete. Fixed HTML structure errors and implemented the base high-contrast terminal theme with CSS. System is now responsive and rendering correctly
Log in to leave a comment
