Backend Engineer
Building and maintaining backend services in TypeScript with MongoDB. Designing scalable APIs and contributing to production infrastructure.
I'm Denisetiya (Deni Setiya) — a passionate Backend Engineer who occasionally crosses into Fullstack territory. I build robust APIs, ship open-source libraries to the community, and live in the terminal. Strong background in DevOps, Linux as my daily driver, and a deep love for type-safe TypeScript.
I'm Denisetiya — a Backend Engineer who occasionally slips into Fullstack. I ship scalable APIs, build libraries for the community, and run Linux as my daily driver.
Comfortable with API gateways (Nginx, Traefik, Kong), deeply invested in TypeScript, and slowly going deeper into Go and Rust for systems work.
A curated slice of recent work. Each project has its own war stories — ask me.
High-performance REST API framework powered by uWebSockets.js. Minimal deps, maximum throughput.
TypeScript validation library with built-in i18n (ID, JP, EN). Zod-like API, tuned for speed.
Developer-first security validation CLI for API, web, and domain audits. CI/CD-ready outputs: Console, JSON, HTML, SARIF, JUnit. Non-destructive payloads, scope allowlists, redacted reports.
Sistem manajemen restoran modern — online ordering, cart, Midtrans payments, admin dashboard. Built on Laravel 12.
Reusable, production-ready Nginx API Gateway. Auto SSL (Let's Encrypt), per-IP rate limiting, easy service registration, full Docker Compose setup.
Dynamic SVG cards for GitHub profile stats. Public hosted API — no token, no Vercel needed. Responsive all-in-one card.
Modern healthcare backend: symptom analysis, medication recs, disease lookup, drug interaction checks.
Robust e-commerce backend. Express, TypeScript, MongoDB, Prisma, Zod — full type safety end-to-end.
Comprehensive Go REST API w/ clean architecture, validation, JWT auth, MongoDB. Production-ready template.
Modern feature-rich Markdown editor. Real-time preview, syntax highlighting, advanced formatting tools.
Lightweight scroll-animation library for React & SSR frameworks. Customizable, tiny footprint.
Picked for outcomes, not hype. Not married to any of these — but they've earned their place.
Less of a methodology, more of a default. Adapts to the project, never the other way around.
We dig into the problem before the solution. Users, constraints, success metrics — all on the table.
Prototype the architecture. Sketch the API. Walk through edge cases. Cheap to change, costly to skip.
Ship in thin slices. Tested, observable, reversible. Every PR is a small bet you can win or unwind.
Performance pass, copy pass, accessibility pass. Details are the difference between OK and remarkable.
Building and maintaining backend services in TypeScript with MongoDB. Designing scalable APIs and contributing to production infrastructure.
Built full-stack web applications using Django and MySQL. Owned features end-to-end from database schema to frontend implementation.
Delivered web projects for diverse clients using React.js and Express.js. Handled scoping, implementation, deployment, and post-launch support.
Assisted faculty in teaching advanced programming concepts in Python. Guided students through practicum sessions, code reviews, and problem-solving.
Shipping libraries for the community — Valdix (validation), Qwe (web framework), Animate On View (React). Focus on type safety, performance, and minimal dependencies.
Cherry-picked from past collaborators, clients, and teammates.
"Code is read more than written. I try to make every line carry meaning — and reserve prose for the things prose alone can express."
"A good library is one you forget you depend on. The bad ones interrupt your day."
"Linux on the desktop isn't a meme. It's a feedback loop where every layer is inspectable. That's the addiction."
Why your API needs idempotency keys, what they actually buy you, and how to implement one without creating a new class of footguns.
How thinking in milliseconds-per-feature reshaped how I design APIs and UIs.
A controversial take on code documentation and what to write instead.
Got a product idea, a tricky technical problem, or just want to chat about distributed systems? My inbox is open.