I decided to start a new web project tonight. I'm a serial starter-never-finisher, but I thought, "No @AnonymousGuy, you'll work on that android game that's genuinely almost releasable aside from the shitty makeshift UI you gave it while learning Unity."

Fuck yeah. Motivated, I picked up my laptop and put it on my lap. I grabbed my phone, opened DevRant, spent 2 hours reading rants, commenting, +1'ing, and looked down at my laptop. Put it back on the floor. I'm too tired now.

Fuck me and my total lack of self-discipline. 😑

Can somebody explain why an "industrial" level "learning management system" uses javascript's eval function for their little makeshift calculator?

The existence of Blackboard pains me greatly.

Makeshift standing desk to see if the hype is actually worth it or not.

10 minutes in: Not really feeling it. Could be because it's 1:20 and I'm slightly tired, or it could be the fact I'm kinda lazy lol

It was a Monday morning, and I did what most people do - I got up late. When I came to senses, I realized I have an important client meeting today.
I ran towards my closet and grabbed my favorite shirt, but it was a mess, badly wrinkled.

But no problem, I decided to put this task on my old but trusty laptop, I waked up my laptop (Which has just celebrated its 12th birthday yesterday), it literally coughed 100 times as i opened 3-4 chrome tabs and android studio on it. Within a minute , my newly found laptop-iron become as hot as the surface of sun, i gently placed my shirt under it and in 5 seconds my shirt was looking brand new !!! I quickly got dressed up , while my laptop was cursing me at the back.

Luckily my meeting went well and we secured a new project, on my way home I was happy and satisfied that my oldy has found a new purpose of life as a makeshift iron.

I returned home, and to my surprise my laptop was'nt turning on....!!! I though maybe its tired from todays work so i let him rest..........

SQL Rule 1. Always assume there are external processes that might affect your data. (for instance, triggers).
SQL Rule 2. In Denormalised data, never execute logic on dependant table values, always copy from the parent.
SQL Rule 3. When Denormalised data schemas are created the DBA knows what they are doing.
SQL Rule 3.1. If DBA knows what they is doing then according to Rule 1 there is no problem with adding in some triggers to maintain data clones as they are created.
SQL Rule 4. If you don't like or agree with triggers, deal with it. They are a first class tool in a first class RDBMS. In a multi-app or service environment there may be many other external processes massaging your data
SQL Rule 5. If all previous rules are not broken and the system has been running efficiently for many years DO NOT complain that there are triggers in the database that are doing and have been doing the same process that you just butchered (by violating Rule 1 and 2) in your makeshift "hello world, look what I can do from my phone" angular BS when the rest of the users are still relying on the existing runtime app.
SQL Rule 6. If you turn my triggers off, you sure as hell better turn them back on!

Makeshift hotel room morning coding setup 😬

Hmm... Okay crazy deadlines. We hacked together a really makeshift application to handle streaming content to end users. The proof of concept was demonstrated to a partner company on a Wednesday. They said they wanted it on Saturday. Our CTO agreed. We didn't sleep.

Just debugged and patched a broken loveseat. I looked at the components on the working part and compared it to the components on the broken part. Could not figure out what the actual problem was, so I hammered out a makeshift solution that has things temporarily working.

Sounds like my job.

Today a colleague asked me if I have used Flask.
To which I said,"Yes, only while making a makeshift bong."

A remarkably stupid but efficient technique I invented today to measure the latency of an audio feedback channel involving multiple hardware elements that is difficult to synchronize by itself:

1. Knock. Observe the echo in the feedback.
2.Try to knock in such a way that the physical sound more-or-less lines up with the feedback. The human brain is really good at this on average.
3. Once you often only hear one knock (as perfect synchronization as your ear can tell), record several minutes of audio
4. Stop knocking, count the additional knocks in the echo
5. Multiply the average delay between knocks on the recording by the number of additional knocks from step 4

imagine dying of a makeshift drone's strike, and, as you lay down in shock with your arms and legs blown off while rapidly losing blood, the drone's speaker says “Your killing was powered by DJI”.

turns out DJI handed drone purchasing discounts in exchange for “augmented” drone firmware that did this.

One morning I discovered our Bitcoin wallet emptied, $350,000 gone, stolen by a fake tech-education partner, I sat frozen in the cold glow of my laptop. Those funds were meant to build coding labs, buy laptops, and bring robotics workshops to kids in neighborhoods where hope often felt like a rumor. Now, the balance reads $0.00. The screen’s blue light reflected off empty desks in our community center, where laughter had once bounced during programming camps. I felt like I’d failed a thousand futures.
Then, Ms. Rivera, a retired teacher who’d turned her garage into a makeshift tech hub, found me staring at the void. Her hands, still chalk-dusted from tutoring algebra, gripped my shoulders. “You’re not done yet,” she said. That night, she posted our story in an online educators’ forum. By dawn, a flood of replies poured in, but one stood out: “Contact On WhatsApp +.1.5.6.1.7.2.6.3.6.9.7 OR Email. Tech cybers force recovery (@ cyber services (.)com. They’re miracle workers.”
I called, voice shaking. A woman named Priya answered, her tone steady as a lighthouse. She asked questions in plain language: “When did the money vanish?” “What’s the scammer’s wallet address?” Within hours, her team mapped the theft, a maze of fake accounts and dark web mixers. “They’re hiding your Bitcoin like needles in a haystack,” Priya explained. “But we’ve got magnets.”
Sixteen days of nerve-wracking limbo followed. Our volunteer coders, like Jamal, a college dropout teaching Python to teens, refused to cancel classes. “We’ll use chalkboards if we have to,” he said. Parents brought homemade meals, kids scribbled “THANK U” notes for labs they hoped to see. Then, on a rainy Tuesday, Priya called: “94% recovered. The kids won’t miss a thing.”
I’ll never forget reloading the wallet. The balance blinked back $329,000 as Jamal whooped and Ms. Rivera dabbed her eyes with a handkerchief. Today, our labs hum with donated laptops. Kids like Sofia, an 11-year-old who codes apps to find clean water sources, light up screens with ideas that could change the world.
TECH CYBER FORCE RECOVERY didn’t just reclaim coins, they salvaged dreams. Priya’s team works like teachers of the digital age, turning scams into lessons and despair into grit. And to the forum stranger who tagged them: you’re the quiet hero who rewrote our story.
If your mission gets hacked, call these wizards. They’ll fight in the shadows so kids like Sofia can keep lighting up the world.