Understanding the core problem before writing a single line of code
I always start by diving deep into the actual requirements. Whether it's a freelance gig or a complex system design, I need to understand the 'why' before I can architect the 'how'.
Why is this step crucial?
Jumping straight into code often leads to technical debt. By mapping out the data flow, database schema, and system architecture first, I ensure the foundation is solid.
My Educational Journey
Self
Learn
Continuously exploring advanced web technologies and backend systems outside of my formal school curriculum to build real-world, scalable applications.
SMKN 1
Ciamis
Built a strong foundation in software engineering, networking, and core programming principles to kickstart my technical journey.
University
Majoring in Software Engineering in a highly entrepreneurial ecosystem. Beyond just writing code, I am learning how to build digital products from scratch, innovate, and turn technical ideas into real businesses.
Imasterthesubtletiesofdiverseecosystemsandactivatecreativesolutions
My primary focus is backend architecture and systems engineering. I enjoy designing databases, building high-performance APIs in Go or Node, and managing infrastructure using modern DevOps practices.