True Shuffle
A Kotlin/Android app that shuffles Spotify playlists in a truly random order.
Recent content in Hello! on The Boomerang IC
A Kotlin/Android app that shuffles Spotify playlists in a truly random order.
Readable code helps developers parse what is in front of them. Understandable systems go further: they provide trustworthy evidence about where behavior lives, how changes propagate, and when it is safe enough to stop searching.
A newsletter hub using Typescript/Node/Vue that helps you keep on top of your newsletters without digging through your inbox.
A CLI tool (React UI to come) that helps you build playlists that match your physical activity using Typescript/Node.
Maintainability isn’t only about finding code or reading code. It’s also about knowing when further search is no longer necessary.
The difficulty of understanding a system depends less on its size than on its cognitive surface area — how much of the system developers must explore to understand behavior.
AI makes it easier than ever to generate code — but it does nothing to reduce the cost of understanding it.
The Single Responsibility Principle works because it limits conceptual frame switching, protecting the reader’s working memory.
A codebase that forces exploration slows everyone down. Breadcrumb systems make the starting point obvious.
Software development is read-heavy. When code is hard to understand, the real performance bottleneck is comprehension, not execution.
Developers don’t read code like compilers. Perceptual principles like proximity, repetition, similarity, and hierarchy shape how we understand it.
Code formatting works best when it aligns with how humans process information: chunking ideas, scanning patterns, and recognizing structure.
Formatting debates often get dismissed as style preferences, but consistent structure helps the brain process code more efficiently.
Refactoring legacy systems becomes safer when structure makes behavior understandable before changes are made.
AI-generated tests often mirror implementation instead of validating it. Reviewing them properly is essential to avoid false confidence.
AI-generated tests often reproduce the structure of the code they test — creating the illusion of coverage without validating behavior.
Team traditions fail more often from cultural misfit than from lack of effort.
A dedicated appreciation day gave teammates a structured moment to recognize each other’s contributions and kindness.
A birthday spotlight survey revealed funny and meaningful details about teammates — but also taught me how cultural differences affect team rituals.
Remote teams don’t get spontaneous celebrations — simple traditions like shared birthday cards help build connection intentionally.
The Tazzie Awards turned work anniversaries into a team-wide event — combining humor, recognition, and participation.
Personalized Spotify playlists became one of our most loved work-anniversary traditions — but only because the team had the trust and familiarity to make it work.
A new version of my personal recipe costing and meal-planning webapp using Rails 8/PosgreSQL and a little bit of React.
A personal recipe costing and meal-planning webapp using Java/Spring/Ebean/MySQL/JSP.
Hi! I’m Christie. I spent three years in engineering management before “boomeranging” back to being an IC again. Along the way, I realized that I don’t just love building software — I love building teams and community, too. The most meaningful moments in my career weren’t the code I shipped; they were the team traditions, inside jokes, thoughtful rituals, and the…
Birthday spotlight survey questions for remote teams to celebrate coworkers in a fun, optional way.
Team tradition ideas with fit criteria, effort level, and purpose for remote or hybrid teams.