Working with state
My background as a developer helps me anticipate and design for state from the outset. Even when I don't catch things immediately, the developers I work with know that they can talk shop to me and that I'll make sure every state we need is accounted for (within reason of course 😇 ).
The following is a stateful breakdown for a 'percent-change' React component that we wanted to standardize across all places where we communicated this type of metric. While calling out increase and decrease was obvious, accounting for edge cases of division by zero were less obvious but equally important for ensuring the clarity of the analytics.
Visualizing technical architecture
My team felt a lot of confusion as we set out to create a new architecture that would enable Signal Sciences to more successfully stop high volume, automated web attacks. We lacked a shared understanding of the existing system we were tasked with extending, so I dove into the code myself to tease out what I could of the core architecture. Having a visual aid helped the team rally together to clarify our understanding (refining the visualization as we went) and ultimately helped us make decisions about how the new tech should be built.