Tools I use, areas I'm strong in, and areas I'm growing into.
Not a skill-percentage chart — a more honest map of engineering capability based on real production experience.
Core tools.
PHP / Laravel
Primary backend stack for production applications and workflow systems. Built high-traffic platforms in Core PHP. Currently working with Laravel on a CMS project for a call center suite.
MySQL
Schema design, normalization, query optimization, temporary table strategies, and reporting-heavy data handling. Core to how I think about application performance at scale.
Bootstrap / JavaScript
UI integration and practical front-end support for full-stack delivery. Focused on functional interfaces rather than design complexity.
Tools I can work productively in.
Python / Django
Built a full-fledged online learning platform in Django with student and teacher accounts, courses, assignments, and file uploads. Comfortable building with it but position it as working knowledge rather than primary specialization.
Automation & Utilities
Built SMS and email automation systems with multi-server support, retry logic, and audit logging. Created Python utilities for batch file renaming with UUIDs and CSV data cleaning for SQL import.
Core engineering skills.
OOP
Clean Code
Problem Solving
API Design
How I think about skill levels.
Things I can build with confidence:
Things I can work productively in:
Things I'm actively growing into:
Tools I work with daily.
Git
Linux
Postman
Apache
Engineering areas I enjoy working in.
Workflow Systems
I enjoy systems where business rules, process flow, and software logic intersect to solve real operational problems — like complaint escalation and service processing.
Data-Heavy Applications
Especially systems where database behavior shapes application performance and schema decisions have long-term impact on reporting and scale.
Automation & Tooling
Building tools that replace manual processes with reliable automated systems — messaging engines, data utilities, and process-driven backend modules.
Areas I want to grow deeper in.
My interest is gradually shifting from application development alone toward deeper architectural thinking — especially system behavior, scale constraints, and software design trade-offs.
How I choose technology.
Prefer tools that reduce complexity rather than add novelty.
Choose technology based on problem fit, not trend value.
Reliability and maintainability matter more than fashionable stacks.
Good engineering often comes from good decisions more than many tools.
What I'm deepening.
- Laravel framework — actively building a CMS for a call center suite
- Advanced Laravel internals and architecture patterns
- Transaction and concurrency concepts
- Distributed system fundamentals