Software Engineer · AWS Solutions Architect
I build things, break things intentionally to understand them, and fix things other people can't figure out.
stack = {
"languages": ["Python", "SQL", "Java", "C++", "TypeScript", "Bash"],
"cloud": ["AWS (EC2, S3, Lambda, DynamoDB)", "Docker", "Kubernetes"],
"frontend": ["Next.js", "React", "Node.js", "Tailwind CSS"],
"databases": ["PostgreSQL", "Firebase"],
"tooling": ["Git", "Postman", "Jira", "Linux"],
}| Repo | What it does | Why it's interesting |
|---|---|---|
| othello | Othello AI in Java | Minimax with alpha-beta pruning — full game tree search |
| RealEstatePrediction | Housing price ML model | End-to-end pipeline: EDA → feature engineering → prediction |
| LifeBalancePlus | Cross-platform wellness app | Flutter + Firebase, shipped on iOS & Android |
| Banking-System | Banking simulation in C++ | OOP-heavy, focuses on data integrity and secure transactions |
| jayson-portfolio | Personal portfolio site | Next.js 14, deployed on Vercel |
I came up through Apple support before moving into SaaS engineering. That background means I don't just fix symptoms — I dig until I find the root cause, document it properly, and figure out why the system allowed it in the first place.
Most of my side projects are attempts to build things I've seen, but would like to make them better, or to understand infrastructure decisions well enough to have an opinion about them.
