Yusuf Rokib
Don Martial.

I'm Yusuf Rokib, known as Don Martial, a self-driven technology learner, software developer, digital product builder and graphic designer. I enjoy learning by taking an idea, working out how it might function, and building a version I can test, improve and learn from.

Rather than limiting myself to one area of technology, I explore different parts of the software development ecosystem. That includes frontend development, backend systems, databases, APIs, cloud platforms, authentication, payment integrations and digital product design. I am interested in how the pieces work together, not only in how to write one part of the code.

Many of my projects begin with one simple question: “What if I build this myself?” From there, I research the technology, plan the system, design the interface, write and test code, work through errors, deploy where appropriate, and keep improving what I learn.

I see every project as an opportunity to understand a new tool, solve a problem, or improve the way I approach technology. Some projects become useful products; others are experiments, prototypes or learning exercises. Each can teach me something valuable.

I believe software needs more than functional code. Interface layout, typography, colors, branding, graphics and user experience all influence how a person understands and uses a product.

My creative interests include graphic design, digital graphics, social media designs, marketing graphics, flyers, branding, UI concepts and visual layouts. This combination of technology and design encourages me to consider both the technical side and the visual side of a digital product.

My goal is to keep improving at the point where functionality, communication and design meet.

When I encounter a technology I don't understand, I try to break it into smaller questions. What is it? Why does it exist? How does it work? How does it communicate with other systems? How can I use it? Can I build something with it—and can I improve what I build?

Sometimes a bug is where the real lesson begins. A failed deployment, an unexpected API response or a database problem can reveal what I still need to learn. I try to use those moments to investigate, repair the issue and understand the cause.

I don't expect every first version to be perfect. My focus is to build, test, learn and keep improving one project at a time.

You'll find experiments, projects, prototypes, backend systems, frontend applications, APIs and other things I'm learning along the way. Some repositories may be experimental or unfinished. Not every project starts as a finished product.

Some repositories represent an idea; some represent a lesson; some represent a problem I was trying to solve; and some grow into more complete applications. I want to keep learning from the process and improving the quality of the things I build.

Every project gives me an opportunity to understand something new. Every bug, deployment issue or API integration can introduce another lesson. I'm focused on steadily improving—one project at a time.