@gleesh The bouncer lets you in without
searching you because he knows you.
First, you think that's cool. Then you start
wondering how many other niggas he
knows. Then you start wondering how
many niggas are in here strapped.
Okay, so I've been trying to drop my phone, but I'm always back to it in a few minutes, so I decided to read up on what's actually going on
Turns out it's called dopamine hijacking, and every app we use is doing it to us right now
Let me explain what I found
API Design Playbook:
Giveaway Alert!!
• Core API fundamentals.
• Clean & scalable design principles.
• Common patterns used in real world systems.
• Practical concepts for interviews & building projects.
(24 hours only & I won't offer this ever again!)
To get it:
1. Like, Retweet & Follow @systemdesignone
2. Reply "Playbook"
Then I'll DM you the details.
Backend devs:
If you’re still spinning up Postgres, Redis, and other services manually, opening multiple terminals, running different commands, fixing port issues… you’re doing extra work.
One simple file can start your entire backend stack in seconds.
Bookmark this for later and retweet so more devs see it.
I miss the days when I wrote code on Notepad and Notepad++.
Back when I had to visit Stack Overflow, read through how someone solved a similar issue, and then write the code myself, relying heavily on docs rather than automated AI.
Those days will always remain golden in my life 🫶🏾
Honestly, if you want to secure a backend role in a fintech company that deals heavily with transactions, these are the things you must understand.
If the company actually knows what they’re doing, their questions will revolve around things like:
Idempotency – preventing duplicate transactions
Concurrency control – handling multiple requests safely
Database transactions (ACID)
Distributed systems basics
A lot of people underestimate this side of backend.
But that’s just the surface…
Bookmark and retweet so people can learn from this too
Techies who have been following my write-ups, stay tuned. Starting next week, I’ll be sharing more technical write-ups — integrations, payment systems, idempotency, scaling, and best practices.
But expect something tomorrow.
Let’s build competent software engineers, not just vibe coders.
Most backend engineers are used to thinking that their job ends once they provide the API endpoints.
But the real question is how well do those endpoints perform when a large number of users hit them repeatedly at the same time? And more importantly, how do you test that during the development phase?
In the video above, I explain how engineers can properly test whether their endpoints can handle scale and repeated requests from multiple users simultaneously, using a tool called Apache JMeter.
The video walks through everything—from installation to running the tool and finally testing your API. For this demo, I used a local service running on my laptop.
Do well to watch, like, retweet, and bookmark so others can learn from it too.
In 2021 Tunde got his first developer job in Lagos
small fintech, 4 man team, big dreams
his boss handed him a laptop on Monday and said
“the codebase is on GitHub, you start today”
Tunde opened his terminal and froze
he had never used Git in his life
Bookmark this. RT the first tweet so your developer friends see it too