elohex

@DPrasanthNair Great oaks from little acorns grow!

Here are some high-level UAT (User Acceptance Test) checks I’d strongly recommend implementing in your auth system for stronger security: 1). Detect login from unusual locations or devices, e.g. Lagos → Russia in minutes, trigger step-up auth. 2). Rate limit login attempts, e.g. 5 failed tries = temporary lock. 3). Prevent token reuse or replay across multiple devices or sessions. 4). Invalidate all sessions on password change or logout. 5). Block any MFA bypass paths completely. 6). Ensure password reset tokens expire fast and are single use only. 7). Prevent privilege escalation via direct API access. Explanation: These checks are basically more like stress tests ones authentication system from an attacker’s point of view. Instead of only verifying that “users can log in,” this UAT here ensures the system can also resist abuse patterns like stolen credentials, session hijacking, and API manipulation. The goal is simple: every critical action in your auth flow should assume someone is trying to break it, and your system should still hold.

Another example: POS transaction at a roadside vendor. Network is unstable. Bank servers cannot fully communicate. The system has to choose: Approve the transaction fast (Availability), but you risk inconsistency. Or reject or delay the transaction (Consistency), which leads to a poor user experience.

Real systems choose trade-offs: Nigerian banking systems often lean towards consistency. Payment gateways sometimes lean towards availability, which is valid. DNS systems choose availability almost always.

@Chude_ND1 Time she spent piecing her nose, could have been better spent learning critical reasoning..

I love how the guy used her words to pin her. Never seen such brutal truth in a while!

You're Nigerian, you know what you did...doubling down and sharing publicly says all about your character

APIs - what Really happens 🔗 1. Client → Sends request 📤 2. DNS → Resolves domain 🌐 3. Load Balancer → Routes traffic ⚖️ 4. Server → Receives request 🖥️ 5. App → Runs logic ⚙️ 6. Database → Reads/Writes 🗄️ 7. Cache → Speeds up ⚡ 8. Response → Built & sent 📦 9. Client → Renders output 📱

😆

Constant training creates muscle memory...one acts without even thinking about it

@Akintola_steve Thanks Steve... sincerely appreciate what you do.

@elohex Nice one elohex

Every time your bank transfer fails in Nigeria, there’s a high chance it has nothing to do with your bank. It failed because of one system. One piece of infrastructure that every bank, fintech, and POS terminal depends on at the same time. It’s called NIBSS. And most engineers building Nigerian fintech don’t fully understand what it actually does

@Akintola_steve They've got the same play as NIBSS.

@Akintola_steve Aside from NIBSS, we have the option of Unified Payments(UP) as licensed payment service provider.

@Akintola_steve Well put together 👍

NIBSS is treated as a national infrastructure. It’s co-owned by CBN + banks. It runs redundancy and failover systems. But here’s the truth: When an entire country routes payments through one backbone… Any issue has a nationwide impact. The blast radius is total.

@TundeTASH Give anyone the "right" spouse/partner

Tell us one thing AI can’t do:

When you wake up every morning, Stand in front of the mirror & psych yourself up. Confess it loud to the man in the mirror: "You sef no small" as much as you can. You might go out that day and do small things but you're configuring your mind to treat you bigger than you are.

@Akintola_steve Not just tech, in all sectors. I preach this constantly, effort without presence means someone else gets rewarded. The balance is "be approachable".

@elohex Most people in tech are more of the Tunde guy. But it is advisable to be both the Tunde and Emeka persona type of guys

The best engineer at that company did not get the promotion. The one who got it had half the output, twice the bugs, and a folder full of unfinished PRs. But he had lunch with the engineering manager every Friday. And Tunde was eating alone at his desk. This thread is about what nobody in tech wants to admit: Technical excellence without social capital is a career on a slow timer.

@Akintola_steve 🙂

@elohex You the Emeka or Tunde guy ?

@Akintola_steve Effort without presence

Emeka joined three months after Tunde. A decent engineer, not exceptional. His PRs had comments. His estimates were often off. He once introduced a bug that took a full day to track down. But Emeka had something else. He remembered people’s names. Their kids. Their football teams. He showed up early to meetings. He asked questions. He followed up after 1:1s. Within six months, Emeka was everyone’s favourite engineer. Not the best. The favourite.

When people say “system design,” they usually mean two distinct things that often get confused: High Level Design (HLD) and Low Level Design (LLD). They are not the same thing. They solve different problems at different stages of building software. Let’s break them down properly

@Wizarab10 There used to be Full Gospel Business Men Fellowship...

Is there a fellowship of young professionals in this Lagos, who meet like once a week, to talk about Jesus and truly check on each other's welfare? A fellowship not linked to any church. A group of about 20 persons just dissecting the gospel and strengthening each other's faith.