Software developer |🦮 Dog Lover || Building Solutions using Web technology
Nairobi, Kenya
Joined January 2020
- Tweets2.2K
- Following1.3K
- Followers647
- Likes26.1K
Pinned Tweet
I used to develop Ms Access management systems after high school, wrote a couple of VBA script this made feel legendary. I was bored on how my systems worked locally, I wanted it to accessed globally that's how I got into web development.
Complex Falcon 𓅃 retweeted
The only programmers who are really in trouble with the competition from artificial intelligence are the ones who insist the world today isn't all that different from the one we lived in last year.
Embrace the paradigm shift or perish.
(This has always been true.)
I just published You dont have to Queue to be Served medium.com/p/you-dont-have-t… #Queue #messages #producers #brokers
Complex Falcon 𓅃 retweeted
Imagine spilling coffee on it and just fixing the stain with ‘Format Cells → White’
👑
The latest 𝕏 algorithm has been published to GitHub
github.com/xai-org/x-algorit…
Complex Falcon 𓅃 retweeted
.@Safaricom_Care @SafaricomPLC
should pay for this kind of disruption. You’ve got to admire the little to no regard Safaricom has for its customers. What nonsense is this exactly? What are those of us in the diaspora supposed to do exactly?
Dear @SafaricomPLC @Safaricom_Care this is utmost inconvenience for users of Mpesa outside the country.
You have logged out all of us and the only way to login again is to have the Safaricom network connected, which doesn’t work on roaming. One had to wait to come to Ke so they can activate the app.
Now tell me, what do you want me to do with the money in my mpesa? How will i continue using it?? Huge disappointment!
To some extent, I feel like this is a User adaptation issue ,, :)) The engineering team could have considered building something similar to the previous M-Pesa App and updated it gradually.
@SafaricomPLCim I’m very sorry to say this, but your new M-pesa app is extremely horrible…. simple put.
Please return the old format, the new version is not legible or user friendly at all.
It’s like a mess of rainbow colors and too much going on, on one app.
Text front, too small… it’s just horrible.
@Safaricom_Care
#Mpesa
Complex Falcon 𓅃 retweeted
INSTANT PAYMENT NOTIFICATIONS (IPN) API by KCB
Kenyan fintech developers - if you've built Customer To Business (C2B) on Safaricom's Daraja, you already understand this pattern. 👇
KCB Buni has an equivalent: the Instant Payment Notifications (IPN) API. A service used to send real-time notifications about payment-related events. It allows businesses or service providers to be informed immediately when certain financial transactions occur, enabling automated processing and updates.
Same concept - your server receives a real-time POST payload the moment a payment hits your account/till. Different rail, direct bank-side execution.
Here's what that looks like in practice:
Safaricom C2B (Daraja):
→ Customer pays to a paybill/till number
→ Safaricom sends a confirmation callback to your endpoint
→ You parse, validate, update your records
KCB Buni IPN:
→ Customer makes payments to a KCB account, Vooma tills or to a Lipa Na KCB till via KCB STK Push or bank transfer
→ KCB sends an IPN payload to your registered endpoint
→ You parse, validate, update your records
The implementation pattern is nearly identical. If you've done one, you can do the other.
Why it matters for your stack:
- Direct bank integration for merchants already banking with KCB Bank Group
- Direct bank integration reduces middleware dependency
- KCB IPN pairs cleanly with their STK Push - one API, full transaction lifecycle
I recently implemented this for a merchant banking with KCB Bank Group. The IPN endpoint handled real-time confirmation, deduplication, and ledger updates - same logic we'd normally wire for Daraja C2B.
If you're building payment infrastructure in Kenya, this is worth knowing.
If you need help integrating KCB Buni IPN, STK Push, or any payment gateway into your product - feel free to reach out. Happy to help.
Explore the KCB Buni API👉👉: sandbox.buni.kcbgroup.com/de…
I’m fed up with emojis on web pages and in web apps.
After vibe coding, at least replace them with proper icons, for God’s sake, unless it's a reaction.
Just built a threaded chat system for a project! Had to dive deep into the database tree structures for nested conversations. Check out these concepts.
- Adjacency List - Simple but needs recursive queries
- Materialized Path - Fast reads, complex writes
- Nested Set - Lightning reads, painful inserts
- Closure Table - Very flexible, extra joins.
I went with Adjacency List + cached depth + path using the ancestry gem. Perfect balance of simplicity and performance for our chat threads!
#RubyOnRails #Database #Programming #WebDev
Complex Falcon 𓅃 retweeted
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.