I started writing code because I wanted to build things — not because I had a five-year plan or a LinkedIn post about it. I just wanted to make stuff that worked. That instinct stuck.
My first name is actually spelled Fawas — but I've always preferred it with the Z. I'm currently a Computer Science student at the National Open University of Nigeria, studying while shipping real products. Most of what I know didn't come from a lecture — it came from doing something wrong, staring at it until I understood why, and then doing it again properly. I've found that the gap between understanding something in theory and actually building it is where most of the real learning happens. That gap is also where it gets interesting.
I've been building professionally since 2022 — across an education platform, a software agency, and a handful of personal projects that range from useful to deeply unnecessary. The unnecessary ones are usually where I learn the most. I gravitate towards frontend because it sits at the intersection of engineering and experience: the code has to work, but it also has to feel right. Getting both at the same time is harder than it looks and more satisfying than most things I know.
Chess
Chess takes up a serious amount of my mental bandwidth — and I mean that in the best possible way. I've spent more time studying openings, endgames, and positional ideas than I'd like to put in writing. There's something about the game that maps cleanly onto how I think about problems in general: you rarely win by playing the best move in isolation, you win by setting up the board so the right move becomes obvious three moves from now. I try to bring that same logic to software — architecture decisions, component design, the moments where it's tempting to hack something together just to make the test pass.
Chess also taught me that losing is most of the job. You can play a near-perfect game and still lose because of one decision in move 22 that you didn't fully think through. That's a useful thing to internalize when you're writing software. The bugs are coming. The question is whether you set things up so that when they arrive, you know where to look.
Music
Music is always on. There's probably a pattern in there if you looked hard enough. My GitHub contribution graph and my listening history are essentially the same document presented differently. You can also reach out if you need a playlist recommendation
Everything else
Outside of those two, I'm drawn to things that are well-made. Interfaces that get out of your way. Tools that do exactly one thing and do it perfectly. Writing that doesn't waste your time. Systems that are honest about what they are. I notice when those things are missing, and I find it hard to leave them broken when I can fix them.
I'm based in Lagos, open to remote work, and currently building. If something I've made or said is interesting to you, I'm easy to reach.