Jesus' baby.đ»
Living, loving & building @ForCre8iveGirls (Mentorship, Members, across 15+ countries).
Scratching the nerdiest of my itches per time.
Microservices is the software industryâs most successful confidence scam. It convinces small teams that they are âthinking bigâ while systematically destroying their ability to move at all. It flatters ambition by weaponizing insecurity: if youâre not running a constellation of services, are you even a real company? Never mind that this architecture was invented to cope with organizational dysfunction at planetary scale. Now itâs being prescribed to teams that still share a Slack channel and a lunch table.
Small teams run on shared context. That is their superpower. Everyone can reason end-to-end. Everyone can change anything. Microservices vaporize that advantage on contact. They replace shared understanding with distributed ignorance. No one owns the whole anymore. Everyone owns a shard. The system becomes something that merely happens to the team, rather than something the team actively understands. This isnât sophistication. Itâs abdication.
Then comes the operational farce. Each service demands its own pipeline, secrets, alerts, metrics, dashboards, permissions, backups, and rituals of appeasement. You donât âdeployâ anymoreâyou synchronize a fleet. One bug now requires a multi-service autopsy. A feature release becomes a coordination exercise across artificial borders you invented for no reason. You didnât simplify your system. You shattered it and called the debris âarchitecture.â
Microservices also lock incompetence in amber. You are forced to define APIs before you understand your own business. Guesses become contracts. Bad ideas become permanent dependencies. Every early mistake metastasizes through the network. In a monolith, wrong thinking is corrected with a refactor. In microservices, wrong thinking becomes infrastructure. You donât just regret itâyou host it, version it, and monitor it.
The claim that monoliths donât scale is one of the dumbest lies in modern engineering folklore. What doesnât scale is chaos. What doesnât scale is process cosplay. What doesnât scale is pretending youâre Netflix while shipping a glorified CRUD app. Monoliths scale just fine when teams have discipline, tests, and restraint. But restraint isnât fashionable, and boring doesnât make conference talks.
Microservices for small teams is not a technical mistakeâit is a philosophical failure. It announces, loudly, that the team does not trust itself to understand its own system. It replaces accountability with protocol and momentum with middleware. You donât get âfuture proofing.â You get permanent drag. And by the time you finally earn the scale that might justify this circus, your speed, your clarity, and your product instincts will already be gone.
I've spent the last two years studying consumer AI trends.
Yesterday, our team @a16z published our latest report on the top 100 AI products (by usage).
My biggest surprises - and what to learn from them âŹïž
Tems Just Dropped the Ultimate Music Mentorship Program for African Women â And Applications Close Soon!
https://t.co/uUC4jKZtVB Check it out here âïž
How the enterprising Engineers at African fintechs and payment companies build the infrastructure to move money around, even when there's no internet.
Find out more in @FinanceinAF's latest engineering deep dive.
The comments
Anthropic announced they've activated "Al Safety Level 3 Protections" for their latest model. What does this mean, and why does it matter?
Let me share my perspective as OpenAl's former lead for dangerous capabilities testing. (Thread)
If youâre building payments in Nigeria, youâre building on NIBSSâwhether you know it or not.
We @FinanceinAF did a technical breakdown for the pros building payments products in Nigeria.
@gbemi_lolade spoke to engineering and product leads who helped us break down everything from APIs and switching logic, and JSON code samples for key interactions.
Full breakdown in the comments
When Iâm not speaking about my faith or ranting about F1, Iâm really into policy.
Iâve recently started @Parlicy101 where I briefly explain parliament & policy in the simplest of terms so everyone can understand the âcomplexâ world & words of government.
Please follow. â€ïž
God abeg. I'm stressed.
OpenAI and urging the U.S. government to allow AI companies train on copyrighted material under fair use. đ€
https://t.co/eZYjjEJpVy