building APIs β’ breaking prod β’ fixing it before anyone notices
backend engineer from phnom penh π°π who loves building microservices and optimizing database queries at 2am β
currently vibing with spring boot, asp.net, and laravel. docker containers are my comfort zone, and ubuntu is home.
status: open to work | down for interesting projects | always learning
backend:
java: "Spring Boot + JPA (the reliable one)"
dotnet: "ASP.NET Core + EF Core (when i need speed)"
php: "Laravel + Eloquent (for rapid development)"
databases:
relational: ["PostgreSQL", "MySQL"]
tools: "Navicat (because GUI > terminal sometimes)"
devops:
containerization: "Docker + Docker Compose"
os: "Ubuntu Server (22.04 LTS)"
deployment: "compose up -d and pray π"microservices that actually work
- REST APIs with proper documentation
- database schemas that don't make people cry
- docker containers that start on the first try (sometimes)
things i care about
- clean code > clever code
- readable commits > "fix bug" commits
- testing in prod (jk... unless?)
const developer = {
code: ["Java", "C#", "PHP"],
frameworks: ["Spring Boot", "ASP.NET Core", "Laravel"],
databases: ["PostgreSQL", "MySQL"],
tools: ["Docker", "Navicat", "Git"],
environment: "Ubuntu + lots of coffee",
currentlyLearning: "microservices patterns",
funFact: "i debug in production because i like living dangerously"
};