Full-stack developer

Building reliable software with calm, structured execution.

I build web applications that are clean, maintainable, and grounded in strong technical decisions. This portfolio highlights my thinking process, measurable outcomes, and approach to solving engineering problems.

View ProjectsContact

Engineering Snapshot

Portfolio foundation

Available

Focus

Maintainable products, practical architecture, clean delivery.

Current Stack

Astro, React, TailwindCSS, TypeScript, database-backed apps.

Working Principle

Craftsmanship over hype. Clarity over complexity.

01

Foundation

00

Client JS

SSG

Output

About

Focused on dependable engineering.

I see software engineering as work that depends on clarity: understanding the problem, choosing the right tradeoffs, and executing with a structure that the next team can understand.

This website is designed to present that way of thinking with calm focus. The homepage creates the first impression, while project details become the evidence: problems, technical decisions, outcomes, and lessons learned.

Skills

A practical, maintainable stack.

Skills are organized by work category so recruiters can scan them easily while leaving room for more specific data in future iterations.

Frontend

  • Astro
  • React
  • TypeScript
  • TailwindCSS

Backend

  • API design
  • Authentication
  • Validation
  • Service structure

Database

  • Relational data
  • Schema design
  • Query planning
  • Migrations

Cloud

  • Deployment
  • Environment config
  • Static delivery
  • Runtime basics

DevOps

  • Build checks
  • Version control
  • Release discipline
  • Debugging

Tools

  • Git
  • Node.js
  • npm
  • Documentation

Experience

A workflow centered on impact.

This section is prepared as a timeline. Until professional experience data is added, the content shows the working patterns that will support impact-focused writing instead of job-description copy.

01

Problem framing

Start with context before implementation

Understand business goals, users, technical constraints, and the definition of done before choosing a solution.

02

System design

Prefer clear structure over clever abstractions

Create modules, data flows, and interfaces that can be understood later without depending on the original author's memory.

03

Delivery

Ship in increments with visible quality gates

Prioritize stable builds, measurable changes, and documentation for important decisions as complexity grows.

Featured Projects

Project details will carry the portfolio.

Project cards are intentionally large and structured so they can later be replaced with real case studies without changing the layout system.

View all projects
FrontendArchitecture
2026
Frontend architecture3 tools

Portfolio Architecture

Fondasi portfolio berbasis Astro yang ringan, konsisten, dan siap diperluas menjadi studi kasus lengkap.

Problem
Portfolio perlu terasa profesional tanpa bergantung pada efek visual berlebihan.
Solution
Menggunakan Astro untuk konten statis, Tailwind token untuk konsistensi, dan React hanya untuk island.
Result
Halaman awal tetap ringan, jelas, dan siap diperluas menjadi project detail yang lebih kuat.
AstroTailwindCSSTypeScript
Content StrategyArchitecture
2026
Content systems3 tools

Project Detail Framework

Kerangka studi kasus yang membantu recruiter membaca problem, keputusan teknis, dan hasil dengan cepat.

Problem
Recruiter butuh melihat cara berpikir teknis, bukan hanya daftar teknologi.
Solution
Menyusun struktur studi kasus yang menjawab problem, solution, technologies, result, dan challenge.
Result
Setiap proyek nantinya punya format evaluasi yang konsisten dan mudah dibandingkan.
Content strategyCase studyStatic components

Articles

Notes on craft and clarity.

Short notes on engineering, interfaces, and technical decision-making.

July 01, 2026

Keeping frontend architecture boring in a good way

A practical note on choosing predictable frontend boundaries before clever abstractions.

June 28, 2026

Writing project case studies that show engineering judgment

How to turn a project page into evidence of decisions, tradeoffs, and outcomes.

June 25, 2026

How I evaluate technical tradeoffs

A compact framework for comparing implementation options without turning everything into a debate.

View all articles

Certificates

Relevant proof, carefully curated.

This grid is intentionally concise so certificates do not take over the page. Final data can be replaced with certificates that are genuinely relevant.

Frontend fundamentals

Certificate placeholder

Backend architecture

Certificate placeholder

Database design

Certificate placeholder

Contact

Let us talk when clarity matters.

For interviews, collaboration, or technical discussions, use one of the channels below. The form on the right only loads when this section is visible to keep the page lightweight.

LinkedInGitHubEmailResume