Curiosity without a backlog ticket

Most of what I build starts with a concrete problem. Something in production is too slow. Something in the office is wrong twice a week. That is how I learned to code.

Not every evening is like that.

Sometimes I open the editor without a concrete goal — no quote, no process, no backlog item. And then, sometimes, a technical itch: cellular automata in 3D, morphing grids, shaders I only half understood on the first pass. No customer. No ROI.

Without AI tools I probably would not have started. A blank Three.js file used to mean weeks of tutorials before anything rendered. Now I can ask for a scaffold, break it, ask again — and still follow the math when the frame rate drops.

I am not selling this as a business strategy. The powder-coating calculator on this site exists because quotes are real work. The Morph field exists because I wanted to see the math come alive.