Yare Yare 💻

One day I'm going to come back to this tweet and say "I made it in tech"

@Akintola_steve Lols 😂

@ossigma11 Me sef I follow you shout omooo 😂

Backend devs, What’s the most difficult feature you’ve ever implemented since your whole existence of writing code? Please I’ll really want to hear from you guys.

@Akintola_steve Let me digest this

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.

@Akintola_steve We feast I’m waiting

I was bored and decided to record a quick video tutorial on how to test whether your API can scale under high traffic using Apache JMeter. I’ll drop the video tomorrow morning, it seems everyone is asleep now.

@Akintola_steve Cool

@am_fathiat She scammed my friend also 77k oh

I texted her already and this is what she have to say well see who will comot from her walahii she’s going to refund the money whether she like or not! This is her TikTok page I’m going to be posting her and my brother chat in the next post

@prime_sui Mostly for versioning

Why do many backend developers start their api endpoints with “/api”

@wura_olar All true

Honestly, it’s exhausting being Nigerian and having to pretend that our problem starts and ends with politicians. Yes, the people at the top are corrupt, but let’s stop lying to ourselves, corruption has sunk deep into everyday life. It’s in how we think, how we behave, and how we justify nonsense as hustle or sharp guy mentality. We lack discipline as a people. Discipline to follow simple rules. Discipline to be honest even when nobody is watching. Everything is about cutting corners, doing things the fast way, the crooked way, as long as money enters pocket. From small bribes to avoid traffic rules, to inflating prices, to stealing from office supplies,to exam malpractice, everyone wants to be innocent, but everybody is somehow involved. We shout bad government,but the same person shouting will still cheat the next person if given the chance. We complain about leaders looting billions, yet some Nigerians will steal ₦5,000 and feel smart about it. Corruption didn’t fall from the sky, it grew because we nurtured and allowed it at ground level. This lack of discipline is ruining our global image. Abroad, the moment you say you’re Nigerian, people are already on guard. You have to work twice as hard to prove you’re not a scammer, not fraudulent, not dishonest. Our passport is weak not just because of policies, but because trust in Nigerians has been damaged over time. That reputation didn’t build itself, our actions did. And economically, this behavior is killing us. Investors don’t trust systems that can be manipulated. Businesses don’t thrive where contracts mean nothing and integrity is optional. Money that should build infrastructure is lost to greed. Productivity is low because many people are focused on shortcuts instead of skill, value, and long term growth. Everyone wants quick money, nobody wants to do the hard, boring, disciplined work that actually builds a nation. What’s worse is how we normalize it. We celebrate wealth without asking questions. We excuse corruption with poverty. We clap for thieves as long as we get our share.We mock honesty and call disciplined people fools. How do you grow an economy like that? How do you build a future on deceit? Until we start holding ourselves accountable, not just politicians, I’m sorry but nothing will change. Until the average Nigerian learns that integrity matters, that discipline matters, that doing the right thing even when it’s hard matters, we will keep recycling the same problems with different faces. Nigeria doesn’t just need better leaders. It needs better citizens. And that truth is painful, but it’s necessary. It is well.

@EOEboh Can I be your mentee

The Three Pillars: 1. Logs (what happened) 2. Metrics (how much/how fast) 3. Traces (the path through your system) Together these give you full visibility.

@Utdtruthful One of the reasons the club would never move forward

🚨🗣️ Rooney on Amorim: “I think you need to earn the right to be able to dictate exactly what happens at a football club, especially United. If Pep comes into the club, for instance, I don't think anyone will question him what players he wants to bring in or the system. I feel for him a little bit, but he’s not Guardiola or Klopp. He hasn't got that history or background, so I don’t think he should be speaking with that authority.” #MUFC [BBC]

@TheUnitedExtra You guys are all crazy what do you want him to do.. which attacking minded player do you have there ffs you all should just rest and understand we are bad at the moment

Advice for entry-level software engineers: Focus on understanding how computers work. Learn how they transmit, process, and store data. Fundamentals are more important than the latest frameworks. Right now, AI can generate code, but it cannot solve the problem for you. To effectively instruct the tool, you must understand the building blocks. 1. Start with Networking. Don't just verify that an API works. Understand how the data gets there. - HTTP/HTTPS: Learn the request lifecycle. - DNS: How names become IP addresses. - TCP vs. UDP: Reliability vs. Speed. If you don't understand the transport, you can't debug the latency. 2. Master the Operating System, specifically Linux. Most of the cloud runs on Linux. You need to be comfortable in the terminal. - File Systems: Everything is a file. - Process Management: How programs start, run, and die. - Memory Management: Stack vs. Heap. All code needs an OS to run. 3. Understand Data Structures (and when to use them). This isn't about passing interview tests; it's about performance. - Know why a Hash Map is faster than an Array for lookups. - Understand Big O notation to predict how your code behaves as user traffic grows. Inefficient code costs money. 4. Deep dive into Databases. Storing data is easy; retrieving it quickly is the hard part. - Indexing: How to make queries fast. - ACID: Understanding transaction integrity. - Normalization: How to structure data to avoid redundancy. Bad schema design creates tech debt that is painful to fix later. The best engineers I know aren't the ones who know every syntax of a new language. They are the ones who can understand systems thinking & can visualize the path of a byte from the user's click to the hard drive and back. “Vision without systems thinking ends up painting lovely pictures of the future with no deep understanding of the forces that must be mastered to move from here to there. — Peter Senge, The Fifth Discipline (Currency)” Focus on the mechanics, and the tools will make sense. Happy New Year, May the force be with you!

If you’re 20-25, you’re probably not sure what you want to do in 2026 yet, if I was 20 again, this is how I’d pick 5 goals for the new year. 1. One to keep fit – Could be the gym, walking, playing football, boxing, or running. 2. One to acquire more knowledge – Could be learning a new skill, sharpening one you already have, learning to create content, or researching investment opportunities. 3. One to develop your mind – Could be journaling (I personally don’t do this), meditating, listening to self-development podcasts, or high-intensity workouts. 4. One to grow your relationships – Keep in touch with friends, communicate and connect with family. 5. One to make you money – Find something you’re interested in or can learn in 3-6 months. Learn it, then start earning from it. In 2026, try.

Soon

@EOEboh @TayCode How can someone contribute to open source effectively

@TayCode This is so real... That's why the next best thing for this kind of situation is to gain some good experience on open source contributions, but even that requires some level of skill

Envy people who got the opportunity to work on impactful things at the beginning of their careers. I am here looking at my resume and the first 3years look like random stints in failed startups that never made it. Also was the only backend engineer with no one to learn from.

The only mirror selfie I took this year 😪🤧

If I talk I would be in trouble

Everytime I see this clip, it moves me incredibly. If you're within means of helping someone step closer to their dreams, please always do. If you've ever been helped, please always remember - and do pay it forward.

@chinedu_10 I would say writing docs is a skill on its own

I’ll go further: writing good technical articles is harder than writing the code itself. You have to build something that works, then explain it to someone with zero context. That’s the real challenge. Code either works or it doesn’t. Documentation has to work for everyone, from juniors to seniors, different backgrounds, different learning styles. Getting code to compile is one thing. Getting another human to understand it? That’s harder.