Software Engineer who loves building cool stuff.
Hi, I'm Ayokunumi Faseesin. I build high-performance web and mobile applications. I design clean systems, audit logic, and ship robust software at speed.
Recent Work
I love crafting beautiful frontend interfaces, but I'm just as comfortable diving into backend systems, headless CMS setups, or building custom Shopify and WordPress solutions when your project needs it!
My Stance on Engineering + AI
I started using AI tools seriously back in early 2024, moving between GPT, Claude, and DeepSeek depending on what I needed that day. At first it felt like a shortcut. Now it's just how I work. I don't see AI as something coming for my job. I see it more like a very fast, very well-read collaborator who has no idea what I'm actually trying to build unless I tell it properly. So that's where most of my effort goes: giving it real context, the actual constraints of the project, not just a vague prompt and hoping for magic. The part people skip, and the part I care about most, is what happens after the model gives me something. I read it line by line. I test it. I question it the way I'd question a junior dev's PR, because that's basically what it is. AI gets me to a first draft fast. Getting it right is still on me.
Client Reviews
Don't just take my word for it. Here is what people I've worked with have to say about the process and the final results.
Frequently Asked Questions
Quick answers to common questions about timelines, project updates, and post-launch support.
What is your typical process for a new project?[+]
First, I get clear on what you're actually trying to solve, not just the feature list, but the real problem behind it. From there I sketch out the data model and API structure before writing any UI, since getting that wrong early is what causes rewrites later. I build in stages you can see and click through, not a single big reveal at the end.
Do you use AI tools in your development process?[+]
Yes, daily, and I don't hide that. I use it to move faster on boilerplate, explore approaches, and catch things I might miss. What I don't do is ship what it gives me without reading every line, testing it, and treating it the way I'd treat a junior dev's pull request. The judgment is still mine.
What happens if I need changes after the project is launched?[+]
There's a short warranty window for bug fixes and small tweaks, no charge. Past that, if you need ongoing feature work, I work either hourly or on a monthly retainer, whichever matches how steady the work is.