I'm a full stack software engineer who builds systems that run in production with real users. I've independently architected and shipped 8+ commercial platforms with Next.js, ASP.NET Core, and Node.js.
<section id="giris">
<h2>My Approach</h2>
<p>
Before I solve a problem, I try to genuinely understand it: the data model, the concurrency scenarios, where the system will break as it grows. Writing code is the last step for me — the architectural decision is the critical one.
</p>
<h3>My Engineering Approach</h3>
<p>
I design systems built on Clean Architecture, SOLID principles, and testability. Given a choice between shipping a feature fast and being able to extend it three months later without breaking it, I always choose the latter.
</p>
</section><div id="vizyon">
<h4>How I Solve Problems</h4>
<p>
I approach hard technical problems — IDOR, TOCTOU stock race conditions, real-time synchronization — with concrete engineering solutions: isolation levels, backplanes, rate limiting. Not assumptions, measurable decisions._
</p>
</div>























8+ commercial platforms: multi-tenant marketplaces, real-time appointment systems, compliance-grade enterprise exam platforms, and e-commerce systems with production payment infrastructure. All shipped at Lighthouse 95+.
.jhun comes from Ceyhun Turkmen's name and makes a playful nod to JSON format: the dot suggests objects and the curly braces represent data blocks. The name and the logo reflect my modern, minimal and tech-focused identity both visually and conceptually.
The navy color symbolizes the night sky's infinity in web design. The navy in the .jhun logo represents the inspiring order of stars and my boundless curiosity.
"Code is the last step of solving a problem — I understand the problem first."
A summary of the systems I've independently architected and shipped.
Production Platforms
Projects Shipped
Lighthouse Score
Full Stack
The principles that guide how I write code.
I separate layers with clear boundaries; on BAZR I kept a 33-entity domain model manageable this way with CQRS/MediatR.
I don't build real-time systems bound to a single instance; on Rezervo and BAZR I designed for horizontal scaling from day one with a Redis-backed SignalR backplane.
Core Web Vitals and Lighthouse scores aren't a bonus, they're part of the deliverable — I've kept 95+ consistently across the projects I've shipped.
I test interfaces with keyboard navigation; aria labels and semantic HTML are a default starting point, not a layer added afterward.
Type safety, a consistent folder structure, a readable commit history — that's the standard I hold myself to for code I'll reopen a year later.
xUnit/Moq on the .NET side, Jest/Supertest on Node — I don't ship critical business logic (payments, stock, authorization) to production untested.
FluentValidation, Zod, and Serilog structured logging — I want to catch failures in the logs before a user has to report them.
I work out the data model and concurrency scenarios first; that's how TavAkademi's exam-integrity system and BAZR's stock race condition got solved.
Systems I've independently architected and shipped since 2024.
Remote · 2024 – Present
Corporate Training & Exam Platform
JWT-RBAC with TOTP/2FA and GeoIP session validation for airport security personnel, a polygon-editor X-Ray exam simulation, and automated certificate generation.
6 Active Commercial Projects
IşPool, Balkolüx, Ferudun Polat Home, NowArt Plicell, RosallieBaby, BarScarf — 6 live platforms with iyzico payments, KVKK-compliant auth, and Meta CAPI/GA4 conversion tracking.
Multi-Tenant Marketplace
Clean Architecture/CQRS 33-entity domain model, Stripe payments + escrow wallet, real-time order tracking via SignalR + Hangfire.
Grouped by category — technologies I use in production.
Education, certifications, and languages.
B.Sc. Computer Engineering
Iskenderun Technical University
2020 – 2024