Yare Yare 💻

software Engineer, Nexara

[Yare Yare 💻 @ossigma11]

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

[Yare Yare 💻 @ossigma11]

@sin4ch @EOEboh Yes

[👑S.A.L.A.K.O🕊 @UnkleAyo]

If you go on any talk show, twitter space, tweet thread - to and debate a Tinubu supporter on policies or why Tinubu doesn't deserve a second term, you are a wild animal.

You are not just a wild animal.

You're also an irreparable fool who has no value for his/her brain cells.

[Yare Yare 💻 @ossigma11]

@Akintola_steve Link me

[Yare Yare 💻 @ossigma11]

@Akintola_steve Lols 😂

[Yare Yare 💻 @ossigma11]

@Akintola_steve Let me digest this

[Akintola Steve @Akintola_steve]

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.

[Yare Yare 💻 @ossigma11]

@Akintola_steve We feast I’m waiting

[Yare Yare 💻 @ossigma11]

@Akintola_steve Cool

[Yare Yare 💻 @ossigma11]

@am_fathiat She scammed my friend also 77k oh

[Yare Yare 💻 @ossigma11]

@prime_sui Mostly for versioning

[Yare Yare 💻 @ossigma11]

@wura_olar All true

[Yare Yare 💻 @ossigma11]

@EOEboh Can I be your mentee

[Yare Yare 💻 @ossigma11]

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

[Yare Yare 💻 @ossigma11]

@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

[Big Sheddy 🦅 @coder_blvck]

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!

[Val @yuteoflondon]

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.

[Yare Yare 💻 @ossigma11]

Soon

[shafu @shafu0x]

be so fucking good you never need to go through HR

[Yare Yare 💻 @ossigma11]

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

[Yare Yare 💻 @ossigma11]

The only mirror selfie I took this year 😪🤧

[Crazy Codes🚀👨‍💻 @richsongocrazy]

🙂