Rust Backend Developer & Cloud Engineer | Rustacean 🦀
Lagos, Nigeria
Joined September 2011
- Tweets10.3K
- Following448
- Followers1.1K
- Likes42.3K
Pinned Tweet
"Teaching is a humbling and deeply educational experience, and I cannot recommend it enough!"
--Jon Gjengset.
Thank you, Jon, for giving your time, expertise, and energy to write a masterclass on Idiomatic Rust. I've always admired your knack for teaching and hope to do the same.
I just finished studying Rust for Rustaceans by @jonhoo.
After studying the Rust Book, like @dtolnay said in the preface, I noticed a knowledge gap between concepts explored in TRPL (The Rust Programming Language) Book (a.k.a., the Rust Book) and terminology in the std library and Rust Reference. I wanted to close that gap, to truly understand, because I've come to LOVE Rust. I wanted to leave no stone unturned. I found the best 2nd book after the Rust Book (goes without saying, I highly recommend).
As advised, in Chapter 13, Jon, I'll learn by teaching too. In the coming days, I'll share blog posts and hopefully hold live sessions where I debunk the myth that "Rust is too hard." Chipping at topics bit by bit.
It used to be that if you wanted to learn the inner workings of computer programming that'd tell you to learn C. Today, I'd tell you to learn Rust. Rust teaches you to appreciate the power you wield when you write, build and run a computer program. Yes, it is complex, but "complex is better than complicated." It might take some getting used to, yes, but with time and focus anyone can master the language and that's what I hope to do.
PS. Thank you @OReillyMedia for access to a plethora of golden technical resources. Thank you @timoreilly. That's two Rust books in 3 months! Grateful.
I've finished studying the Rust Book 🦀 (also known as The Rust Programming Language Book) by Carol Nichols and Steve Klabnik. Precisely, the interactive version by C.S. Brown University, (also known as the Rust Book experiment) which is available online for free via the link: rust-book.cs.brown.edu/exper…
Allwell retweeted
A former member of a secret society says sex drive and wealth come from the same place. The hunger that keeps people up at night, he says, is the same hunger that builds empires.
The man is Kevin Trudeau, and he says it plainly: those who create a lot in life have a large sexual drive as well. Sexual energy is creative energy, and making money is just another way to spend it, the same as painting, cooking or building anything at all.
What separates the builders from everyone else is what they do with that energy before it’s gone.
Trudeau calls it transmutation. Take a strong desire and push it into work, a business or a deal, and that work suddenly has “a lot of juice behind it.” Things move faster and come to fruition stronger. He claims the super wealthy don’t rely on business plans at all, but on rituals like this one, passed down in the secret society he says he was part of. Of all the rituals he learned there, this was the one he was most excited to practice.
The idea isn’t new. In 1937, Napoleon Hill gave a whole chapter of Think and Grow Rich to “sex transmutation,” and generations of salesmen have read it since. Trudeau adds a warning Hill mostly skipped: with very powerful people, the same drive can turn into a slippery slope.
The fuel is the same, and the only question is whether it ends up in a bedroom or a bank account.
So the next time it’s 2 AM and you’re too wired to sleep, open the laptop instead of the apps, and save this post for that night.
Allwell retweeted
Bamboo brought more cash for IPO of Dangote refinery more than any 🇳🇬 financial firm, now I understand why their app had some down time
Allwell retweeted
I laugh when people criticize @investbamboo here, while incumbents in the industry are terrified of Bamboo's grip on the younger, future market. In one year, 85% of all new customers on the NGX came from them alone. They are the Opay of Nigerian investing.
I was on the board of an older competitor then, and I sounded the warning. I used Bamboo, not the company's product, because it was better and simpler. @investbamboo may have product and pricing issues, but they have cornered a chunk of the market because people trust them. Their brand has matured quickly.
They are locking up a particular demographic because older brokerages with a brand advantage were slow and refused to update their tech because of internal politics. You would typically use what your friends already use. Investing is not like payments; it is closer to banking.
Well said.
Nigerian freelancers, don’t let anybody gaslight you into believing your location should determine how much you earn.
I worked on an AI video generation project alongside other freelancers from the US. We were all paid $250 for every 40-second video we created.
We created several videos, and I received the same rate as freelancers living in California.
Nobody told me my rate should be lower because I live in Nigeria.
Some months ago, I also worked with Higgsfield on their MCP campaign. I was paid the same rate as other creators in the US. Same thing too when I worked with Kittl ( Germany )
So when people tell you international clients will always pay you less or according to your country minimum wage, I need you to understand that this isn’t always true.
Your location is not a discount code for clients to use against you.
Yes, the market matters. Your skills matter. Your experience and the quality of your work matter.
But don’t let anybody convince you that you must accept peanuts because you’re in Nigeria, especially when you’re delivering the same quality of work as someone in America.
Negotiate based on the value of your work and don’t allow them to trick you oh.
Allwell retweeted
Nigerian freelancers, don’t let anybody gaslight you into believing your location should determine how much you earn.
I worked on an AI video generation project alongside other freelancers from the US. We were all paid $250 for every 40-second video we created.
We created several videos, and I received the same rate as freelancers living in California.
Nobody told me my rate should be lower because I live in Nigeria.
Some months ago, I also worked with Higgsfield on their MCP campaign. I was paid the same rate as other creators in the US. Same thing too when I worked with Kittl ( Germany )
So when people tell you international clients will always pay you less or according to your country minimum wage, I need you to understand that this isn’t always true.
Your location is not a discount code for clients to use against you.
Yes, the market matters. Your skills matter. Your experience and the quality of your work matter.
But don’t let anybody convince you that you must accept peanuts because you’re in Nigeria, especially when you’re delivering the same quality of work as someone in America.
Negotiate based on the value of your work and don’t allow them to trick you oh.
Allwell retweeted
They said African languages were too fragmented, too complex and too commercially insignificant to build advanced AI for.
We disagreed. So we built it.
64 languages. 166 voices. 3 billion parameters. ONE model.
Today, we are unveiling STORM-Ensemble 3.0, the most capable multilingual speech synthesis model we have built at PlotWeaver.
From Yorùbá, Igbo, Hausa and Nigerian Pidgin to Swahili, Amharic, Wolof, Zulu, Xhosa and dozens more, STORM-Ensemble 3.0 generates speech across 64 languages, with 166 distinct speaker voices.
Every voice you hear is generated by our model, not a prerecorded sample.
But the real breakthrough isn't the numbers.
It's what becomes possible when this technology is in the hands of people who can build with it.
-African filmmakers distributing stories across languages.
-Banks and telcos serving customers in their mother tongues.
-Education platforms reaching more children.
-Developers building voice AI products without starting from scratch.
We are not building AI for African languages simply to prove it can be done. We are building the infrastructure to make our languages commercially viable at global scale.
Next week, I will be speaking at the Commonwealth Business Forum in Antigua about unlocking the Commonwealth's creative potential. This launch is a practical demonstration of that ambition.
Africa must not simply consume the future of AI. We must build, own and shape the infrastructure that powers it.
Watch the video. Listen to the voices. Imagine what's possible.
Introducing STORM-Ensemble 3.0.
PlotWeaver. Build Once. Speak Every Language.
#PlotWeaver #STORMEnsemble #VoiceAI #AfricanLanguages
Allwell retweeted
🦀 🤌 Beautiful Rust v1.5.0 is out
If you don't know what this is, it’s a free set of skills that teaches AI coding agents to write better Rust.
I created this six days ago and it went kinda wild, now has over 1,000 stars on Github, which is a big deal for little ol' me 🥹
Here's what's new in this version 🔽
- it now knows Bevy, the Rust game engine. It catches game bugs that look fine but crash or misbehave once the game runs.
- every code example in the skills is now tested automatically. The AI copies these examples into real projects, so a broken one gets caught before anyone sees it.
Three people helped make this release. Thanks to Trevin, Dylan, and millionart for the Bevy idea.
Now live on Github:
github.com/morganlinton/Beau…
Allwell retweeted
Rust vs Go: both have real advantages, and the trade-off is sharper than it looks.
Go is the simple one. It's easy to learn, doesn't carry many language features, and compiles fast. Rust is on the complex side: the spec keeps growing, and compiling is slow. Day to day, Go is simpler in most cases. You don't fight a complex type system, and any function can run as a goroutine.
Concurrency is where the two really split. There are two families. Go is one: lightweight threads, start any function in a goroutine, done. The other family is sync vs async, and Rust, Python and JavaScript all live there. That's where complexity creeps in. Functions have colors. Rust and Python give you two worlds, and you must never call a blocking function from an async one. JavaScript is simpler because it's a single world. Sync vs async forces you to clearly define what blocks and what doesn't, and that's real extra complexity. The upside is performance: async generally beats goroutines.
Rust's best part is the type system. You can model a lot in it, and the more business logic you push into types, the more bugs the compiler catches before anything runs. Go's type system is not that comprehensive. One example: Go can't catch a race condition at compile time. Rust can. But the cost of that type system is compile time. Bugs caught early and slow builds are the same coin.
For AI coding, Rust becomes a double-edged sword. Code moves fast, so slow compile hurts more. But if the model expresses business logic through the type system, far more bugs get caught at compile time. Slower, but higher quality.
That's why we chose Rust for data infra. There, robustness and reliability outweigh the speed of writing code.
Allwell retweeted
its true, Anthropic really vibecoded their entire backend to Rust and none of you noticed
Anthropic rewrote its Messages API in Rust. Zero Rust devs on the team.
Claude wrote the code. Humans wrote the plan and checked old vs new matched on real traffic. CPU dropped 40-50%.
Pretty sure "never do the big rewrite" is dead advice.
@katelyn_lesse on @latentspacepod
Allwell retweeted
Funding rounds aren't milestones. It shouldn't be your goal to raise a series A. It should be your goal not to need to.
Allwell retweeted
A man who knows he’s going to win doesn't worry about when. He just keeps showing up because he knows his time will come.
Allwell retweeted
All of us at Marvel Studios are deeply saddened by the passing of Sir Patrick Stewart. Sir Patrick brought Professor Charles Xavier to life with extraordinary grace, intelligence, and humanity, defining the character for generations of fans, from "X-Men" to "Logan" to "Avengers: Doomsday." He was a singular talent, a generous collaborator, and a true gentleman. Our hearts go out to his wife Sunny, his children, his friends, and the countless fans around the world whose lives he touched with his art.
Allwell retweeted
The article is gold. my takeaways:
As a solo developer:
1. Before opening a PR, run a handful of internal skills and verification steps (tests, builds, diff reduction, end-to-end checks, UI vs design guidelines, etc.).
2. Run an AI review on every pull request using a new agent with fresh context focused on the diff.
As a team:
3. Define risk tiers and classifiers based on the change, not the author. One classifier sets the risk level; another checks whether extra approval is still required even if the tier doesn’t call for it. Some paths always need another approval (sensitive code flagged by owners, CI workflow files, etc.).
4. Ask Claude to generate a mini explainer of the change. It’s faster and more useful for understanding context than reading every line of a trivial diff.
5. With agents it’s cheap to start new work — but sometimes you shouldn’t. That’s another reason for keeping humans in the loop beyond just security and ownership.
