So that coworker of mine who got promoted to manager keeps continuing on abusing her new power. She convinced upper management to implement a new policy where you would be disqualified from your monthly performance incentives if you take 2 total sick days a month. She says this is to reduce the number of sick days people take, which of course upper management loved hearing.

By the way, since she's a manager now, this particular policy doesn't affect her - it only applies to us in the trenches. She can still take as many sick days as she wants, since being a manager she can work from home.

Needless to say, save for a couple of suck-ups, she's lost a lot of friends and made a number of enemies in our department, particularly on our dev team.

Holy fucking cockgoblin!

If you interview for a senior position, please, for the sanity of your interviewer (me), make sure you know how to declare variables and how to iterate over an array in the language which the shitgoblin (you) "love and use all the time".

Of course the interviewer (me) is gonna be polite and let the shitgoblin (you) code out your 50-line solution for a 3-line problem, but after 2 hours watching the shitgoblin contemplate solutions that anyone who ever opened a fucking beginners tutorial by accident could answer, the interviewer might prefer to have been on a Justin Bieber concert or have sucked huge sweaty ballsacks for those two hours.

I know that interviews can be hard and stressful - I've been there, am there, and at some point will be there again - but please, for the love of nonexistent gods, don't be a time-wasting shitnugget but prepare yourself!

Yesterday: Senior dev messages out a screenshot of someone using an extension method I wrote (he didn’t know I wrote it)..

SeniorDev: “OMG…that has to be the stupidest thing I ever saw.”
Me: “Stupid? Why?”
SeniorDev: “Why are they having to check the value from the database to see if it’s DBNull and if it is, return null. The database value is already null. So stupid.”
Me: “DBNull is not null, it has a value. When you call the .ToString, it returns an empty string.”
SeniorDev: ”No it doesn’t, it returns null.”
<oh no he didn’t….the smack down begins>
Me: “Really? Are you sure?”
SeniorDev: “Yes! And if the developer bothered to write any unit tests, he would have known.”
Me: “Unit tests? Why do you assume there aren’t any unit tests? Did you look?”
<at this moment, couple other devs take off their head phones and turn around>
SeniorDev:”Well…uh…I just assumed there aren’t because this is an obvious use case. If there was a test, it would have failed.”
Me: “Well, let’s take a look..”
<open up the test project…navigate to the specific use case>
Me: “Yep, there it is. DBNull.Value.ToString does not return a Null value.”
SeniorDev: “Huh? Must be a new feature of C#. Anyway, if the developers wrote their code correctly, they wouldn’t have to use those extension methods. It’s a mess.”
<trying really hard not drop the F-Bomb or two>
Me: “Couple of years ago the DBAs changed the data access standard so any nullable values would always default to null. So no empty strings, zeros, negative values to indicate a non-value. Downside was now the developers couldn’t assume the value returned the expected data type. What they ended up writing was a lot of code to check the value if it was DBNull. Lots of variations of ‘if …’ , ternary operators, some creative lamda expressions, which led to unexpected behavior in the user interface. Developers blamed the DBAs, DBAs blamed the developers. Remember, Tom and DBA-Sam almost got into a fist fight over it.”
SeniorDev: “Oh…yea…but that’s a management problem, not a programming problem.”
Me: “Probably, but since the developers starting using the extension methods, bug tickets related to mis-matched data has nearly disappeared. When was the last time you saw DBA-Sam complain about the developers?”
SeniorDev: “I guess not for a while, but it’s still no excuse.”
Me: “Excuse? Excuse for what?”
<couple of awkward seconds of silence>
SeniorDev: “Hey, did you guys see the video of the guy punching the kangaroo? It’s hilarious…here, check this out.. ”

Pin shoulders the mat…1 2 3….I win.

My friend said this,

Roses are red,
The screen turned blue,
I'm not a programmer,
What the fuck do I do.

I'm sorry for your eyes

A client’s server crashed so they called us. When we checked the logs we found a user was logged in 200,000+ times. We told them the user and a few minutes later we get a picture of a cupcake that was on the enter key. They got cupcake DOS attacked. My team isn’t in charge of the login functionality but I can say the team that is got a fairly aggressive internal support ticket.

Meditation for the rest of us...

Boss: “Our YouTube channel doesn’t look at all like our website.”

Me: “I’ve made it look as close to our branding as YouTube allows for with its limited editing controls.”

Boss: “This is unacceptable. I expected more from you.”

Me: “I cannot accept the blame for this. YouTube is setting the design parameters for all channels and I can only do so much.”

Boss: “You can call the YouTube, can’t you? Why didn’t you call them?”

Me: “.......and ask them....what?”

Boss: “You don’t ask! You tell! Our company has been around for 140 years. Our brand name carries that weight. They’ll change their design to what we need if you’re assertive enough.”

Me: “Ma’am, that’s just not how this works. That’s not how any of this works.”

"my app is so awesome you don't even have to close it, it crashes itself automatically. "

Me: 1 is something, 0 is nothing, NULL is the absence of things
JuniorDev: wut
Me: You've got pizza in a box, that's 1. If there's no pizza in the box, that's 0. If there's no pizza and no box, that's NULL.
JuniorDev: OOH so there's no object to reference if I ask for a slice!
Me: *small tear*

Always explain things in terms of pizza. Always.

- Sir, you must put away your laptop before the flight takes off.
- Is a tablet okay?
- Yes
- *Uncouples keyboard from Surface*
- ಠ_ಠ
- (⌐■_■)

Developer: We have a problem.
Manager: Remember, there are no such things as problems, only opportunities.
Developer: Well then, we have a DDoS opportunity.

"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.

Client: We have a HUGE security problem.

Me: *thinks about any possible vulnerabilities* What is it?

Client: A user can take a picture of our website and steal our content.

I’m done for today.

This is what happens when you listen to clients