Building practical software, exploring how systems work, and learning by shipping.
Java β’ Spring Boot β’ React β’ MySQL
I'm a full-stack developer interested in building software that solves practical problems.
I enjoy taking an idea from problem β prototype β working application. Along the way, I'm especially interested in understanding what happens behind the scenes: how APIs communicate, how databases are designed, how systems handle growth, and how simple decisions in architecture affect a product.
I don't want to just learn technologies. I want to understand why systems are built the way they are.
- ποΈ Backend architecture and system design
- π Event-driven systems and asynchronous communication
- π‘ Reliable API and backend service design
- ποΈ Database design, indexing, and performance
- π€ Open-source collaboration and code review
Learning by building, breaking things, fixing them, and understanding why they broke.
The problem
Students can miss classes when schedules, announcements, and reminders are spread across multiple platforms.
The approach
Notify sends scheduled notifications before upcoming classes, helping students stay aware of their timetable without manually checking multiple sources.
What I learned
Working with backend APIs, databases, Firebase Cloud Messaging, and the challenges involved in delivering notifications reliably.
Tech: Java β’ Spring Boot β’ MySQL β’ Firebase FCM
The problem
Moving text between devices often means opening a messaging app, sending yourself a message, and copying it again on another device.
The approach
System Paster allows text to be transferred between devices using a QR code, without requiring users to create an account.
What I learned
Designing a simple user flow, working with REST APIs and databases, and handling limitations when transferring larger amounts of text through QR codes.
Tech: React β’ Vite β’ Spring Boot β’ MySQL
The problem
People sometimes travel to a local store without knowing whether it is currently open.
The approach
Openly helps users check the availability status of nearby stores before visiting.
What I learned
Building a simple, focused product experience and thinking about how location-based information can solve everyday problems.
Tech: React β’ Vercel β’ API Integration
Small problems can still lead to interesting software.
I'm also interested in learning through open source.
Some of my contributions and projects focus on creating beginner-friendly resources and gaining experience working with code written by other developers.
- ReactDevs
- devtasks
- Java and Spring Boot learning resources
I'm particularly interested in improving my understanding of:
- Reading unfamiliar codebases
- Writing maintainable code
- Working with Git and collaborative workflows
- Receiving and applying code review feedback
I learn best by building.
Tutorials are useful for understanding concepts, but I believe real learning happens when you have to make decisions yourself:
What should I build?
How should these components communicate?
Why is this API failing?
Why is this query slow?
What happens when the requirements change?
Those questions usually teach me more than simply completing another tutorial.
My current focus is becoming a stronger backend and full-stack developer by building projects and improving my understanding of:
Java β Spring Boot β Databases β APIs β System Design
At the same time, I'm continuing to explore new technologies whenever they help me understand how modern software systems are built.
I'm always interested in:
- π‘ Discussing software ideas
- π€ Collaborating on projects
- π± Open-source contributions
- π§ Learning from other developers
Thanks for stopping by π
Still learning. Still building. Still curious.