Gm Solana

We are outside at SEZ Dubai, attending my first ever life solana event @SuperteamAE and it's sure gonna be a banger 😎, thanks to @Harri_obi and @afscott for making this possible

The youths, “leaders of tomorrow,” but they don chop wetin dey tomorrow. 😕😒 Now they’re giving us tribalism to fight over. Mumu people. 🤦‍♂️🤮

The @excalidraw mcp is sick.

Have it live draw explanations (with pencil sounds and all) then pop open to the app and make your own changes.

Learning with ai is so fun. (Also, don't stop learning, your brain is too valuable)

I made a video about what Seyi's father and the APC have done to Nigeria

ive been leveraging ai to teach me topics in ways i like to learn

built a memory simulator: pick the hardware, OS (Linux, macOS, Windows) and apps, then watch what happens when you run out of RAM

here: an 11 GB game on a 16 GB machine pushing Photoshop and Slack's idle memory out to swap

I won't be surprised if my leak shows up on this page 😳

Bro, who are your sources? 😂

Happy New Month, everyone!

May October bring us massive joy, countless blessings, and beautiful moments. ✨️

She wants to slay so bad

What a bad bunny 😂😂

Rust has one serialization library that is Serde. Over the years I collected a bucket list of all the things that I do not enjoy about it. Finally did something about it and finished Deser. Here is a small summary of the why, what and how: lucumr.pocoo.org/2026/9/29/dese…

I want whatever this Cloudflare team is taking. These guys ship like shooters 😤

I made a video about this but had to delete it. Many of these people come with immense arrogance rather than openness to learn.

It's sickening. Everybody wants to prove they know it all by putting the other person down. Chill bro, you don't work at Jane Street, on flight control systems, or at Google or Cloudflare.

It's frustrating to see people without an open mind to learning and improving.

I think continuous profiling should become a default part of observability in the AI coding era.

AI can generate a lot of correct code very quickly, but correct code is not always efficient code.

An agent might choose an unnecessarily heavy library, allocate too much memory, use a poor algorithm, or simply implement something in a way that costs far more CPU than necessary.

Metrics can tell you that CPU usage or latency is getting worse. A flame graph can show you where the program is actually spending its time.

From there, you can inspect the hot paths, review the implementation manually, research better approaches, replace inefficient libraries, or use an AI agent to investigate possible optimizations.

As AI makes writing code cheaper measuring the actual performance of that code becomes even more important.

Send + Sync.

Send — a type can be safely transferred to another thread.

Sync — a type can be safely shared between threads through references.

Has to be sendryx.com.

Building a stablecoin-based payment platform is no joke. You have to think about a million different ways things can go wrong, from security and transaction integrity to system failures, edge cases, reliability, and handling money safely.

Building Sendryx has forced me to go much deeper into systems design, backend architecture, security, distributed systems, and blockchain infrastructure. And the interesting part is, I’m still learning and relearning as we grow.

It’s probably the project that has challenged me the most technically, and that’s exactly why I’m so proud of it.

You are definitely not alone, funny enough this time last year I can't understand shit in Rust now i see myself buried in any Rust's codebase for hours 😇

Y’all do not realize how many codes ancient Igbo people were cracking? Y'all are just learning this? Even when it came to mental health, they were developing approaches that, in some ways, resemble things we recognize in modern mental healthcare even though their understanding of why mental illness occurred was completely different.

The day I started researching precolonial Igbo approaches to mental illness, my mouth was left open. Yes, many conditions were interpreted through a spiritual lens and attributed to gods, spirits, or supernatural forces. But some of the actual practices used to help people were surprisingly familiar.

They had practices resembling talk therapy, art-based therapy, music-based interventions, medicinal herbs, and even designated places where people who were too mentally unstable to remain safely with their families could be cared for. Obviously, they didn’t call these things “psychotherapy,” “art therapy,” or “psychiatric facilities.” Those are modern terms. But the parallels are fascinating.

What makes it even more interesting is that these practices developed within their own spiritual framework. What could resemble talk therapy, for example, was explained to me as helping guide a distressed person away from harmful or irrational thoughts and toward different ways of thinking and behaving. One historian I spoke with described parts of the process to me, and I remember thinking, “Hold on… this sounds almost like a distant cousin of CBT.” 😂 Not CBT in the modern clinical sense, obviously, but the idea of challenging thoughts and trying to change behavior through changes in thinking sounded remarkably familiar.

Other practices involved having people express or depict what they were experiencing so the healer could interpret what spiritual force was believed to be involved and determine the appropriate intervention. Their explanation for why it worked may have been completely different from modern day knowledge, but some of the methods themselves are fascinating to examine through a modern psychological lens.

That is what blows my mind. They did not have modern psychiatry, neuroscience, diagnostic manuals, or our current understanding of psychopathology. They were working within the knowledge system available to them (gods, spirits, etc), yet they still developed complex ways of caring for people experiencing psychological distress.

I swear, every time I become interested in some aspect of precolonial Igbo society and start digging into it, I leave flabbergasted. It makes me wonder how these indigenous systems of knowledge might have continued developing if colonialism had not disrupted, suppressed, and reshaped so much of Igbo society.

When I tell y’all I’m proud of ancient Igbo people, you really don’t understand. The more I research, the more fascinated I become. They were cracking codes despite having limited knowledge.

This is Beautiful 😍

If you're wondering what this actually means, here's a simple way to look at it.

Normally, you'd create a vector like this:

let mut numbers = Vec::new();

numbers.push(10);
numbers.push(20);
numbers.push(30);

You don't specify an allocator. Rust uses the default/global allocation mechanism.

With the Allocator API, you can conceptually do:

let mut numbers = Vec::new_in(my_allocator);

numbers.push(10);
numbers.push(20);
numbers.push(30);

The difference is that you're explicitly telling the collection which allocator it should use.

That might not look like much, but it opens up some interesting possibilities.

You could have different allocation strategies for different workloads:

Normal Vec

Vec
↓
Default allocator
↓
Memory

versus:

Allocator-aware Vec

Vec<T, A>
↓
Your chosen allocator
↓
Memory

For example, an application creating lots of short-lived objects might benefit from an arena-style allocator.

Another workload might benefit from a memory pool where previously allocated blocks can be reused.

The important part is that the Allocator API itself isn't an arena allocator or a memory pool.

It's a standard interface that allows collections like "Vec" to work with different allocation strategies.

And this isn't limited to "Vec". The idea applies to allocator-aware collection types and other allocation-based abstractions.

So instead of memory allocation being something completely hidden underneath your collections, Rust is giving systems programmers a more standardized way to control that layer.

If you're learning Rust, this is worth understanding beyond just:

"Vec<T, A>"

Because it gets you into the deeper parts of systems programming:

heap → allocation → allocator → memory layout → performance

That's where Rust gets really interesting.

"The database is now completely empty, reset and waiting for new data"

Your papa 😩😭

Lol, something similar is exactly what made me switch to OpenCode. The fact that I didn’t even have that $20 to spare on Claude, yet I still managed to waste it, pushed me to start exploring OpenCode.

I went down the rabbit hole and even watched tutorials. Mehn, I’ve been using different models there and haven’t paid a dime. The tasks I’ve been working on recently aren’t that heavy, and the free models have actually been executing them pretty well. Models like BigPickle on OpenCode Zen have been more than sufficient for my daily workflow for now.

Claude Code can wait till I have a serious project worth spending money on 😂.

ItIt pays to serve Jesus,I speak from my heart

🙇‍♂️❤️