Uplixdev

A polished portfolio beats a perfect résumé. Let your real-world projects do the talking—show clients and employers what you can build, not just what you know. #PortfolioPower #WebDev #FrontendDeveloper #BuildInPublic #TechCareer

Every Nigerian payment app has a queue. When you hit send, your transaction doesn't go straight to the bank. It enters a queue, gets processed in order, retried on failure. The UX looks instant. The backend is not.

It’s been close to a year since I last did an interview, yet I still get lots of DMs, offers, and gigs. If you’re the shy type and don’t know how to properly pitch yourself or communicate how valuable your skill set is, getting jobs or gigs in this current tech space might honestly be difficult. Do you know how many people apply for the same role every single day?

Interviewer: Your refresh token was stolen from one device. How do you invalidate only that session without logging out every device?

@smartnakamoura Congratulations sir

7k followers in the fucking chart😭❤️🥹

@c26338275 Thank you brother

@uplixdev Big congratulations brother 🩵

Wow Made this post in October and in April this year, God did got an IPhone 12. God did💃💃

If you’re in Nigeria and your MTN data disappears faster than money in your account, you’re not crazy. 15GB weekly is now ₦6,000. Not too long ago, that same thing was around ₦2,000. 1GB now averages around ₦575. Everybody keeps shouting “telcos are thieves”. But after digging through NCC reports, MTN financials, global pricing data, and industry numbers… the reality is way more uncomfortable than that. This whole thing is deeper than people think.

Someone lost ₦100k within 24 hours of opening their very first bank account. not to armed robbers just to a phone call. here's exactly how this scam works 🧵

I don’t know but I think I have lose interest for this network provider, terrible bandwidth, can use the network to receive OTP from TikTok, can’t use it to create Apple ID for days now.

Let’s talk about System Design Interview Preparation. But first, a short story. This thread is purely educational, so kindly repost and bookmark for reference later before continuing. Now let’s read carefully.

Someone should help me be @GloWorld to improve on their bandwidth in Ogun state for days now network is bad, can’t make proper calls on WhatsApp can u imagine

@smartnakamoura Happy new month senior More blessings

Happy new month🎉 Say it back if you see this 🥳

@Akintola_steve Happy new month sir More blessings

Happy new month to you all. Good bless you all. To my mutuals too, I love you all. Btw let’s go celebrate my dad’s birthday 🎁

When building distributed systems, people don’t realize they’ve already shipped something that might give them a crazy production issue. For instance, you save data to your database, then publish an event to a message broker. Simple, right? Until it isn’t. I'll break down "Transaction Outbox Pattern" using a real-world example. With all today's Twitter gbasgbos so I'll use the same e-commerce to explain the pattern; So, imagine you’re building an e-commerce system. A customer places an order: You write the order into your database. You publish an “OrderCreated” event to Kafka (or RabbitMQ). Now here’s the problem: these two steps are NOT atomic. If your DB write succeeds but your event publish fails: 1. Your system now has an order that other services (inventory, payment, shipping) don’t even know exists. If your event publish succeeds, but your DB write fails: 2. Other services react to an order that was never actually created. This is how systems quietly corrupt themselves. And no… wrapping both in a single transaction is not possible because: 1. Your database and your message broker are two completely different systems. 2. Distributed transactions (2PC) are slow, fragile, and rarely worth the complexity. So what do you do? This is where the Transaction Outbox Pattern comes in. Instead of trying to write to the DB and publish an event at the same time, you change the flow: You write your business data (e.g., Order) In the SAME database transaction, you also write an “event record” into an outbox table Now, both operations succeed or fail together. No inconsistency. Then separately: 1. A background worker (or polling service) reads from the outbox table 2. Publishes events to your message broker 3. Marks them as processed Now your system becomes: Eventually consistent, Fault-tolerant, Retryable without duplication (if done right), Real-world example: Say you’re running a marketplace like Jumia. When an order is placed: Orders service writes to the orders table Same transaction writes to outbox table → { type: "OrderCreated", payload: {...} } Then a worker: Picks that row Publishes to Kafka Updates status → “processed” Is Kafka down? No problem, the event stays in the outbox and retries later. If your app crashes? No problem, the event is still in the DB. This pattern solves: Lost events Partial failures Inconsistent state across services It’s one of those patterns that looks like it's stressing you out until your system scales and you realize it’s the only reason things aren’t falling apart. In the next threads, I’ll show: What the traditional (broken) approach looks like visually What the outbox pattern flow looks like Why one silently fails while the other survives real-world chaos

See speed ooo

@Aje_Dynamicz Thank you sir for this goldmine

Nobody is talking about this remote skill that pays ₦300k–₦2M per project... It's not copywriting. It's not graphics. And Nigerian freelancers are sleeping on it badly. Let me explain 👇

@smartnakamoura Gbam No long cap😂😂😂😂

Jumia in a week? Build it. Then let me send 50,000 users to it on a Friday evening. We'll talk after.

A Nigerian fintech just lost ₦20 million to a fake webhook. Attacker didn’t hack anything. They just POSTed this to the endpoint: { "event": "transfer.success", "amount": 500000, "status": "success" } Backend credited the user. Zero money moved. This is happening more in crypto payments too. What every backend dev must do in 2026: 1. Verify webhook signature + IP + timestamp (not just event name). 2. Never credit on webhook alone always confirm on-chain + NIBSS. 3. Add rate limiting and replay attack protection. 4. Reconcile every stablecoin inflow against blockchain truth. Crypto rails move fast. One lazy endpoint and you’re done. Save this like your production depends on it. Drop your worst webhook horror story 👇

@fidexcode Well done senior Congratulations 💯

Added bed and gas cooker. Buying properties is damn cost.

On May 1st, CBN's new rules kick in. Most Nigerians don't know what's changing. The ones who don't?...they'll find out the hard way when they can't access their own money. Ten things every Nigerian must know before May 1st or else you gonna learn the hard way🧵 thread