TAENTED

A good dev writes clean code. A great dev understands what runs between the code and the database — and designs for it. System design isn't advanced knowledge. It's foundational. Please RT if this helped so share the knowledge 🙏 Happy Sunday!

Building websites isn't just about writing code or letting an AI write it for you to speed up delivery. The real skill is knowing what happens when you push your code to production. Here is a thread on something most tutorials skip 🧵

These aren't edge cases. They're production bugs wearing the costume of infrastructure issues or bad luck. The fix isn't more code. It's correct system design from the start.

Starvation High-priority traffic (bulk product reads) hogs the connection pool. Lower-priority ops like sending a verification email - never get their turn. Your user never gets their OTP. You never know why.

Live-lock Both operations keep reacting to each other. They're "running" but making zero actual progress. Worse than a crash because it's harder to diagnose.

Deadlock Two operations each wait for the other to release a DB resource. Neither moves. Both freeze. Your app just... hangs.

It gets dangerous. When transaction pooler and session pooler traffic compete on the same DB without proper management, you get classic CS concurrency problems. Most devs don't know these by name. They just call it a "slow day." 👇

Here's a real-world way to think about it. Imagine Jumia: - Millions of users browse products → transaction pooler (fast, stateless reads) - Sellers verify accounts, get emails, update profiles → session pooler (persistent sessions) Both hit the same database.

These 3 options exists for a reason: Direct connection → local dev & migrations Transaction pooler → production reads (users fetching posts - short, stateless) Session pooler → persistent ops (auth, emails, verifications) Picking wrong silently breaks things.

I recently added a blog system, admin dashboard & partnership portal to a company site backed by Supabase (PostgreSQL). Everything worked locally. Then came the question nobody warns you about: How do you connect your DB correctly across environments?

@VictorBuildsApp Noted boss😂.

If I miss a day (unless it’s exams or no light 😅), I’ll give ₦10,000 to one random person who reposts this and correctly calls me out that same day.

At the beginning of this year, I decided to start posting more about myself and my work here on X to document my journey and open myself up to opportunities. That didn’t go well obviously 😂 I just dropped one post and disappeared.

@pec_visuals Moving a couple of projects to production phase. I’d love to see the smile on my clients faces.

What’s one thing you’re focusing on this week?

Rest, reset, and refocus. A new week is coming.

Feeling grateful actually🙏 Honestly working and schooling is the best way to train yourself and get ready for the real world after done with school.

Claude deep down: “This one don come again”

When I hold the mic, everyone keeps quiet and listens. Been a trait of mine since day one.

@Kadotttt @mathjuma Well, Given the problem specifications in your case, The passed requirements are An Encryption and Handshake (very necessary) UDP or TCP communication protocols Stealth/obfuscation features DNS leak protection. Kill switch.

@Kadotttt @mathjuma When you purchase a data plan, you use their public Ip for internet access, which makes them able to see the requests you sent to different sites. The only solution is to either use a proxy or a strong VPN that encrypts all your communications.

@taented9 @mathjuma Which is that strong vpn 😞

You people never told me that your Wi-Fi supplier can see my browsing history even in incognito mode 😭😭😭😭😭😭😭😭😭

@mathjuma If i watch something on incognito will they see what I watched? That's my real concern

Helpful Ethical hacking tip they don’t tell beginners: VMs are good for learning, but they slow you down long-term. Dual-boot or switch fully. Fewer issues, better performance, and direct hardware communication.