About Me
I've always liked making things and figuring things out for myself. I didn't grow up around labs or tools, and the people around me couldn't usually explain how things actually worked. For a long time I used that as a reason to hold back. What changed was realising I was never going to start under perfect conditions, and that the work gets clearer when you're willing to try something, get it wrong, and come back with better questions. Most of what I know now came from building things and getting them wrong first.
Coming from an African context, where access to equipment and resources isn't always easy, I think about how to make better use of what's already available. A cheap part, a basic method, or a useful insight is often enough to begin. That mindset shapes most of what I build and the systems I spend time trying to understand. I put this site together to share some of that process and connect with people who'd rather get on with building practical things than wait for the perfect setup.
How I Learn
I learn best when I can get close to the thing itself: see it, visualise it, or put it in my own words before diving in. When I start something new, I try to break it down into the simplest, most useful questions. What problem are we actually trying to solve? What do we already have? What's not working? What can we test first? Even a rough first version usually teaches me something, and a small test often turns up lessons that go beyond the specific project. That's the part of engineering and the scientific method I genuinely enjoy.
I also learn a lot from people. A good conversation can surface assumptions I didn't realise I was making, or hand me a different angle on a problem entirely. My goal is usually to make the next step clearer than the last, and to leave something behind: a sketch, a test, a working prototype, that's practical enough for someone else to pick up, question, or improve.