My coworker wanted to get some program from a website that requires a username/password to download. It is a utility program for controls automation. He didn't want to have to create a username/password so I said he could use mine.

I went over to his desk and read off the username to him which he entered. Then I started reading off the "password" to him:
"y o u r m o m i s a s l u t"
He got suspicious at the last few letters and then clicked on "show password" icon. He of course saw: "yourmomisaslut". At this point he just bust out laughing. I then gave him the correct password.

Opened a legacy PHP file from 2008.

No functions.
2,000+ lines.
Inline SQL.
HTML inside echo statements.
A single if (true) wrapping the entire thing like some cursed gift box.

At the top:
// Do not modify. Works perfectly.

At the bottom:
It writes to two databases. Only one exists.

Somewhere in the middle:
It sends an email…
to the client’s ex-wife.

I closed the file.
Rebooted my laptop.
Took a walk.
Still not okay.

"We really struggle to find people with this skil set"

So you're going to hire me, pay well, and not be full of shit, right?

dev communities can be the most toxic as well as the most welcoming at the same time.

just depends on what your timing is. You can get a bunch of links to help debug your issue or you can get told to "kill yourself".

You never know.

Anyone else just randomly hit Help > About on programs when you’re bored?

Shit.

Thought I had turned off the stove after making dinner but seems it stayed on.

Thankfully the kitchen automatically turns off after a set time, so only the pan and a couple nearby things were lost.

Still, seems some electric wire in the extractor got wrecked because the kitchen line breaker is down and won't go up.

Waking up to your house full of smoke really sends you into panic mode...

In my latest installment of "Swift, WTF?", we look at the "if" conditional in terms of the Swift convention of:

if let x = y { /* ... */ }

so what this does :
1. declares x in the scope of the braced code
2. sets x to y (an ahem, "optional")
3. decides if x is not *nil*, then executes the braced code.

This is very similar in both the visual and the operation to the C code of:

if (int x = y) { /* ... */ }

1. declares x in the scope of the braced code
2. sets x to the value of y
3. if x is not zero, then executes the braced code

which is considered *exceptionally* poor style.

Neither the C nor the Swift construct result in a legitimate boolean value of "true" or "false", although C comes closer than Swift.

In the Swift case the *imaginary* "nil" value has to be interpreted as "false" and thus there must be extra code is for the conditional to check on whatever constitutes the **actual** value of nil in Swift and then set the condition to "false".

(remember boys and girls, "optionals" are not real, they are an imaginary language construct of Swift and have no legitimate counterpart in the CPU operations with memory and registers)

At least in the case of C, if the value of x is zero or NULL (which is 0) then it is technically a "false" which in C is 0. Regardless, it is really poor programming and anyone doing that on my team gets an ear full.

But in Swift this obfuscation of code is common and condoned! Well, why not put more of the program in the condition of the if? In fact, stuff the whole thing in there.. why not? 🙄

This just reenforces my opinion that Swift is not a bird but the stuff that comes out of the underside of the bird. 🐦💩

I meant to upload this Reddit post from r/TrueOffMyChest as an image, but apparently that feature is broken. So I transcribed it. This rant writes itself. It's absolutely discrimination and by consent of the state. This, plus age and viewpoint discrimination, is why I own and operate my own business. I refuse to be beholden to HR assclowns trying to virtue signal their way into their next promotion.

"So I did an experiment, I work in CS and decided to test what the gender bias is. So I took my CV And changed the name to a female name. I'd send it out with my real name, then a few days later (or few days before) with a female name.

Out of 100, my applications with a male name got 7 responses for interview.

Out of 100, my applications with a female name got 45 responses to interview

The female resume was 650% more likely to get a callback. And the resumes were identical.

So then I thought 'what about someone looking for working class jobs?' So I decided to focus on restaurants-servers, hosting, etc. Made a fake resume, and responded to craigslist ads with both male and female names. Sometimes the male went first, sometimes the female went first.

Out of 100, my applications with a male name got 10 responses to interview

Out of 100, my applications with a female name got 87 responses to interview

The female resume got 870% more responses."

when you're adding whiskey to your coffee during work hours, you know you really should find a new job.

when you end up in the ER with excruciating pain early on a Saturday morning from persistent inflammation from chronic job stress and getting sick more than normally, you gotta change jobs.

no amount of money is worth your health.

(the drugs they gave me were pretty fun though, but not something I ever want to go through again)

Devrant not loading again... hit refresh... still nothing... is today the day it finally snuffs it?

Sigh with relief as the UI starts to load...

And there it is: a lengthy ode to the best pest control service in Hockaloogie, Alabama.

The natural balance of the universe has been restored.

Having no say in your own work and everything being decided AFTER THE MERGE REQUEST is really interesting.

Preparing my 2 week notice.

In modern C#, everything's an interface.

Zig is actually sort of similar. I guess I owe it to C# for teaching me the magic.

Sorry, I mean:

IZig is IActually ISort of ISimilar. (IContinued...)

You know what I find truly despicable? Consultants who grossly over-sell worthless digital products.

Take a guy who throws together 2 text boxes and a list in Figma and calls it: "The disruptive platform that will solve all your problems at once today!". Are you fucking kidding me? Such an insult to people's intelligence.

There is a saying: "A salesman will sell you a dirty cloth for the price of a house".

I was cited in a decent-ish journal article.
Feels like a win.

devrant cert expired

Am I in a toxic work environment or not?

1. I suggested implementing some code guidelines for our team so we can all work the same way. Lead architect sends me a DM telling me to stop talking about it until after projectX is done because it might stress out other devs. Friday he talks about how important it is to use standardised tools and ways of doing things.
2. Spent a week working on a bug fix and they said solution is good, but then invalidated all of my work by DM-ing me saying it's unusable because i worked on wrong branch and he quickly fixed it over the weekend and I should just copy his (inefficient) code.
3. I ask him a basic question of what version the backend software is using and he doesn't even respond. I ask another team member who quickly helps me check. it would have taken 1 fucking integer to answer that question. i wanted to learn the backend stack, but not so much anymore.
4. Lead doesn't respond to project management software ticket mentions.
5. Lead randomly makes hotfixes to the QA server without prior notice so the backend randomly goes down at times during work hours and then my local copy of the front end stops working for no reason at all when I am trying to focus on bug fixes
6. UX/UI designer's screen designs look completely different than the actual app, so I spent weeks implementing a feature looking like his nice designs, then having to change it again, taking another week.
7. Generally poor comms
8. Leadership mentioned jobs are safe, then 2 months later retrenched a bunch of people.
9. People getting sick all of the time.
10. Nobody gives a shit about technical debt

I hate deprecations! Adopted a web project that was actively maintained until 2023, how can it already be so "legacy" that none of its npm scripts work anymore?

Yeah turns out writing a shell is a whole lot more work than I thought

Fuck man, why can't I just find a cool project that is actually doable in a normal lifetime

somewhere out there, there's a person who ate more mayonnaise than any other person.