Replying to @Callmeisaac17
Practice with yourself alone
Replying to @faustinaify_
I hope he does in a good way
One thing I think more people should practise is speaking and responding to others without unnecessary body movements.
Someone asks you a simple question, and before you even answer, youβve nodded your head five times, adjusted your clothes, touched your face and shifted your entire body π
You donβt have to move your whole body to communicate.
Learn to give a simple yes or no without overdoing it. Practise speaking calmly, maintaining a comfortable posture and being intentional with your gestures.
Iβm not saying you should stand like a statue. Body language is a normal part of communication.
But thereβs a difference between expressing yourself naturally and constantly fidgeting while you speak.
Sometimes, the less you do, the more composed you appear.
Replying to @0xTreasure
Thatβs brilliant man
Replying to @Akintola_steve
Good luck bro
Replying to @pamilhereen
God go do am for me π
Ray π¨π½βπ» website & app developer retweeted
Weβre launching Rants π
Sometimes βitβs fineβ is not fine π€§
Get your own link and let people tell you what they really think, anonymously.
For your business, your work or just yourself. For the culture π
rants.huxxle.com/create/
When it comes to system design, most people understand logs and metrics but tend to overlook traces, which are just as important for improving a system.
Logs help you understand whatβs happening in your application. They record events like user actions, failed requests, database errors, and other activities that help you investigate issues.
Metrics give you measurable insights into how your system is performing. Think response times, error rates, successful transactions, abandoned carts, server usage, and so on. They help you identify patterns and spot performance issues.
But hereβs where traces come in.
Traces follow a request through your system, from the moment itβs received to the moment itβs completed. They show which services were involved, how long each operation took, and exactly where delays or failures occurred.
Imagine users complaining about slow checkouts. Your metrics might tell you checkout times have increased, and your logs might show that payments are still processing successfully. But neither necessarily tells you whatβs causing the slowdown.
A trace can reveal that your payment service is spending 3 seconds waiting for an external API.
Now you know where to investigate instead of guessing or wasting time optimizing unrelated parts of your system.
Thatβs why traces matter. They help you identify bottlenecks, understand dependencies between services, troubleshoot failures faster, and make targeted performance improvements.
Logs tell you what happened. Metrics tell you how your system is performing. Traces help you understand the journey behind it.
All three matter if youβre serious about building reliable, scalable systems.


