Check out ColorClock development journey 🌈 ⏱️
Leveling up ColorClock with testing, tooling, and better software design.
Ten years in the making and ColorClock was deployed at Burning Man 2024 🥳 It worked the whole week and I didn’t even need to break open the backup electronics box 😅
Our scheduled live demo pushed us to finish the project just in time. The event was a success and I even got to play teacher again 👩🏫
My lesson on why you should always use parenthesis in preprocessor directives.
This week I contemplated the optimal solution for the circuit board layout.
My slow burn realization that I won’t be able to use a multiplexer as an IO expander for RGB output.
My experiments with an IO expander, level shifter, and a lesson learned.
A mystery solved, a Linux partition, and we’re officially listed!
Every software hurdle feels like an epic journey. My latest challenge was learning how to set build flags.
We decided to extend the shade portion of the structure to give the participant more space.
Finding the balance between artistic vision and feasibility of execution for the user interface.
My multi-stage approach to development.
After a weekend of rapid fire brainstorming discussions, we have decided on an overall physical design of the project.
Windows Subsystem for Linux 2 cannot interface with my computer’s serial ports and it makes me very sad 😭
I’m learning the importance of incremental development.
Once upon a time I was intimidated by the command line. Today, I get annoyed when I can’t use Vim.
When starting out, avoid getting caught up in the details of implementation, and instead invest your energy in preparing to show up.