A talking CV

Summary

• extensive experience in multiple industries
• deep knowledge of software engineering (multiple languages), databases, DevOps, cloud services, and more
• management

What I like

I like working on new projects, but I also like the challenge of working on large code bases. Working years in technology in the global equity trading, I'm used to working with, and managing, distributed teams. Thinking in terms of different timezones has become second nature.

What makes me tick

I have definitely been accused more than once of throwing myself deeply into my work.

How I work

sense of accomplishment takes a village give credit where credit is do

had home lab over a quarter century. a mixture of Linux workstations, Unix servers (including a DEC Alpha!), and Windows servers would test out Exchange, run databases, and more multi-processor box AMD64 - offered an ssh to a maintainer to help fix a compilation bug

How I pick technology

the adoption curve. https://en.wikipedia.org/wiki/Technology_adoption_life_cycle#:~:text=The%20technology%20adoption%20lifecycle%20is,characteristics%20of%20defined%20adopter%20groups. I'm usually early in the early adopter phase. It isn't until later in the early adopter, or early in the early majority that I start recommending things at work. (I don't want to recommend things that don't end up getting traction.)

How I got here

I never liked being type cast. (Although, ironically, I do like typed languages.) I think a lot of it was driven by my never-ending quest to learn everything I can about anything related to computers.

I have moved back and forth between pure software engineering roles and DevSecOps-type roles. Because of my background, I often find myself coaching others no matter my role or their role. As a result, I have worn many hats over the years, and I am often the person who figured out complicated problems or old bugs.

Experience overview

If you want more details, check out my LinkedIn