Watching the Dutch government trying to get through the public procurement process for a "corona app" is equal parts hilarious and terrifying.

7 large IT firms screaming that they're going to make the perfect app.

Presentations with happy guitar strumming advertisement videos about how everyone will feel healthy, picnicking on green sunny meadows with laughing families, if only their app is installed on every citizen's phone.

Luckily, also plenty of security and privacy experts completely body-bagging these firms.

"It will connect people to fight this disease together" -- "BUT HOW" -- "The magic of Bluetooth. And maybe... machine learning. Oh! And blockchain!" -- "BUT HOW" -- "Shut up give us money, we promise, our app is going to cure the planet"

You got salesmen, promising their app will be ready in 2 weeks, although they can't even show any screenshots yet.

You got politicians mispronouncing technical terminology, trying hard to look as informed as possible.

You got TV presenters polling population support for "The App" by interviewing the most digitally oblivious people.

One of the app development firms (using some blockchain-based crap) promised transparency about their source code for auditing.... so they committed their source, including a backup file from one of their other apps, containing 200 emails/passwords to Github.

It's kind of entertaining... in the same way as a surgery documentary about the removal of glass shards from a sexually adventurous guy's butthole.

Imma keep watching out of morbid fascination.... from a very safe distance, far away from the blood and shit that's splattering against the walls.

And my phone -- keep your filthy infected bytes away from my sweet baby.

I'll stick with social distancing, regular hand washing, working from home and limited supermarket trips, thank you very much.

🍿🍿 pull up a chair and get comfy. This was a few years ago and anger has filled some details, so bear with me...

One day, during one of rare afternoons off of work, I was in the library to work on a group project for school. This was maybe a month before it was due, so we were tracking for decent progress and one less stressor over finals. It was about 80° F out, with the perfect breeze for the beach, but school comes first.

I'm team lead (which is terrifying, but less important) and my bro C shows up early to be ready to go on time because he's professional. I'M SO BAD I FORGOT DOUCHEBAGS NAME, so he's A (for asshole), shows up AN HOUR AND 15 MINUTES LATE. But it's not the end of the world, C and I worked around our database schema (which A sent us and we approved), so we could iron out kinks as we went.

A gets there... Fucking finally.

Fucker didn't have the database built (had 2 months to do it, we all agreed on schema a month prior. We're trying to be the adults our ages claim is to be).

*breathe in, count to 10* not a problem, A, just go ahead and start it now so we can at least check what we have.

Ok, my queen, I'll have it done in 10 minutes...

🤔🤔

We needed an id (sku... Which, in 99.9999% of companies is numeric), a short name (xBox one, Macbook, don't smart tv), a description and a price (with 2 decimals). All approved by all 3 of us.

His sku ranges from 3 to 9 ALPHA NUMERIC CHARACTERS, the names were even more generic than expected (item1, item 2, Item_3), no description, and he somehow thought US currency had 5 decimal places!!! (it's more accurate...)

There was an epic, royal, and expensive fight scene in the library (may have been during the Lenten season I decided to give up caffeine AND fast for 40 days to prove a point to an ass wipe of a history teacher, don't recall). I made him cry, he failed the class because C and I wound up fixing everything he touched (graded by commits, because it was also an intro to git, but also, a classmate saw it all), and I had to buy multiple people coffee for yelling in the library.

A tried making out buttons work (I was fed up and done thinking for the day, so moved to documentation), but he fucked those up. I then made those worse by having nested buttons, but I deleted all his shit and started over and fixed it.

I then cried, but C and I survived and have each others backs still.

After using linux as the main os for the last two weeks, here are the biggest drawbacks of linux in my opinion.

1. AMD hybird apus are not supported by linux kernal and it's very lousy.

2. Cannot do any graphics related work without having my screen going black several times.

3. Using dual screen is not reliable, and black screen occurs in one or both screens.

4. The computer goes crazy after waking up from suspend mode and gets overheated!

5. Kernal updates! Is much worse than Windows updates. At least after the painful windows update restart you know everything will be ok, but with linux good luck!!!

6. Realtek Wifi dongles still suffering since 2010.

In my opinion, if you are going to use linux for the first time make sure your hardware is compatible with linux, else be ready for a fight of unstable hardware problems.

If I close my eyes will all the problems pleas go away?

😭

These days where you haven't slept, woke up to smartphone having seizures and work began by spawning into a combat zone.

No I wasn't ready to fight, me wants sleep.

😫

I saw a genie once.

So it was like 1 am, me and my girlfriend back then was wandering around the street. We haven’t slept for like two days. It was also a time when she started showing signs of being bipolar and my manic episodes started. So we wasn’t exactly in a good shape, everything felt surreal.

To add absurdity I was holding a pair of scissors (I don’t remember how I got them in the middle of the street) ready to fight back night gopniks.

We went underground and we saw this: there was a hobo standing on a chair and singing. He was really good at it, all opera level stuff with tremolo and everything. The other hobos was standing around him looking and listening. They all completely ignored our presence.

Between two pillars lied the other hobo. He was covered in some dark-looking liquid. Around him was a really huge bottle, so huge in fact that he could probably fit in. I guess they use those kind of bottles in bars or something.

I have no other explanation that he was a genie that was living in that bottle before and granted that singing hobo three wishes: brilliant singing voice (he could probably be a guy who always wanted to sing but had no talent and so he started drinking and became a hobo eventually), an audience that understands and appreciates (the other hobos) and a final wish, just to drink together and have a great conversation.

Learning react at the moment and I feeling like am walking on fire but am ready to fight to to the end.

Hello node.js
i hope to have some fun with each other
But if you want to fight with me, I'm ready to defeat you

"The Perils and Triumphs of Debugging: A Developer's Odyssey"

You know you're in for an adventurous coding session when you decide to dive headfirst into debugging. It's like setting sail on the tumultuous seas of code, not quite sure if you'll end up on the shores of success or stranded on the island of endless errors.

As a developer, I often find myself in this perilous predicament, armed with my trusty text editor and a cup of coffee, ready to conquer the bugs lurking in the shadows. The first line of code looks innocent enough, but little did I know that it was the calm before the storm.

The journey begins with that one cryptic error message that might as well be written in an ancient, forgotten language. It's a puzzle, a riddle, and a test of patience all rolled into one. You read it, re-read it, and then call over your colleague, hoping they possess the magical incantation to decipher it. Alas, they're just as clueless.

With each debugging attempt, you explore uncharted territories of your codebase, and every line feels like a step into the abyss. You question your life choices and wonder why you didn't become a chef instead. But then, as you unravel one issue, two more pop up like hydra heads. The sense of despair is palpable.

But, my fellow developers, there's a silver lining in this chaotic journey. The moment when you finally squash that bug is an unparalleled triumph. It's the victory music after a challenging boss fight, the "Eureka!" moment that echoes through the office, and the affirmation that, yes, you can tame this unruly beast we call code.

So, the next time you find yourself knee-deep in debugging hell, remember that you're not alone. We've all been there, and we've all emerged stronger, wiser, and maybe just a little crazier. Debugging is our odyssey, and every error is a dragon to be slain. Embrace the chaos, and may your code be ever bug-free!

I wrote a script, modified + tested it and that worked fine 6 months ago. I expected to use it then but didn't but all good so i kept a special branch for my script which generates data from old db, formats it to new db structure and dumps it into a collection. In fact, i ran one of the scripts last month (360 records) and it worked fine. Today, when i need to migrate 14,000 records, script refuses to run. I am ready to fight the universe because wtf.