Skip to content
Arkan Nugraha

About me

Building
production software.

I'm Arkan Nugraha, a fullstack developer focused on shipping practical applications across web, mobile, and SaaS platforms.

Quick facts

NicknameArkan Nugraha
FocusSoftware development
LocationWest Java, Indonesia
InterestFutsal

Favorite club

LiverpoolLiverpool FC (Premier League)Persib BandungPersib Bandung (BRI Super League)

My story

I started coding in 2024 with Python, then moved into HTML, CSS, and JavaScript before expanding into PHP and Flutter. Each step taught me how to think in systems rather than just syntax.

At SMK Negeri 1 Cianjur, I focused on practical, hands-on projects. That background pushed me toward real products instead of tutorials, most notably WorksPass, where I worked through multi-tenant architectures, data modeling, and shipping features that people actually depend on.

I see every project as a problem to solve, not a feature list to finish. I care about the decisions behind the code: database shape, API boundaries, deployment strategy, and how the product behaves when things go wrong. That mindset shows up in the work itself.

Outside coding, I play futsal, practice armwrestling, and spend time in Minecraft or eFootball. Those activities keep me competitive, patient, and curious, qualities that directly help me when debugging complex systems or improving products under pressure.

Right now I am focused on sharpening my cross-platform skills, with a strong preference for systems that are easy to maintain, easy to extend, and easy to deploy. I want projects that combine clean architecture with real-world impact.

Visit my GitHub

Languages and tools

Technologies I use.

Languages & Frameworks

Python
HTML
CSS
JavaScript
PHP
Laravel
Dart
Flutter
Express.js
TypeScript
React
Next.js
Tailwind CSS

Databases & ORM

MySQL
MongoDB
Firebase
PostgreSQL
Prisma

Tools & Environment

VS Code
Git
Apache
Arduino
Postman
Antigravity
Docker

Cloud & Hosting

GitHub Pages
InfinityFree
AeonFree
Vercel

How I work

Production over
perfection.

Ship working features first

Prioritize functionality people can use over polished mockups.

Trace bugs to their root cause

Fix the cause instead of stacking patches on the symptom.

Document decisions, not just code

Explain why a choice was made so the next change stays safe.

Keep architecture simple and scalable

Prefer plain, obvious boundaries over clever abstraction.