Hey, I'm Naufal — a Software Engineer who enjoys turning ideas, real-world problems, and complex workflows into thoughtful digital products.
I believe great software is more than code that works. It should solve the right problem, feel intuitive to use, and be built with engineering decisions that make sense.
My approach sits at the intersection of product thinking, user experience, and software engineering.
I enjoy exploring the entire journey — from understanding a problem and shaping an idea to designing interfaces, building systems, and refining the details.
What I care about:
- 🎯 Problem-solving: Understanding the why before deciding the how.
- 🎨 User experience: Creating interfaces that feel intuitive, clear, and delightful.
- 🏗️ Engineering quality: Writing maintainable code and making thoughtful architectural decisions.
- 🧩 Product thinking: Connecting technical implementation with actual user needs.
- 🌱 Continuous learning: Staying curious, experimenting, and improving through building.
A few projects that represent how I think, build, and solve problems.
Making language learning more meaningful through patterns, context, and active recall.
An interactive language-learning product designed around cognitive patterns, structured learning paths, Active Recall, and Spaced Repetition.
- Learning experiences built around linguistic patterns and context.
- Structured multilingual curriculum.
- Interactive lessons and practice experiences.
- Learning progress and review mechanisms.
What it represents: Product thinking, learning experience design, and interactive application development.
💡 What I find interesting about this project
Veloa explores how software can support the way people understand and retain information — not simply display learning materials.
It combines product design decisions with structured learning experiences and interactive application behavior.
A system for turning plans into measurable progress.
A personal productivity application that brings daily tracking, time blocking, projects, career activities, learning, journaling, and reflection into one workspace.
- Daily and weekly planning.
- Time-blocking and focus tracking.
- Project and career management.
- Learning progress with spaced repetition.
- Structured application architecture and data isolation.
What it represents: Full-stack engineering, system design, data modeling, and engineering discipline.
💡 Engineering interests behind Fyura
This project explores how domain rules, services, repositories, authentication, database constraints, and user interfaces can work together as a coherent application.
A key design principle is:
Record what actually happened, not what was planned.
Solving operational problems with practical software.
A web-based point-of-sale and distribution management system designed for an egg distribution business.
- Sales and multi-item order processing.
- Inventory synchronization.
- Customer and supplier payment tracking.
- Installment and transaction history.
- Excel data export and receipt printing.
What it represents: Real-world problem solving, business workflow analysis, and practical software development.
📄 Research publication: Pengembangan Sistem Transaksi Penjualan Toko Uwais Telur Menggunakan Metode Rapid Application Development
💡 Why this project matters
Uwais Telur represents an important part of my engineering perspective: software should be shaped around real operational needs.
The goal was not to build another generic POS application, but to address the workflows and challenges of a specific business.
I work with technologies across frontend development, backend systems, databases, and application tooling.
I enjoy learning by building, experimenting, and understanding how things work beneath the surface.
Some areas I'm interested in:
- 🏗️ Scalable application architecture and maintainable systems.
- ⚡ Web performance and frontend optimization.
- 🔐 Application security and data protection.
- 🤖 AI-powered applications and practical automation.
- 🎨 Design systems and thoughtful user experiences.
- 🧪 Testing, reliability, and engineering best practices.
I don't believe in learning technologies just to collect them. I prefer understanding a concept and applying it to something useful.
I'm always happy to connect with developers, designers, builders, and curious people who enjoy creating useful things.
Whether it's discussing software architecture, sharing project ideas, exploring new technologies, or collaborating on something meaningful — let's connect.

