Forged in Grief: How Tragedy Turned Me Into a Systems Architect

I watched television for the first time at age twelve. I got my first mobile phone at sixteen—only for it to be stolen weeks later. Where I grew up in Nigeria, owning a laptop was enough to make you a suspect to the local authorities, not a student trying to build a future.

I did not grow up with a safety net, startup capital, or high-profile industry connections. I had to learn how to survive, and eventually, how to build.

The Turning Point

In 2023, during my final year of Agricultural and Environmental Engineering at the Federal University of Technology, Akure (FUTA), my world shattered. My father was killed in a fatal motor accident. My mother was hospitalized with severe injuries from the same crash.

Overnight, I was thrust into being the primary anchor and provider for my family at just 22 years old. Staring at MATLAB code in the computer lab and coming home to a grieving household, I had a choice: let the weight of the grief crush me, or channel that pressure into focus.

I chose focus. I taught myself everything I could about modern API integrations, workflow architectures, database management, and large language models. I freelanced to survive.

Moving Beyond Chatbots

Most people think of AI as simple chatbots. They write standard prompt wrappers that output generic replies. But in my freelancing, I quickly realized that businesses do not need toys—they need systems.

I started designing robust pipelines that eliminated manual data entry, validated leads in real-time, managed database race conditions, and routed voice calls automatically.

Today, I run my own consultancy, Israel O. Dare / Izzytechub, and I am rated as a Top Rated Plus talent on Upwork, placing me in the top 3% of freelancers globally. I construct systems that process hundreds of thousands of dollars on autopilot.

The Ideology: Bring Me the Hard Stuff

My engineering background taught me to think in terms of inputs, outputs, bottlenecks, and feedback loops. Whether optimizing the thermodynamics of agricultural storage or configuring pgvector databases for document retrieval, the core logic is the same: eliminate friction, guarantee data integrity, and build for scale.

Easy work bores me. The systems that others say cannot be automated are the ones I want to build.

If you have a complex operational workflow that keeps breaking, or a customer bottleneck that wastes your team's hours, let's talk. I build things that work.