Hello! This page is to demonstrate my technical skills to anyone interested (co-workers, friends, and potential employers).
Below is a summary of my github repos that are in a "demo" state that I believe help demonstrate my architectural and coding skills to prospective employers. The intent is to showcase my personal and organizational infrastructure, managed as code and designed for best practices, automation, and clarity.
I use jsonresume to host my resume here
- architecture, terraform, ci/cd, analytics, cloud development --> Poly-repo Cloud Organizational Example
- learning from scratch, coding with no-prior experience ---> My first python backend API
- passion, self-directed project ---> Passion project - OSRS bot (Out of date)
Poly-repo Cloud Organizational Example (example of an opinionated ideal state for a corporate code base)
This serves as an opinionated example of how to practice IaaC for cloud, while separating repos and responsibilities to respective teams. The idea being that individual teams would be the code owners of certain repositories, and other teams could do PRs to the repos as needed. CODEOWNERS files would be implemented to control who has access to what, restricting the access for both tags and approvals for merges to the trunk (ie main) branch. Thus implementing SOC2 controls for approvals/automation, while also following best practices of inner-source within an organization
the 6 repos:
- github-org-infra: (owned by an infra & Security team) Central repo for managing the GitHub organization, repositories, teams, and settings via Terraform. Provisions and configures all other repos, controls who has access to PR.
- iam-oidc-permissions: (owned by Security/IAM team) Manages AWS IAM roles, policies, and OIDC trust for CI/CD pipelines. Secures CI/CD and cloud access for all repos, this prevents feature branches from accessing unauthorized
- cloud-org-infra: (owned by infra or Cloud/Network Security team) Cloud organization infrastructure, including DNS, subdomains, routing, and cloud resource management. Supports organizational controls and broader cloud resource configuration.
- frontend-app: (owned by an application/frontend team) Infrastructure and deployment for the static front-end application. Interacts with
backend-api. - backend-api: (owned by application/backend team) Serverless backend API infrastructure, consumed by the frontend and other services. Provides data to
reporting-analytics. - reporting-analytics: (owned by application/data team) Infrastructure for reporting and analytics, consuming data from backend.
As a passion project I started working on porting OSRS bots to python. The softwares goal was to automate money making and skill training in the game Old School Runescape. My personal goals for the project was I wanted to learn about manually managing memory bindings for a C library. I also wanted an exercise in porting a library from one langauage (pascal) to another (python).
- pyautoeios
- PyReflect
- my personal fork of pyscreeze to support images with transparency (outdated PR here )
Eventually I also want to get into a deeper understanding of computer vision, but for now this project is on hold due to the more important work of being a dad to young children.
Flask applicaiton made as part of an interview process. This serves of an example of a complete newb (me 5 year ago) making their first api. I made this 5 years ago before my time at torqata, where I learned a-lot from fellow backend developers, most importantly, the usage fastapi and alembic which are not present in this example below.