I'm writing my bachelor thesis in LaTeX. As people who use LaTeX might know, it generates shitloads of files while compiling (like 10 files per .tex file).
To unclutter my project folder, I wrote a simple one-liner bash script that deletes all files which are not .tex or .bib files (literature references) and of course it will not delete itself (although that one also took me longer to figure out why my script 'kept disappearing for no reason after I ran it' than I'd like to admit).

However, I forgot that images are also files which are stored in the project-folder.
And this is how I suddenly lost all of my images for no reason at all, resulting in my PDF not building anymore. Luckily we all commit and push all regularely, right...

Edit: I just figured out that I'm even stupider than originally thought... My .gitignore ans more importantly, the '.git' folder also neither end in .tex nor .bib. Guess I'll just go fuck myself.

Is anybody aware of some tecnique to install Visual Studio without having it to dump like 20Gb of useless garbage in unforeseeable locations of your hard drive?

what you think about that?

A Gentoo installation might be fun, but it sure as hell isn't worth it, both in time and effort. Broken audio, broken video, broken stability. A broken kernel that doesn't recognize the hard drive or the network interface. And half a week to compile the fucking thing and it's still not done. This is not the right distribution for me.

Taking a 4 day vacation from coding at work sure is great.

When a hiring manager wants 5+ years experience in Swift.

Swift release date = June 2, 2014

😂👍🖕

"You gave us bad code! We ran it and now production is DOWN! Join this bridgeline now and help us fix this!"

So, as the author of the code in question, I join the bridge... And what happens next, I will simply never forget.

First, a little backstory... Another team within our company needed some vendor client software installed and maintained across the enterprise. Multiple OSes (Linux, AIX, Solaris, HPUX, etc.), so packaging and consistent update methods were a a challenge. I wrote an entire set of utilities to install, update and generally maintain the software; intending all the time that this other team would eventually own the process and code. With this in mind, I wrote extensive documentation, and conducted a formal turnover / training season with the other team.

So, fast forward to when the other team now owns my code, has been trained on how to use it, including (perhaps most importantly) how to send out updates when the vendor released upgrades to the agent software.

Now, this other team had the responsibility of releasing their first update since I gave them the process. Very simple upgrade process, already fully automated. What could have gone so horribly wrong? Did something the vendor supplied break their client?

I asked for the log files from the upgrade process. They sent them, and they looked... wrong. Very, very wrong.

Did you run the code I gave you to do this update?

"Yes, your code is broken - fix it! Production is down! Rabble, rabble, rabble!"

So, I go into our code management tool and review the _actual_ script they ran. Sure enough, it is my code... But something is very wrong.

More than 2/3rds of my code... has been commented out. The code is "there"... but has been commented out so it is not being executed. WT-actual-F?!

I question this on the bridge line. Silence. I insist someone explain what is going on. Is this a joke? Is this some kind of work version of candid camera?
Finally someone breaks the silence and explains.

And this, my friends, is the part I will never forget.

"We wanted to look through your code before we ran the update. When we looked at it, there was some stuff we didn't understand, so we commented that stuff out."

You... you didn't... understand... my some of the code... so you... you didn't ask me about it... you didn't try to actually figure out what it did... you... commented it OUT?!

"Right, we figured it was better to only run the parts we understood... But now we ran it and everything is broken and you need to fix your code."

I cannot repeat the things I said next, even here on devRant. Let's just say that call did not go well.

So, lesson learned? If you don't know what some code does? Just comment that shit out. Then blame the original author when it doesn't work.

You just cannot make this kind of stuff up.

"A different error message! Finally some progress!"

A young guy I work with burst into tears today, I had no idea what happened so I tried to comfort him and ask what was up.

It appears his main client had gone nuts with him because they wanted him to make an internet toolbar (think Ask.com) and he politely informed them toolbars doesn't really exist anymore and it wouldn't work on things like modern browsers or mobile devices.

Being given a polite but honest opinion was obviously something the client wasn't used to and knowing the guy was a young and fairly inexperienced, they started throwing very personal insults and asking him exactly what he knows about things (a lot more than them).

So being the big, bold, handsome senior developer I am, I immediately phoned the client back and told them to either come speak to me face-to-face and apologise to him in person or we'd terminate there contract with immediate effect. They're coming down tomorrow...

So part my rant, part a rant on behalf of a young developer who did nothing wrong and was treated like shit, I think we've all been there.

We'll see how this goes! Who the hell wants a toolbar anyway?!

!rant

I've completely switched to drinking water since a few weeks and I feel much better than I used to, that might ofcourse be a placebo effect but it helps either way.

Last time I tried a Fanta at a party almost couldn't finish it because of the amount of sugar. Now I'm only used to having sugar in a cappuchino.

I'd encourage others to try the same 🤩

Qin Chen, a 38 year old facebook employee, recently committed suicide and facebook is trying really hard to hide this.

Apparently he was too stressed out at work and was trying hard to steer things his way, he almost succeeded, but then his manager backstabbed him and left him helpless.

Instead of promoting a better work culture and taking steps against such malpractices at workplace, facebook is trying to hide this incident.

Facebook has to realize that them behaving this way not only insults the departed and his family, but also raises a question that is the life of any of their current employees of any value to facebook, or do they just look at them like workforce and not humans?

Let us not be silent. It was Chen yesterday, it could be any one of us tomorrow.

Not me but my husband @WhAtEvErYoUmEaN keeps updating our pillows, doesn't like certain customer servers and tends to tell our cats to get a job/ point them to job counseling.