Let me do a quick, chaotic introduction of myself below. Don't worry, there will be a detailed about section further down.
Software design and AI integration. Product and software design, full-stack web development, graphic design, editorial and copy.
A RELUCTANT NOTE
I do not like making portfolios or sharing them, so it took a lot of annoyance on my part to make this portfolio a reality. It feels a lot like self-idolatry or narcissism to admire and showcase my own skills—almost like a peacock looking for attention. But someone said it is important for my career in this field, so here is my portfolio.
But to be honest, despite the fact that I have kept my best works to myself, it was quite fun to make this portfolio. Perhaps Sisyphus also likes to look at the scratch marks on his rock once in a while, admiring his own work.
The source-built sites live inside the laptop. Switch tabs — each preview is bundled with this portfolio, interactive, and independent of its public deployment.
Tap any icon. It opens the way it would on the phone in your pocket, because that detail is the difference between a mockup and a product.
I have a lot of apps and softwares I built that I cannot show publicly here.
A desktop that behaves like one. Double-click an icon; drag, stack, minimise and close the windows.
I have a lot of apps and softwares I built that I cannot show publicly here.
I'm Jazil. 22, and I've already had four careers. Hardware obsessive, then a professional graphic designer, then an English book editor for publishing firms, and now this — software design, which is where all of it was quietly heading the whole time.
None of those replaced the one before it. They stacked. That's the whole pitch.
TOOLS I AM COMFORTABLE WITH
VS Code
React Native
GitHub
Cursor
Photoshop
Premiere Pro
DaVinci Resolve
Codex
Claude
n8nPUBLIC FICTIONEvil Baby is the only title I share openly; my other authored work remains under private pen names. Royal Road ↗
TECHNICAL FOUNDATION
I know JavaScript and TypeScript, and I'm good with React Native. I'm also decent with assembly fundamentals, giving me a deeper foundational understanding of how computers work beneath the abstractions.
02 / THE SAME INSTRUCTION, FOUR LEVELS UP
mov eax, DWORD PTR [rbp-4] add eax, DWORD PTR [rbp-8] mov DWORD PTR [rbp-12], eax
int total = a + b;
total = a + b
Add the two numbers together.
I learned it from the bottom. That's why a new language costs me an afternoon rather than a year — the syntax changes, the machine underneath never does.
03 / LANGUAGES INSTALLED
04 / THE ARC
Hardware first. Understood machines physically before I understood them logically, and never lost the habit of asking what the silicon is actually doing.
From around ten years old, reading occupied much of my life. It began with fantasy—Harry Potter, Journey to the West, and similar worlds—then widened into Dune, The Stormlight Archive, Nietzsche, Kafka, Dostoevsky, Murakami, Camus, and Blood Meridian. From there I fell in love with myths, epics, and monumental classics such as The Odyssey, The Epic of Gilgamesh, and Moby-Dick. Living inside stories and language for so long is what first led me toward writing, and eventually into content and book editing.
Trained and worked as a designer. Type, grid, hierarchy, restraint — the vocabulary I still design every interface with.
Worked as an editor—not an author—helping proofread and edit 17+ published books and many more unpublished manuscripts. Also handled freelance translation and editing for substantial, unpublished academic papers. Structure, clarity, and a very high tolerance for detail.
Building software end to end and putting AI into the places that genuinely benefit from it. The part everything else was preparation for.
05 / THE REST OF IT
I learned graphic design professionally before I shipped a single product. It means I don't hand off to a designer and I don't guess at spacing, hierarchy or type. The interface is designed, then built, by the same person — which removes an entire translation layer from the process.
This site is the argument. Nothing on it is a template.
As a professional English book editor for several firms, I helped proofread and edit more than seventeen published books, plus many more unpublished manuscripts. I was their editor, not their author. Separately, I took on freelance translation and editing work for substantial academic papers. Those papers were private client work and were not published.
That work teaches something no course does: how to hold a stranger's entire structure in your head, find the one load-bearing flaw, and fix it without breaking their voice. It is code review with higher stakes and much worse error messages — and it is why my documentation, naming and API surfaces read like someone meant them.
I treat a language model the way I treat a compiler: I know what it's good at, where it silently degrades, and how to shape a problem so the output is something I'd actually ship.
That means I build AI into products where it earns its place, and leave it out where it doesn't — which turns out to be the rarer skill. I move fast with these tools without losing the ability to explain every line that ships.
Someone who can take a product from blank canvas to shipped — the design, the build, the copy, and the AI layer — without needing three specialists in the loop, and who can talk to your users in five languages while doing it.
Hiring, contracting, or just want to argue about whether a language model belongs in your product — all three are welcome.