What I do
The work usually sits at the overlap of infrastructure, application engineering, and practical architecture. I like systems that are clear to extend, reasonable to support, and grounded in how the product actually gets used.
These are the main buckets the work tends to fall into, along with the tools that often support each one.
DevOps
A lot of my recent work has centered on infrastructure, deployment pipelines, monitoring, and operational reliability, with AWS at the center of that stack.
AWS
Jenkins
Docker
Terraform
Kubernetes
Cloudflare
New Relic
PagerDutySoftware engineering
I build web applications, REST APIs, CMS platforms, and iOS applications with an emphasis on maintainable structure and sensible abstractions.
LAMP
DI
iOS
REST
CMS
Unit TestsLanguages
These are the languages I use most often or feel most comfortable working in when the project calls for them.
PHP
Swift
SwiftUI
Bash
JavaScript
HTML
CSSSupporting tools
The supporting tools matter too. Good delivery depends on version control, release tooling, frameworks, and the systems that help teams stay productive.
Xcode
Git
TestFlight
Laravel
CakePHP
Yii
WordPressI am not rigid about methodology, but these principles consistently lead to code that is easier to change and easier to reason about.
S
Keep classes and modules focused so they are easier to understand, change, and debug.
O
Extend behavior when needed, but avoid rewriting stable code just to add something new.
L
Derived types should behave in ways that do not break the code using the shared abstraction.
I
Smaller, more specific interfaces usually produce cleaner designs than broad ones that do too much.
D
Depend on abstractions instead of concrete implementations so systems stay easier to test, swap, and evolve.