Curiosity first
I like understanding how things work before deciding how they should work. That habit leads from a terminal window to a visual detail surprisingly often.
Build, break, learn
Most useful ideas arrive after something fails. I document the failure, reduce the mystery, and turn the lesson into something repeatable.
Make it clear
Whether it is code, infrastructure or a page on the web, the goal stays similar: remove what does not matter and make the important part easy to see.
What comes next
More experiments. Better documentation. More photographs. The archive is deliberately unfinished.