A frontend engineer building toward AI-native systems.
I’m Farkhan Nabiel Makarim, an Applied Software Engineering student at Politeknik Negeri Lampung. I enjoy building digital products that combine engineering, design, and user experience — from business applications and e-commerce systems to immersive web experiences built with WebGL. AI-native engineering is the direction I’m actively growing toward, and the work is judged by one thing: whether the system earns trust under real conditions.
Four commitments behind every system
- 01
Systems thinking
I design for the whole, not the feature. Data flow, failure modes, and the seams between parts get the same attention as the surface — because that is where products quietly succeed or break.
- 02
Software engineering
Typed, tested, and legible. I treat code as a long-lived asset: clear boundaries, honest abstractions, and tooling that keeps a codebase fast to change months after launch.
- 03
Experimentation
AI moves weekly, so I keep a lab. I prototype aggressively, measure honestly, and let evidence — not hype — decide what graduates into production.
- 04
Problem solving
I start from the real constraint, not the obvious task. The best version of a system is usually smaller, sharper, and closer to the actual problem than the brief first suggests.
Potential, proof, partnership
I started where most engineers do — chasing the satisfaction of a thing that simply works. That hunger turned into a habit of shipping: client work, a final-year thesis, and interactive web products on the other side of the screen.
Somewhere along the way the question changed from “can I build this?” to “will this hold?” Proof became the point — measurable outcomes, documented decisions, systems that behave the same on a bad day as a good one.
Now I’m building toward that standard: growing into an engineer who can take an ambiguous idea, pressure-test it, and turn it into something durable — while learning to weave AI into the work responsibly. That’s the work I care about — the kind that keeps earning its keep long after launch.
What I bring to a team
Engineering
- TypeScript / React / Next.js
- API & data modeling
- Performance & accessibility
Creative / 3D
- Three.js / React Three Fiber
- GLSL shaders & WebGL
- GSAP motion
AI-assisted
- AI-assisted development
- LLM integration basics
- Exploring agentic workflows
Have a system worth building well?
I work best with founders, CTOs, and teams who care about the details that survive contact with real users.