I build systems,
not just websites.
I'm Danish Iskandar, born in 2006, currently a diploma student in Computer Science at KPM Beranang. I'm still early in my journey as a developer, but I've always been curious about how technology works and how systems are built behind the scenes.
I enjoy learning by doing. Whether it's building small projects, experimenting with new tools, or fixing things that break, I use hands-on experience to understand concepts better.
I focus on improving how I write code, how I solve problems, and how I approach building software in a more thoughtful and intentional way.
Four years,
one line at a time.
The first line
I opened an editor because I wanted to know how the things I used every day were actually made. Nothing I wrote that year worked properly, and that turned out to be the point — every broken build taught me something a tutorial never would.
Making it work
I stopped copying and started building. Small tools, half-finished ideas, a lot of things I abandoned. Somewhere in there I learned to read errors instead of fearing them, and to sit with a problem long enough to actually solve it.
Learning by shipping
Diploma in Computer Science at KPM Beranang. The classroom gave me the theory, but the real learning happened at night — building projects nobody asked for, just to see whether I could take an idea all the way to something people could open in a browser.
The first real client
Someone paid me to build something their business depended on. That changed how I write code. Suddenly it wasn't about clever solutions — it was about systems that keep working on a Tuesday afternoon when I'm not around to fix them.
First internship at Perfect Internet
My first time building alongside a team instead of alone. Working to someone else's standards, reading code I didn't write, and learning how software gets made when it has to outlive whoever started it.
Ship it, then make it right
A working thing in someone's hands teaches me more than another week of planning ever will.
If I can't explain it, I don't understand it
I write code I could walk a client through. Cleverness I can't defend gets deleted.
Boring tech, interesting problems
The stack should be the least surprising part of the project. Save the risk for the parts that matter.
Build for the person who maintains it
Usually that person is future me, and future me is always in a hurry.
Finishing my diploma at KPM Beranang while building systems for real businesses.
Backend architecture, database design, and how to scope a project before writing any code.
AI-assisted workflows, and how much of my own process I can automate without losing the craft.