Validate HELLO, I’M
Jazdy
Labajan.
System Developer Aspiring DevOps Engineer
I build thoughtful interfaces, reliable web systems, and the infrastructure that keeps them running.
- STATUS
- BUILDING
- FOCUS
- DEVOPS
- BASE
- CDO, PH
SELECTED WORK
Built with purpose.
Structured to last.
CURRENTLY
Where I am right now.
GITHUB
Contribution history.
Still building.
ATTESTATION
Built with people.
Backed by their words.
This space stays quiet until the words are real.
No invented testimonials. When someone I’ve built with shares feedback I can publish, it appears here automatically.
RESOURCES
Tools I trust.
Curated, not exhaustive.
ABOUT
A thoughtful front end.
A stronger foundation.
I’m Jazdy, based in Cagayan de Oro City, Philippines. I’m a 3rd year Information Technology student specializing in System Development and an aspiring DevOps Engineer.
I build web based systems with a focus on backend development, databases, UI/UX, and clean structure. I’m also exploring cybersecurity, secure coding, deployment, and system reliability.
My goal is simple: build useful systems, understand how they work, and keep improving them.
MY JOURNEY
Learning the layers.
Building the foundation.
A short path through the experiences that shaped how I build today.
-
GOLDEN HERITAGE POLYTECHNIC COLLEGE
Where coding started
Started exploring programming and web development during Grade 9 and discovered that I enjoyed building things through code.
-
PHINMA SENIOR HIGH
Building the fundamentals
Strengthened my foundation in IT systems, networking, and programming through the TVL ICT strand.
-
NOW
PHINMA COC · 3RD YEAR
Going deeper into systems
Studying Information Technology with a System Development specialization while growing toward backend, security, deployment, and DevOps.
WHERE I’M HEADED
From building systems to understanding how they run.
I’m expanding beyond application development into deployment, infrastructure, automation, security, and system reliability.
CONTINUED LEARNING
Certificates & credentials
Programming foundations, backed by completed courses and assessments.
SELECTED WORK
Ideas into interfaces.
A closer look at
what I’m building.
CLIENT OPERATIONS SYSTEM
Wannabees KTV
Sales, Inventory & Customer Management
A live web system built for Wannabees Family KTV to centralize day-to-day operations. It gives staff a clear view of room availability, active orders, time-out alerts, sales activity, inventory, and customer-related workflows from one operational interface.
- STATUS
- Deployed
- ACCESS
- Verified owner and staff accounts
- FOCUS
- Operations, reporting, and service flow
Project brief
The dashboard prioritizes live operational awareness: new and active orders, room occupancy and cleaning states, available rooms, and time-out alerts are visible at a glance. The system also includes a secured login flow with verification, sales reporting with trend data and transaction filtering, and management areas for inventory, pricing, users, and settings. The application is published online, but operational pages remain restricted to verified accounts.
DEPLOYED STUDY PLATFORM
Geminile Study Hub
A deployed study hub I built as a focused web experience for student learning, study workflows, and organized access to resources.
- STATUS
- Live deployment
- ACCESS
- Public web experience
- FOCUS
- Student learning and resource organization
Project brief
This project is presented as a real deployed build rather than a concept. The live deployment is linked directly so the interface and current experience can be explored as shipped.
CLIENT PORTFOLIO
Rose Ann Camposo Portfolio
A personal portfolio I built around a psychology student's story, skills, journey, and contact experience. The design keeps the presentation warm, calm, and human-centered while giving each part of her path room to breathe.
- STATUS
- Live deployment
- ACCESS
- Public portfolio
- FOCUS
- Personal narrative and clear information hierarchy
Project brief
The site introduces Rose Ann as a psychology student and future clinician, then carries that narrative through About, Skills, Journey, and Contact. The interface emphasizes personal storytelling, readability, and an approachable tone instead of a generic portfolio template.
Real builds first. The collection will keep growing as I ship more.
THE STACK
Technologies I use, know deeply, and reach for by default.
- JavaScriptWeb development, frontend and backend
- PythonAutomation, scripting, backend development
- JavaBackend development
- DartMobile development with Flutter
- React JSInteractive user interfaces and components
- BootstrapResponsive web design
- HTML/CSSSemantic markup and styling
- Node.js & ExpressServer-side applications and APIs
- MongoDBNoSQL database management
- MySQLRelational database management
- FlutterCross-platform mobile application development
- DartFlutter development
- VercelFrontend deployment and hosting
- Git & GitHubVersion control and collaboration
- VS CodePrimary development environment
- XAMPPLocal development server
- Anthropic ClaudeAI assistant for reasoning and basic code completion
- CopilotAI-powered code for checking bugs and suggestions
PLAY
Take a quick dev break.
Pick a mini-game. Each one opens in its own game screen without leaving Play.
Debug the workstation.
Click the part of the desk you would check first.
Make the release call.
Build is green and the checks are clear.
Choose what you would do.
Catch it before it escapes.
Catch 5 bugs before 3 escape.
Know the right port.
Select the default port.
Match 5 services.
Ship it in the right order.
Trigger the first stage.
Clear the matching pairs.
Find all 4 matching pairs.
PRAISE
Words from people
I’ve built with.
Jazdy keeps the technical side organized and communicates clearly about what still needs to be done. He pays attention to both how the system works and how it feels to use.
He does not stop at making a feature work. He checks the flow, cleans up the interface, and keeps improving the implementation until the result feels complete.
When something breaks, Jazdy takes the time to trace the problem instead of applying a quick patch. That makes technical issues much easier to work through as a team.
Jazdy is usually the person who looks past the obvious solution and asks how the whole workflow should fit together. That helped our project stay structured as it grew.
He notices small interface details that are easy to ignore, but he also understands that design has to support the actual task. The result is usually cleaner and easier to follow.
Jazdy takes ownership of his part of the build and is willing to go back into it when something can be improved. He is consistent about turning feedback into actual changes.
He is careful about how data moves through a system. Even in smaller projects, Jazdy thinks about validation, structure, and what could go wrong before it becomes a bigger issue.
Jazdy asks the right questions when requirements are unclear. That usually saves time later because the team understands what needs to be built before everyone starts coding.
He is the type of teammate who keeps checking the small details after the main feature is already done. That extra pass usually makes the final output feel more polished.
Jazdy does not treat security as something to add at the end. He brings up access control, validation, and data protection while the system is still being designed.
He learns quickly when the project needs something unfamiliar. Instead of waiting for someone else to handle it, Jazdy usually researches the problem and comes back with a workable direction.
What stands out is that Jazdy cares about whether the system will still make sense after more features are added. He tends to build with the next step in mind.
WORKING TOGETHER
How I work with people, what good collaboration looks like, and how to get started.
WHAT WE CAN BUILD TOGETHER
Product Build
End-to-end development of a web product — from concept to launch. Design, engineering, and iteration.
Design Engineering
Design systems, component libraries, and the space where design meets code. Precision and craft.
AI Integration
Adding intelligence to existing products. Embedding LLMs, building pipelines, and making AI useful.
Consulting
Technical strategy, architecture review, team mentoring. Focused sessions that move the needle.
A GOOD COLLABORATION LOOKS LIKE
- Clear scope and shared goals from the start
- Honest communication, even when it’s uncomfortable
- Respect for craft — no rushed, sloppy work
- Room for iteration and genuine feedback
- Ownership and accountability on both sides
START A CONVERSATION
If something feels like a good fit, send me a short note about what you’re working on. No long forms. Just a message.
jazdylabajan@gmail.comRESOURCES

