Every project has weeks where the graph is flat. This was one of those weeks.
This is the first entry in a weekly devlog for my current main project — a browser-based 3D car simulation built with Three.js and Cannon-es: vehicle physics, a test track, and cinematic camera modes. The goal I’ve committed to is generating tracks for five scenarios, each featuring ten different cars.
The honest update
No real progress this week. The blocker wasn’t technical — it was attention. I kept drifting toward other projects that felt easier or more exciting to start, and the car simulation stayed exactly where it was: untouched.
Feeling: stuck — and distracted. No screenshots to show this time.
Why I’m logging a “nothing” week anyway
Before starting this project I wrote a focus contract: a one-page commitment that says I don’t switch projects until the finish criteria are met — unless I go through a deliberate, non-impulsive abandon process. Part of the agreement is that I show up every week and write down what happened, even when the update is just “nothing much.”
There’s a reason for that rule. Progress that’s visible is fuel against distraction. A blank week feels like it disappears; a written week — even a stuck one — keeps the loop honest, and makes it easier to pick things back up next week.
The smallest next step
The contract’s principle: the smallest real step counts. So next week’s goal isn’t finishing the demo — it’s one scenario, one track, a handful of cars rendering end-to-end. If even that feels heavy, it’s just opening the project and pressing play.
Stuck weeks are part of the process. Logging this one still counts. See you next week.