The RGB makes the code run faster

“You’ll be working in a fast-paced environment…” ALWAYS means “We’re incompetent, we don’t realize it, we don’t hire enough people to spread out the workload, we don’t have a real process, and we’ll blame you, the new guy, the first time something goes wrong.”

In highschool we went through something like a malware/phishing prevention course.

It was pretty cool tbh, we spend the whole hour in a virtual environment where you'd see common malware and phishing attempts, but the really fun you could also "hack" other students.

Hacking them means you could cause some things to happen on their "PC". One of those was showing in a captcha on their screen and they had to type a the string of your choosing, before they could access the rest of the "virtual computer" again.

You can probably guess where this is going.
I was the first who had the idea to mix big i and small L and tested it on our teacher, who was also part of this environment and screenshared to the projector.

Thanks to sitting next projection I could see the pixels and I can confirm: same character, Pixel perfect!

I will forever cherish the memory of my the teacher begging me to undo the "hack" and the chaos that followed amongst my peers 😈

Also one of the excersizes was stupid. Click on a phishing mail and enter your credentials in the form. I asked the teacher WTF kind of credentials they even want me to enter to microsooft.cum and they just said "the credentials obviously" so I think they got their karma🖕

I wrote a Blender plugin that uses vector math, matrices, calculus, trigonometry, and likely other types of math. There's recursion, filesystem access, image processing, interface logic, and on and on.

And worst of all - other people are expected to use it, so there's added pressure to do a good job.

Oh, the hours I spent trying to figure out why the imported geometry looked like an exploded mess. Fumbling around with mathematics I didn't fully understand was exhausting. Finding help was impossible at times because I didn't have the vocabulary to even describe the problems I was having. And getting it to complete an import before the heat death of the universe was not easy.

Every time I made progress and thought I was done, I would discover a bug that other importers didn't have, leaving me to sift through languages that definitely aren't Python to see if I could reverse engineer the logic they used.

I almost gave up a few times, but didn't.

Now I have something that, while not used by many people, works very well, is very efficient, and doubles as a palette cleanser when I need to do something for fun or for a challenge. Plus I learned a lot along the way.

I have worked with a handful of very green devs in the last 10 years. A common theme has emerged.

They don't heed any of my advice.

An exercise to the reader:

If you have a Windows machine, but need to work in a Linux environment, what would be your first instinct how to proceed?

In this exercise, you are as green as it gets. You have very little professional development experience, let alone server admin experience. And your lead dev has suggested setting up a VM.

1. Set up a Linux VM
2. Use a live CD or set up a dual boot system
3. Pay for a cloud server and set it up from scratch

I have no idea how this person intends to get any work done on a remote, terminal only, Linux server. That is if I can even get their environment into a sane configuration.

I attended a webcall with the cat on my shoulder, some manager complained it was not professional.
Now, I do not know who that was so I'll have to just shoot in the crowd and take innocent victims, but from now I'll attend every single call with as many cats on screen as possible. Possible outcomes, and both are fine by me, either they cut down the amount of unnecessary calls -as to limit the amount of catness on their screen- or learn to grow the fuck up because unlike some retard I get paid for working, not for busting the balls to the people that actually work.