Full-stack developer focused on web applications, backend systems, and reliable infrastructure
I build the systems a university actually runs on: exam platforms, faculty and directorate sites, and the servers underneath them. Most of my work starts with a process that still happens by hand and ends with something people use on a Monday morning.
01 — Selected work
A platform used by hundreds of people every week is a different design problem from a demo. These are the pieces I can show, plus the university sites I build and maintain.
A computer-based exam platform with three timed sections, automatic scoring, role-based access, offline answer buffering, and verifiable digital certificates.
Day-to-day development and operations for the public web presence of Universitas Ubudiyah Indonesia — six study-program sites, four directorate portals, and the internal systems staff use.
Practical infrastructure work I run for my own projects — static sites in containers, Caddy in front, service isolation, and the experiments that follow.
Public study-program and directorate sites I build and maintain as a programmer. Internal systems are not listed.
Small tools I maintain for my own setup, published because they might be useful to someone else.
02 — About
My route into software was not a straight line. I started with routers and cabling, moved into programming, and ended up responsible for the systems in between.
I studied Computer and Network Engineering at SMK Negeri 1 Banda Aceh, where the work was physical: configuring networks, running cable, administering systems. That background never left. I still reach for the network layer first when something breaks.
I graduated in Informatics from Universitas Ubudiyah Indonesia in 2026, and I work there as a programmer. The work covers internal information systems, study-program websites, and the infrastructure that supports them — which means I see the whole path from a requirement to a running service.
I start with the workflow, not the stack. Who does what, in which order, and what happens when a step fails? Most of the difficulty in institutional software lives in those exceptions, not in the happy path.
After that I optimise for operability: one deployment path, explicit configuration, logs that answer questions, and a database schema that matches how the domain actually behaves. I would rather ship a boring system that survives a semester than a clever one that needs me every week.
Most of my free time goes into Linux: the desktop stack, self-hosted services, and small utilities that fix problems I keep running into. I maintain two open-source projects — a session manager for the Umbriel Wayland compositor and a Noctalia plugin for Soundcore earbuds.
I am going deeper into backend engineering with Go, API architecture, and container-based deployments. Not as a rebrand — as the next layer of the same work.
03 — Expertise
I am not equally deep in everything below. Each group says what I use the tools for and how often I work with them.
Component-based front ends, responsive layouts, and applications that stay readable as they grow. I work mostly in React and Next.js at the university, and reach for Astro when a site is mostly content.
Seen in TOEFL Prediction System, study-program and directorate sites
API design, server-side application logic, authentication, and role-based authorization. I care about clear request boundaries, predictable error shapes, and permissions that are enforced in one place.
Seen in TOEFL Prediction System, internal UUI systems
Relational schema design, migrations, and queries that match how the application reads its data. PostgreSQL is my default; MariaDB and MySQL come with existing applications.
Seen in Exam data, university content systems
Linux servers, containers, reverse proxies, and the networking between them. I deploy with Podman or Docker, terminate TLS with Caddy, and keep services isolated per container.
Seen in This site, personal services, campus deployments
Git, the terminal, and an editor that stays out of the way. I debug from logs and request traces first, write tests where a failure would be expensive, and use AI assistance for grunt work rather than decisions.
Seen in Every project
04 — Experience & education
Work
2025 — present
Universitas Ubudiyah Indonesia · Banda Aceh, Indonesia
Education
2022 — 2026 · graduated
Universitas Ubudiyah Indonesia
Completed alongside full-time programming work at the university.
Vocational
SMK Negeri 1 Banda Aceh
Computer and network engineering: routing, switching, server administration, and cabling.
Achievement
Won the provincial Lomba Kompetensi Siswa in IT Network Systems Administration and represented Aceh at the national competition.
05 — Engineering notes
Write-ups about decisions, trade-offs, and things I had to learn the hard way. Some are finished essays; some are working drafts published as they are.
06 — Current focus
Active interests, not finished expertise. These are the areas getting my reading time and side-project hours.
Writing services rather than scripts: explicit structure, context handling, and tests that catch regressions before deployment.
Running more of my own services on Linux with Podman: isolated networks, reverse proxying, backups, and upgrade paths that do not need a rebuild every time.
Designing interfaces that survive version two — resource boundaries, error contracts, pagination, and authorization that is checked once.
Using agents and editors for repetitive work while keeping review, testing, and architectural judgement human.
07 — Contact
I am open to full-time roles and freelance work. The fastest way to reach me is email — tell me what the system needs to do, not just what stack you want.