what i’m about to write reminds me of this piece i wrote in 2016.

it’s year end, and amidst the flurry of activities and moments of reflection, some bibliophiles took to their socials to share how much they’ve read over the course of the year. unsurprisingly, the non-readers jumped in to dispute certain claims without basis while high-fiving themselves with uninformed takes on reading.

i condensed my read of what was going on into this tweet. it was an observation about how unprovoked reactions often reveal insecurities. if anything, a more accurate articulation of it could have said, “your real problem might be with yourself…”. i followed it up by acknowledging my own limitations.

someone replied. their argument is a time management concern. it’s a pseudo-anonymous handle i have come across a few times. previous context indicates someone who is online more often than not. precious...

growing up, i only paid attention to proper casing when creating documents or writing an email. for instant messaging, i used all lowercase. then smartphones took off and autocapitalization made it something to not worry about… until i realized i probably didn’t want to give away what device i’m on when chatting with people. why should they rightfully guess i’m on my laptop when i text in lowercase when i can make things ambiguous by always texting in lowercase?

so i turned off autocapitalization.

over time, a framework emerged to tell my lowercase writing apart from appropriately cased ones. the former signified a stream-of-consciousness articulation, while the latter implied formal comms.

i plan to publish more in the new year, and one way i intend on making it less of an aspiration is to occasionally share slightly longer form versions of the kind of thoughts that inform my...

on june 9 2020, i cut my locs. it was peak lockdown season and people worldwide were forced to introspect and make big life decisions. for a lot of people, this meant cutting their hair, for others, it was learning to make banana bread, but i digress.

my loc journey started in 2010 - about two years before i officially went to the salon to get it done properly. i had stopped using my comb and wore caps most of the time. over time, i had locs free-forming at the back of my head, and after rocking the look for a bit, i had it done right. i started out with interlocking, but i quickly switched to palm rolling.

when paystack got accepted into ycombinator in 2015, my cofounder and i moved to the bay area for a few months. i no longer had access to my usual loctitian and finding one in white people country wasn’t exactly the most straightforward thing to do. since my locs were borne out of...

Every Sunday, you’ll likely find my friend Tolu at brunch somewhere. She might be at Eric Kayser alone, catching up with a former colleague at Pitstop, or hosting close-knit friends at her apartment in Victoria Island. It was no surprise that when she came to spend the weekend at mine sometime in February 2021, she was itching for us to go out to brunch on Sunday. Another friend of mine was around at the time, and we collectively agreed to spend our Sunday morning at Orchid Bistro, Ikeja GRA.

We spent the time talking about anything and everything, catching up on our individual travails, and running commentary on the food. A colleague of mine was scheduled to visit me that day, so she joined us at Orchid Bistro instead. I appreciated how chill and relaxing the outing went and commented on how I’d love to experience it more often. The only problem was that regularly leaving my house...

My first memorable experience with a well-designed and functional network was in 2009 at the African University of Science and Technology (Abuja). My friend, @bigbrovar, designed and built the network, and was its sole administrator.

Speaking of the network being very functional, I am referring to the breadth of services running within the network that needed to be kept alive. The university assigned laptops to students. These laptops ran a custom Linux distro (also put together by my friend) and, at some point, loaded the user’s home directory off the network, making it possible for students to login to their desktop profile on any school-issued computer they can find. There was also some caching setup in place such that any HTTP download is done once over the internet and subsequently on the network, dramatically cutting down bandwidth requirements for system updates, etc. I used to...

My earliest participation in distributed computing systems was installing SETI@home on my computer in the early 2000s. Short for “search for extraterrestrial intelligence”, SETI@home at the time was essentially a screensaver that leveraged idle computing power to analyze data captured from the Arecibo Telescope to detect signs of intelligent life outside our planet.

The project failed to detect evidence of life outside earth. However, it proved that it is possible to leverage volunteer computers worldwide for scientific research, giving researchers more options beyond buying time on specialized supercomputers for their work. SETI@home also evolved from a single-purpose screensaver into the Berkeley Open Infrastructure for Network Computing (BOINC). This system matched volunteer computers with various projects that could use the spare compute.

Enter Folding@home

Like SETI@home...

Ever since I had my Twitter handle changed to @0x back in January of 2010, I have been no stranger to attempts at stealing the account off me. First, it was seemingly lame password reset attempts - I got the emails, and simply ignored them, and then it escalated to straight up demands to surrender the address via subtle threats in my DMs.

Sometime in 2018, someone succeeded in breaching my old and abandoned yahoo email account and then emailed me from the address, asking me to change my Twitter password to a specific text, along with what to set the new email address on the account to. I didn’t respond - he later reached out via DM threatening to leak compromising pictures he had in his possession from the breach.

I didn’t think I had anything to be worried about. My security sense is definitely not fort knox level but at least, I had all the bases covered - I use a password...

It’s amazing how I have managed to garner a reputation for always being angry in certain social circles. Particularly on Radar, I have been referred to as a terrorist, someone who prides in mindlessly bullshitting (or attacking) other people’s ideas, amongst other things. I have in not so many words been blamed for some people abstaining from sharing their thoughts or products for fear of being judged. Some have even gone as far as looking forward to the failure of things I lay my hands on just so they can have a good laugh - I know this because this sentiment has been expressed to people who happen to be friends of mine.

Wow.

Sometime in 2009, I wrote a casual blog post titled Celebrating Mediocrity which basically expressed my disgust with the low ambitions of most web services created by Nigerians. This sentiment hasn’t changed much. What has become even stronger is how much people...

So I had been home for at least 7 days straight now, besides going out for the obligatory Tuesday evening dinner. Now this can be considered awesome. Working from home with only three destinations to really be bothered about - the bed, the desk, and the kitchen. Okay, maybe occasional trips to the bathroom. However, things can get a little awry quickly. Like running mad from all the monotony. It doesn’t help matters that I live in a secluded part of town.

A couple of weeks back, while in a little conversation with the lady driving the uber I was in, I asked about what fun stuff to do in town and she mentioned this outdoor mall in San Jose with a number of bars and outdoor happenings in the evenings. This sounded great. Afterall, It’s high time I started making friends around here. Ope and I decided to head there last night. The plan was simple - relax, have fun, and knock ourselves out...

As a developer, the most exciting moment about your product can easily be when people start making use of that shiny new code you pushed, and everything hums along just fine. Or not. For some reason, I tend to prefer the latter, because you see the problems right away, and get to work fixing them which eventually culminates in that additional sense of pride in your work.

We promised the world we would move Paystack to public beta back in December. As a matter of fact, we raced towards making this happen between December 7 and 11. Rhyme not intended. These were nights without sleep for me, well partly because my clock also hadn’t fully adjusted to Nigerian time as I found myself sleeping more between the hours of 11am and 6pm. Then the slow downs began. It was like finishing 98% of the work, and then taking your sweet time to do the remaining 2%. There was one excuse or the other for not...