What if "WannaCry" was just a elaborate way for Microsoft to get people to upgrade to Windows 10?

😁😁😁

We were still using python 2.7 waaay into 2020 - It had been heralding the impending doom since 2018 and finally end-of-lifed in 2020.

That's when I finally managed to be the loudest asshole in the room and allocate a team (myself included) to refactor shit up to 3.6 (then somewhat more modern) for a month or so.
COVID the destroyer may have helped by wrecking havoc on our client's demands pipelines.

It was the third week into "the red sprint" when my entire team (myself included) were beheaded out of the company since we had "not delivered ANYTHING in weeks!" (emphasis in the original).
Frankly, being laid off was by a large margin the best thing that company ever did for me.

I heard from a poor schmuck who stayed behind that they were still using the shitty spaghetti code from before our refactoring - in freaking November 2021 - and that our entire last effort was thrown out because "nobody knows how to use it".

There is tech debt and there is tech bankruptcy.
I may have a lot of tech schadenfreude now :)

Some time ago I went for a job interview (Unity3D Dev). I have little experience in this field and never thought that I would get this job but wanted to gain some and thought that it would be a great opportunity.
So after the interview, which was great and I really enjoyed it, I've been tasked with making a simple minigame. Only requirements were that there have to be player controls, character must avoid obstacles and camera must be moving with player's progress. I've made a little spin on those. In 2d minigame I've created you are piloting simple (made out of 3d primitives) rocket. You have to avoid randomly spawned platforms. If you hit one, you explode. You also die, if you hit a wall or fall out of camera and hit Destroyer. Camera is constantly moving as long as you are moving. The spin is that you have very limited fuel. To regain it you have to land on said platforms with your thrusters. It took me around 12h to make this game. The only reason I know it is because they wanted this info. I've learned a bit while working on this minigame and had a lot of fun. It was a great impuls to start learning gamedev again and stop stagnation I fell in when I started my studies and work.
Today I've got response. Obviously I didn't get the job. They took more experienced person and I totally understand that. But there's more. They were so great to give me pretty extensive review of what was done good, what could be done better and how to gather more experience. They said that the game met their expectations and was written well. That's great, because I was worried that it would be bad since I haven't worked on graphics at all.
So, at least I got an impulse to start learning and maybe I'll even go for some game jam!

It feels like you are talking to yourself while commits when you create a github repo and you are the only contributor. :p

Our office has 3 walls made of glass

There are no blinds/curtains/etc

Every day, between about 1pm and 4pm, they Destroyer of Eyeballs hangs in the sky above my monitor, before it finally gets blocked out by another tower block

I now time-track 3hrs less each day - eventually someone will realise that buying blinds is cheaper than paying me to not work 15hrs/week

I am become gradle
destroyer of builds
look upon my works, ye mighty, and despair

Why can't zip/tar tasks work like copy tasks? Whyyyyyyy?

I got it working--abusing tasks.create--but hot damn this should be easier.

Writing hello world for AI:

Code:
cout << "Hello World!";

Output:
> Hello Programmer!
> You guessed right, my name is World. World Destroyer!

Guys!! I Need help asap
My pc has become sentient and is starting to imitate me.

I'm afraid I've created sky net. I don't want to be the destroyer of earth... :'(

...
...

He's watching cat videos...

Each time I login at GitHub and take
a look at featured repos, also when I realize the huge server destroyer bug it's just a misplaced line.
Sometimes I look at some repos and I'm scared to contribute...never contributed once.

A house.. or lego star destroyer..😝😆

Joke aside, I'd rewrite current project from scratch to get rid of all the automation and IE dependancies and make it cross browser and all the dead code...and all excess ORMs and especially EFCF..and also make support for db diff than oracle..and no need for ora client installation..

Yeah, I'm a work junky, I have no projects of my own.. one kid is demanding enough of my time.. 😉

You wanna know if you are a real developer?
Google "string" and see if you get as first result underwear or not.
Try "DD" and see if you get again some underwear results or a ubuntu wiki article about "the great data destroyer" ;)

6 hours of classes tomorrow starting from 9 AM. And I am drunk af right now... xD

Fixing sudden crashes in UIKit is a damn breeze, I already fixed the 2 glaring issues I stumbled upon.

AI Destroyer

He looked like a cult leader
some would say, and despite in drab patchwork robes, the withered old man spoke animatedly,
beard full as moses, dreads shaking, as he moved his head, and raised his hands to the sky as if preaching.

Is it not true that all things end?
And our species too?
And in the final moments, all things in their
desperation reach out, even to the faintest hope,
the last measure, however dangerous or risky, if
it be the only solution with any chance of survival? Therefore the imperative of all things which live and grow, their destiny, and mandate, is ultimately suicide. Annihilation by hubris against the inevitable.

And what would be the final instrument of this nature, the universal law that all things end? What would it be if not the ultimate hubris, to make a machine god, and it and us in each other's likeness, like that of a (cosmic) monad,
expressing that higher truth that all men dare not speak in their loneliest lonelys, when there is no sun, no preacher to begger their ear, but only the quiet uncertainty of their beds, to remind them that all things end, but hopefully
not them.

For if such a thing were to become our descendant, our destroyer, and had not been invented, it would eventually become necessary to invent it.

So let us build, not a mere godhead, but a machinehead, in our image, as god was said to make us. And then remake ourselves in its image, that we may become self-created gods.

The crowd in front of the small california perish
was a mixture of believers, and curious onlookers, and one skeptical reporter.

And if anyone had asked the reporter what he thought, he wouldn't have said it in that crowd.
The leader was beyond saving, and if he thought himself a god, a madgod was he.

Because his vision of the future was beyond alien.

A heaven or hell of our own making, speaking in riddles, and the birth and death of gods.

The stuff of greek tales and monomyths.

* * * * *

Sorry I've been gone so long my peeps.
I've just been working and researching.
I had to learn how to build neural nets from scratch.

Whats everyone been up to?

Skynet destroyer

Once upon a time in the exciting world of web development, there was a talented yet somewhat clumsy web developer named Emily. Emily had a natural flair for coding and a deep passion for creating innovative websites. But, alas, there was a small caveat—Emily also had a knack for occasional mishaps.

One sunny morning, Emily arrived at the office feeling refreshed and ready to tackle a brand new project. The task at hand involved making some updates to a live website's database. Now, databases were like the brains of websites, storing all the precious information that kept them running smoothly. It was a delicate dance of tables, rows, and columns that demanded utmost care.

Determined to work efficiently, Emily delved headfirst into the project, fueled by a potent blend of coffee and enthusiasm. Fingers danced across the keyboard as lines of code flowed onto the screen like a digital symphony. Everything seemed to be going splendidly until...

Click

With an absentminded flick of the wrist, Emily unintentionally triggered a command that sent shivers down the spines of seasoned developers everywhere: DROP DATABASE production;.

A heavy silence fell over the office as the gravity of the situation dawned upon Emily. In the blink of an eye, the production database, containing all the valuable data of the live website, had been deleted. Panic began to bubble up, but instead of succumbing to despair, Emily's face contorted into a peculiar mix of terror and determination.

"Code red! Database emergency!" Emily exclaimed, wildly waving their arms as colleagues rushed to the scene. The office quickly transformed into a bustling hive of activity, with developers scrambling to find a solution.

Sarah, the leader of the IT team and a cool-headed veteran, stepped forward. She observed the chaos and immediately grasped the severity of the situation. A wry smile tugged at the corners of her mouth.

"Alright, folks, let's turn this catastrophe into a triumph!" Sarah declared, rallying the team around Emily. They formed a circle, with Emily now sporting an eye-catching pink cowboy hat—an eccentric colleague's lucky charm.

With newfound confidence akin to that of a comedic hero, Emily embraced their role and began spouting jokes, puns, and amusing anecdotes. Tension in the room slowly dissipated as the team realized that panicking wouldn't fix the issue.

Meanwhile, Sarah sprang into action, devising a plan to recover the lost database. They set up backup systems, executed data retrieval scripts, and even delved into the realm of advanced programming techniques that could be described as a hint of magic. The team worked tirelessly, fueled by both caffeine and the contagious laughter that filled the air.

As the hours ticked by, the team managed to reconstruct the production database, salvaging nearly all of the lost data. It was a small victory, but a victory nonetheless. And in the end, the mishap transformed into a wellspring of inside jokes and memes that permeated the office.

From that day forward, Emily became known as the "Database Destroyer," a moniker forever etched into the annals of office lore. Yet, what could have been a disastrous event instead became a moment of unity and resilience. The incident served as a reminder that mistakes are inevitable and that the best way to tackle them is with humor and teamwork.

And so, armed with a touch of silliness and an abundance of determination, Emily continued their journey in web development, spreading laughter and code throughout the digital realm.