PK / 01
A little about me
01 / About
Engineering with intent.
I take products from requirements to implementation and deployment — across client applications, SaaS platforms, REST APIs, databases, authentication, and server infrastructure.
My current focus is Java backend development: Spring Boot, PostgreSQL, JPA/Hibernate, API design, system design, and scalable backend architecture.
JavaSpring BootPostgreSQLJPA / HibernateNode.jsReactMongoDBRedisREST APIsSystem DesignDockerGit
02 / What I Work With
What I Work With.
Backend Systems
REST APIs · Business Logic · Authentication · Authorization
Data Systems
PostgreSQL · MongoDB · Redis · Data Modeling · Caching
Application Architecture
Clean Architecture · Layered Architecture · SOLID · LLD · HLD
Product Engineering
Web Apps · Mobile Apps · SaaS · Client Platforms
Infrastructure
Linux · VPS · Git · Deployment · Background Processing
03 / Selected work
2022 — 2026Things I've built.
04 / Journey
From building features to understanding systems.
Build
Started by turning ideas and requirements into working web applications and full-stack products.
Ship
Moved from individual features to complete applications — APIs, databases, authentication, mobile apps, deployment, and real client requirements.
Understand
Began going deeper into software engineering fundamentals: OOP, SOLID, clean architecture, data modeling, testing, caching, and system design.
Go Deeper
Now focused on Java backend engineering with Spring Boot, PostgreSQL, JPA/Hibernate, security, Redis, and distributed systems.
Keep Improving
The goal is simple: write software that works today, is understandable tomorrow, and can evolve when the requirements change.
05 / How I Work
Engineering principles.
Not a list of skills. A visual representation of how I think about building software.
Explore the loop
01Model
Understand the problem before writing the code.
Nodes, relationships, and domain boundaries take shape.
02Build
Turn the model into working software.
Layers connect the client, services, APIs, and data.
03Test
Verify the behavior, not just the happy path.
Requests, responses, edge cases, and failure paths become visible.
04Measure
Understand what the system is actually doing.
Signals reveal latency, throughput, and the cost of each decision.
05Improve
Find what can be made simpler, faster, or clearer.
Complexity dissolves as the system is refined.
06Scale
Design for the next requirement, not just the current one.
The architecture expands without losing its shape.