I just saw a news article (nope, not sharing it...don't want them to get the clicks) where they said it's now considered passive-aggressive to use the following emojis (the percentage is a non-specific n-value and N-value...probably 3...of how many younger folks think it makes you look "old" to use these):
1 - Thumbs up - 24%
2 - Red love heart - 22%
3 - OK hand - 20%
4 - Tick - 17%
5 - Poo - 17%
6 - Loudly crying face - 16%
7 - Monkey eye cover - 15%
8 - Clapping hands - 10%
9 - Lipstick kiss mark - 10%
10 - Grimacing face - 9%

I previously only ever used thumbs-up and checkmarks to signal that I understood the message sent to me. My new goal is to use as many of these as possible when messaging anyone under 30. If you are so butthurt by ANY emoji, then you certainly deserve what's coming to you.

So, I got this new coworker of mine, he's 5 years older than me and says he's got a loooot of experience with html, css und javascript. Nice. Boss wants us to blur some text on a website, I show him how to do it with css "filter: blur(4px)".

5 minutes later he's all proud and says "done". I think nice, check the code - and see this moron having put an <img> png in there, having blurred the text with photoshop. Short memory, anyone?

Jesus fuckin Christ!!!!

This Iran situation is getting out of hand on the internet!! You have IRGC members publicly try to terrorize people through social media! I checked out some posts on insta, following their hashtags in their language, and then ended up in one weird account posting severed heads! Like, what the absolute fuck???

I know people who own social media platforms are not responsible, but fuck I am terrorized to my bones right now! How does the algo not stop this shit?

Can we talk about something? I can't be the only one...

Code dreams.

What are they? You either sleep poorly, lightly, or not at all and continually repeat nonsensical code that you would otherwise KNOW is wrong when awake, (and it may even be a problem you already solved!) but for some reason your brain just wants you to mull over it over and over again.

I've been free of them for quite some time, but it happened now the past two nights. Drives me fucking nuts.

Me: So you have no work experience, and majored in liberal arts, but you did go through a 6 months bootcamp, right?
Candidate: Yeah.
Me: sounds good, we will have to work together with you for a long while until you become independent, but I think you can definitely do this. What are you salary expectations?
Candidate: I'm thinking of 5000.
Me: Aight, thanks for your time! We'll send you more details later

Around here, 5000 (arbitrary made up number) is what you pay someone with around 3 years of experience at least. It's always these pampered fucks from rich countries that want to earn a shitton of money for the grand effort of going to a goddamn bootcamp for some months. That is their definition of effort and hard work, because it seems they've never once in their lives had any sort of hardship or struggle beyond crying that dad got them an Android instead of an iPhone. If you leave them alone they can't do jack shit because they've never worked in real, big projects, so you gotta invest a lot of time in them. Which is fine, everyone starts from somewhere. But what kinda balls do you have to demand a mid level salary when you have done basically nothing so far, and your knowledge is superficial at best?

I know that a lot of jobs and recruiters give bottom of the barrel shit, but I swear some candidates are insane. Unpopular rant I assume but I just needed to scream a bit.

A conversation that me and my boss had this week:
Boss: "Hey, why is this not progressing"
Arcsector: - "We're waiting on system users to move their destinations"
"We need the system in the database in order to move it"
- "Okay awesome - let's move it, oh wait, I can't do it because I don't have access, here's the stuff that needs to be done: a, b, and c"
"Oh I'm actually not able to help with that"
- "So then how are we supposed to get it done?"
"idk but also this other issue is something missions are complaining about"
- "oh I already am talking to them about it and it should be remedied by the team creating the problem because it's a false positive"
"Well we need to solve it still"
- "We would've solved it already but it has dependencies with other projects that we're still working on because we don't have enough people"
"We cant get you more people because we don't have the budget"
- "Then this stuff will have to wait"
"Get it done"

ACTUALLY SCREAMING! Why cant people understand that there are conesequences for their actions??!!

It's been 6y since i created a devrant account, and went from a college kid to a dev lead, so much changed and i use my old posts as a window to the young me.

I am working my dream job, yet it feels like a nightmare.
The young me would give an arm and a leg for this position, and here i am feeling like this is worthless.

If any of you guys experienced something like this, would love to hear what it took to go back to feeling excited to code.

I met a rather talented developer some time ago that is highly proficient in C# as well as React and Angular for the creation of web programs.
Dude knows the ins and outs of C#, has been working on it since the early stages of ASP.NET.

I am always intrigued as to why certain people chose certain languages. When I asked him, he admitted to being very lost during his early days, and somehow settled on C# because of the file extension being cs, which made him think that it was the proper Computer Science programming language, get it? because of CS?

Now a days he does use a wide variety of stacks and languages, and he keeps up to date, not one of those "I don't need to learn anything new!" types of developers, the dude is absolutely l337, but i keep thinking that such a talented developer had such a funny start.

ARGH. I wrote a long rant containing a bunch of gems from the codebase at @work, and lost it.

I'll summarize the few I remember.

First, the cliche:
if (x == true) { return true; } else { return false; };
Seriously written (more than once) by the "legendary" devs themselves.

Then, lots of typos in constants (and methods, and comments, and ...) like:
SMD_AGENT_SHCEDULE_XYZ = '5-year-old-typo'

and gems like:

def hot_garbage
magic = [nil, '']
magic = [0, nil] if something_something
success = other_method_that_returns_nothing(magic)
if success == true
return true # signal success
end
end

^ That one is from our glorious self-proclaimed leader / "engineering director" / the junior dev thundercunt on a power trip. Good stuff.

Next up are a few of my personal favorites:

Report.run_every 4.hours # Every 6 hours
Daemon.run_at_hour 6 # Daily at 8am

LANG_ENGLISH = :en
LANG_SPANISH = :sp # because fuck standards, right?

And for design decisions...

The code was supposed to support multiple currencies, but just disregards them and sets a hardcoded 'usd' instead -- and the system stores that string on literally hundreds of millions of records, often multiple times too (e.g. for payment, display fees, etc). and! AND! IT'S ALWAYS A FUCKING VARCHAR(255)! So a single payment record uses 768 bytes to store 'usd' 'usd' 'usd'

I'd mention the design decisions that led to the 35 second minimum pay API response time (often 55 sec), but i don't remember the details well enough.

Also:
The senior devs can get pretty much anything through code review. So can the dev accountants. and ... well, pretty much everyone else. Seriously, i have absolutely no idea how all of this shit managed to get published.

But speaking of code reviews: Some security holes are allowed through because (and i quote) "they already exist elsewhere in the codebase." You can't make this up.

Oh, and another!
In a feature that merges two user objects and all their data, there's a method to generate a unique ID. It concatenates 12 random numbers (one at a time, ofc) then checks the database to see if that id already exists. It tries this 20 times, and uses the first unique one... or falls through and uses its last attempt. This ofc leads to collisions, and those collisions are messy and require a db rollback to fix. gg. This was written by the "legendary" dev himself, replete with his signature single-letter variable names. I brought it up and he laughed it off, saying the collisions have been rare enough it doesn't really matter so he won't fix it.

Yep, it's garbage all the way down.

I was on vacation when my employer’s new fiscal year started. My manager let me take vacation because it’s not like anything critical was going to happen. Well, joke was on us because we didn’t foresee the stupidity of others…

I had to update a few product codes in the website’s web config and deploy those changes. I was only going to be logged in for 30 minutes to complete that.

I get messaged by one of our database admins. He was doing testing and was unable to complete a payment on the website. That was strange. There was a change pushed by our offsite dev agency, but that was all frontend changes (just updating text) and wouldn’t affect payments.

We don’t want to enlist the dev agency for debugging work, especially when it’s not likely that it’s a code issue. But I was on vacation and I couldn’t stay online past the time I had budgeted for. So my employer enlists the dev agency for help. It’s going to be costly because the agency is in Lithuania, it was past their business hours, and it was emergency support.

Dev agency looks at error logs. There are Apple Pay errors, but that doesn’t explain why non Apple Pay transactions aren’t going through. They roll back my deployment and theirs, but no change. They tell my employer to contact our payment processor.

My manager and the Product Manager contact Payroll, who is the stakeholder for our payment gateways. Payroll contacts our payment gateway and finds out a service called Decision Manager was recently configured for our account. Decision Manager was declining all payments. Payroll was not the person who had Decision Manager installed and our account using this service was news to her.

Payroll works with our payment processor to get payments working again. The damage is pretty severe. Online payments were down for at least 12 hours. Our call center had logged reports from customers the night before.

At our post mortem, we had to find out who ok’d Decision Manager without telling anyone. Luckily, it was quick work. The first stakeholder up was for the Fundraising Dept. She said it wasn’t her or anyone on her team. Our VP of Analytics broke it to her that our payment processor gave us the name of the person who ok’d Decision Manager and it was someone on the Fundraising team. Fundraising then starts backtracking and says that oh yes she knew about it but transactions were still working after the Decision Manager had been configured. WTAF.

Everyone is dumbfounded by this. How could you make a big change to our payment processor and not tell anyone? How did our payment processor allow you to make this change when you’re not the account admin (you’re just a user)?

Our company head had to give an awkward speech about communication and how it’s important. The web team can’t figure out issues if you don’t tell us what you did. The company head was pissed because it was a shitty way to start off the new fiscal year. Our bill for the dev agency must have been over $1000 for debugging work that wasn’t helpful.

Amazingly, no one was fired.

!!fml

"Root, go fix this bug. It'll take you two days."

The "bug" is a feature that was never implemented for one particular payment type.

The code in question is two years old, full of typos, smells, junior-isms, and is convoluted AF. The feature's commit touched 190 files and implemented many other features as well. Thus far, I have been unable to narrow down where this particular feature's code lives for the other payment types, nor which code or payment paths lead to it. Burned out, I can barely focus on the screen, let alone follow its many twisting and dynamically-inferred paths. I hint as to the ticket's scavenger hunt nature during standup.

"But I wrote comments on the ticket telling you exactly where to look to fix it," Thundercunt admonishes in front of the team.

"Sure, you did," Root replies. "You reworded what the original dev had said in the comments 20 minutes prior, and agreed with him. His comments were helpful, but it doesn't tell me how any of it works," she continues.

TC scoffs and closes the meeting.

Root stares blankly, seeing neither code nor screen, questions her life decisions, and recalls the previous tickets she has worked on: nearly every one of them busywork, fixing other people's bugs. Bugs she never could have gotten away with if she tried.

"Why do I put up with this?" She asks. "They don't care, and it's killing me."

But the bills remain, and so must she.

"Fuck my life" she finally decides.