@_Ola_sun_kanmi I was in a similar situation also in 200l. I didn't realize the field I plucked the water leaf had been fumigated. The strange smell when cooking the water leave gave it out. I poured it away with the small fish I bought and still drank garri again.
Damnnnn. It’s almost 12 today and I’ve forgotten about following 100 people daily 🤦🏻♂️🤦🏻♂️🤦🏻♂️
If I’m not following you and you’re Nigerian, just RT. No need to comment.
I applied to your firm for a job, you sent me rejection letter, very normal. I took it.
What I won’t take is you adding me to your subscribers, sending me news letter. You too dey go!!!
You’re uploading a 5GB file. You’re at 94%. Your internet drops. Most people groan and hit upload again from zero. But on a well-built backend, nothing restarts. It picks up exactly where it stopped. Here’s how.
A backend that handles this correctly never treats a 5GB file as one 5GB request.
Before the upload even begins, the file gets sliced on the client side into small fixed-size chunks typically around 5 to 10MB each. Each chunk gets a unique identifier: its position in the file, the total number of chunks, and a fingerprint of the original file so the server always knows what it’s dealing with and can verify nothing was corrupted in transit.
The server doesn’t just receive chunks blindly. It maintains an upload session; a record that tracks which chunks have arrived and which haven’t. Every time a chunk lands successfully, the server logs it. If the connection drops at chunk 47 of 500, the session doesn’t disappear. It sits there, waiting. When the user reconnects, the client asks the server one simple question: what have you already received? The server responds with the list of completed chunks, and the client resumes from chunk 48. The first 470MB never move again.
This is why platforms like Google Drive, Dropbox, and YouTube never make you restart a large upload from scratch. They use this exact pattern sometimes called multipart upload or chunked resumable upload and the session stays alive on the server for days, sometimes up to a week, giving the user a generous window to reconnect and continue.
The final step is reassembly. Once the last chunk arrives and every piece is accounted for, the server stitches them back together in the correct order and runs an integrity check against the original file fingerprint. If everything matches, the upload is complete. If even a single chunk is corrupted, only that chunk gets re-requested not the whole file.
@TheRuqayyah Everyday I wake up. I thank God for never having to experience what it means to work in a toxic space. This stories I see always send shiver down my spines
i made the Eba for myself and my room mate and after I finished devouring the Eba, I delivered my own banter back to him. The last time we spoke, he wasn’t doing so well. Whenever I can, I send him some money. A small way to show gratitude for always rescueing me back then
There was a particular day during my undergraduate years when my roommate and I were completely broke. No money was coming from home, and we had no one to call for help. The only thing left in the room was a small plastic container of salt. in school.
With the most serious but funny tone, he said, “Ego, go my kitchen go turn Eba chop egusi before hunger kill you" The way i dashed to his kitchen, even flash will struggle to keep up with me.