July 2, 2019
Every day at Mixmax, engineers must consider problems and solutions from many different angles: we assess risk in our deploy plans, balance readability and succinctness, and make sure to delight users with small touches.
Working within the constraints of professionalism and quality is important for a high-performing team, and it's equally important to find ways for our creativity and playfulness to shine. In May, we set ourselves a challenge: toss all the usual constraints out the window, optimize for creativity, cleverness, and enjoyment instead, and write some code that outputs the Mixmax logo!
This code wouldn't go into production, of course, and it wouldn't need to be maintained by other team members. It was purely a way to exercise the right side of the brain and have a little fun. We called it the Creative Code Challenge, and gave ourselves a month to see what we could do.
Participation wasn't mandatory, because creativity can't be forced. On the Mixmax engineering team, we each allocate a portion of our work time to pursue anything that interests us or helps us grow and learn, so taking part in the creative challenge was just one of (nearly) infinite options available for spending that time. At the end of the month, four of us had put together entries.
tl;dr check out the challenge and the entries on Github, or read on for a summary.
Trey Tacon, our head of platform engineering, is a big fan and advocate for Go, so of course he took the creative code challenge as a refreshing opportunity to exercise his Go skills in an unfamiliar area: image manipulation. He was motivated to create something a little more engaging than a static logo, so his entry applies a spinning Mixmax logo watermark to any image.
Eli Skeggs says, "The Mixmax logo has some neat geometries that I realized I could exploit by using spatial transforms to turn the entire logo into a single inequality. I realized it'd be even more fun to code-golf this solution, as it ends up being pretty amenable to a functional approach." He chose to work with the Pyth language because "Pyth is an old friend, and I generally enjoy class-1 programming exercises (those involving mathematics and the terse representation of logic/control)."
Does this look like fun? Feel free to put together your own entry (see the very loose guidelines here) and submit a PR.
Want to work with a team that understands the value of balancing rigor and fun? Come join us!