Code as an engineering tool — writing precise scripts that make hardware do exactly what you need it to do.
I write code the way a machinist runs a lathe — with a specific part to produce, not to admire the toolpath. The goal is always a reliable, readable script that does one job well, and can be handed off to someone else without a manual.
My most-used language in professional work. At HighRes, I write C# scripts within proprietary lab automation platforms to control liquid handling devices — triggering dispense operations, reading instrument states, handling errors, and building compound workflows that chain multiple devices together. The code needs to be reliable: failures in automation scripts can waste expensive reagents or corrupt an experiment that took days to set up.
I've also used C# for configuration utilities and data logging tools that support field service operations.
MATLAB was the computational environment at RPI — used across biomechanics, numerical methods, signal processing, and data analysis coursework. I'm comfortable with matrix operations, plotting, curve fitting, basic ODE solving, and writing clean functions that document their own inputs and outputs.
Basic Python for scripting, data manipulation with pandas, and occasional automation tasks. Not my primary language but enough to work with existing code, modify scripts, and solve one-off problems.
"My code tends to be specific, documented, and boring — which is exactly what you want when the hardware on the other end costs six figures."