I’m a software engineer with over 10 years experience building for startups. I specialize in backend development and distributed systems. I have a talent for architecting and building robust, reliable software and systems.
The following is a professional README in case you and I ever work together. These are guidelines, not hard and fast rules.
- You can always change my mind.
- Complexity is a hill I will die on.
- TDD is the best way to design software.
- The best code is no code.
- Let CICD do it.
- Premature abstraction is as bad as premature optimization. A little duplication is ok.
- Be transparent and candid. But don’t be a jerk.
- Meetings are not for builders.
- Challenge decisions and perceived group consensus.
- Conflict is painful, but it’s the only way to grow.
- Building software is more art than science.
I live in Colorado with my lovely wife and kids. My work (building software) is my hobby. I heard that may not be healthy. So I also enjoy playing golf and occasional binge gaming on my Nintendo Switch.
“Legacy code is simply code without tests.” ― Michael C. Feathers, Working Effectively with Legacy Code
“Everything in moderation, including moderation.” ― Oscar Wilde
“Do not seek to follow in the footsteps of the wise; seek what they sought. Seek the meaning behind their footsteps, and not upon the steps themselves.” ― Bashō
“Hello there” ― General Kenobi