AWS Cloud Adoption FinOps Initiative
Developed a FinOps program to modernize cost awareness and resilience across AWS for a 150-person engineering team — including meetings, guidance, tool setup,...
What It Is
Technical Documentation is the creation of structured materials explaining systems and processes. On this site, it matters because it transfers across technical, operational, and venture work instead of staying trapped in one narrow context.
Learn more: https://en.wikipedia.org/wiki/Technical_documentation
AWS Infrastructure Cost Reduction — FinOps with Custom Tableau Dashboards
Built Tableau dashboards from AWS Cost and Usage Reports to give leadership visibility into cloud spend using Tableau, Tableau Server, AWS Athena, S3, and...
Build Systems That Outlive Direct Involvement
Why durable systems are stronger than work that depends on one person staying permanently in the loop.
Collaborative By Design
Why capability expansion usually comes from structured collaboration rather than isolated solo output.
Company-Wide Engineering Documentation Initiative
Developed documentation for hundreds of concepts, systems, datasets, terminology, and deployment procedures. Fought to get the Atlassian stack provided to...
Consulting and Advisory
Engagements advising teams and organizations on strategy, architecture, and technical execution.
Contacts
How the systems I use to remember people, maintain context, and reduce relationship decay over time.
Course creation systems
Frameworks structure and deliver educational content in modular, progressive formats.
Documentation As Operating Infrastructure
Why documentation should be treated as part of the system itself, not as optional cleanup after the work.
Documentation Systems
Structured methods turn work into reusable artifacts such as case studies, SOPs, templates, and playbooks that both operate systems and teach them.