I’m starting a small public learning log to make my experiments easier to revisit and share. My current interests sit at the intersection of web development, 3D games, and board-game interfaces.
For web and 3D work, I want to focus on fundamentals: clear component structure, readable state changes, simple interactions, and the little performance lessons that only appear after something runs in a browser. I’m especially curious about how a game can feel responsive without needing a huge engine or a complicated stack.
Board-game UIs are a fun companion project. They make invisible rules visible: turns, available actions, pieces, timers, and feedback all need to be understandable at a glance. A good table layout is part information design and part storytelling.
This log will hold short notes about what I tried, what broke, and what I learned. I’m not aiming for polished tutorials every time. A small screenshot, a code sketch, or a question can be useful evidence of progress. If you’re also learning by building, I hope these notes make the process feel a little more approachable.
Top comments (0)