Skip to main content


Hey, I am Okiki Ojo (pronounced O-key-key O-jo), I’m a student studying Software Engineering at Ontario Tech University (formerly University of Ontario Institute of Technology, UOIT), previously interned as a Software Engineer at Vercel . From a very young age, I've always been interested in tech, and science. Initially, I started web development out of curiosity, eventually it became a hobby, and after many hobby projects (e.g. Open Source projects; read more in featured projects ), I thought it would be cool to offer my skills to clients who want awesome web experiences, thus here we are.

I have a passion for design and development, I'm driven to create things that function with a shine you can't resist. I'm always eager to take on a challenge, and aim to exceed in all tasks I take on. My philosophy is simple sophistication, solving complex problems with simple, efficient, and effective solutions that are sustainable, maintainable, and evolve.

Open source development (OSS), has taught me quite a lot, for one its made me truly appreciate good governance, and even better coding/documentation practices. During my adventures in OSS, I worked on many projects ranging from @okikio/animate to (learn more at featured projects ), wrote multiple blog posts and articles , I even earned a position as a maintainer on the project. All the experience gained from OSS development has been a great asset to help me grow as a developer and a person.

As part of my odessy through the OSS community, I gained experience in many technologies, Astro, Javascript, Typescript, CSS/SASS, HTML, Pug, Node.js, Deno, Oak.js, Fastify, Pjax, React, Next.js, Solid.js, Svelte, C#, C/C++, and more… In general I've found learning a technology with a specfic need in mind does wonders for learning techniques, technologies and topics. Thus I prefer to learn skills as I need them, so I can focus on finding solutions to problems instead of trying to implement new technologies for the sake of implementing them.


When developing projects and solutions I first aim to understand the needs and goals of the project, I then determine the best approach to build a solution and what type of solution. There are four parts to my method, speed, efficiency, ease-of-use, and impact.


How quickly do the stakeholders wants their solutions implemented, and accordingly what tools will ensure high levels of speed.


Making sure not to waste resources, time and/or effort, so stakeholders can get the most out of the final product.


The solution needs to be easy to use, easy enough so stakeholders can use the solution without breaking a sweat.


The solution should leave an impact, an impact large enough that stakeholders understand the what, where, why, and how's clearly.

Featured Projects.