I had this beautiful view from my office on Friday...😍😍😍

Internet Explorer:
You type a local IP without the protocol.
It doesn't add http automatically.
It doesn't add https automatically.
IT TRIES TO SEARCH IT ON BING

I freaking hate IE

At job interview.

They: What would you describe as your biggest character flaw?

Me: *rolls d8* I pretend not to understand the local language in order to avoid interactions I would rather not have.

They: What?

Me: ¿que?

[Client]
We've noticed we gave you the wrong product prices for our new online shop.

[Dev]
Yeah, just login to the backend and fix them.

[Client]
But we don't want to use your fancy backend, we'll be using anyway soon - we want EXCEL!
Could you send us an EXCEL, so we can fix that?
How much will this cost?

[Dev]
Sure... here you are.
Not that much, takes about an hour.

[Client]
Great, you'll hear from us in a few days.

(a few months later...)

[Client]
We've finally managed to update the EXCEL. And btw, we've also added a bunch of columns with product pictures and new properties, highlighted products to delete red, inserted some comments with manual instructions and basically destroyed the entire data structure of this table.

Before I forget... also make sure to get this finished today, we have to go live ASAP. Our marketing campaign is already live.

[Dev]
Well, I'm sorry to say this, but this is not possible.
I'm currently working on another project and it will take me hours to clean up the data you sent me, before even starting to build an import tool for the new data you provided. Better stop the campaign and I'll do my best to get this done by the end of the week. Also it may be a bit costly.

(angry client calls immediately...)

(dev transfers to manager...)

(client transfers to client's boss...)

[Manager]
Ok Dev, I think I was able to explain it to them. However, it would be great if you spend day and night to get this thing out ASAP.

[Dev]
No problem...
I'll just do it by hand to get this out immediately.

(few days later; nearly done, exhausted)

[Client]
Hey Dev, here's another EXCEL.
We've just noticed there were a bunch of errors in the previous one. Please use this instead...

I extracted a tangled action to its own api, and wrote a test for it.

The test failed.

I added debugging, more debugging, all the debugging. It still fails. But I can at least see why it fails!

It turns out the api finds and updates the wrong user. It finds and updates the wrong user EVEN WHEN THERE ARE NO OTHER USERS.

WHAT THE SALAMI.

Also, the user lookup it uses is extremely roundabout and takes several seconds with ~2 million users. Normally I'd fix the lookup, but it has been in production for several years, and I'm terrified it will break something if I fix it.

Blargherhagrid.

This is probably gona make me sound arrogant, but fuck it, you don’t know who I am, and I need to RANT!

I hate it when B.A.’s who have never studied UI or UX rail-road over my design decisions, and I just gota go along with it cos they in charge.
Then, when I make the interface the way they want it, all sorts of problems arise… Mother fucker, I saw this shit coming, and that’s why I designed it the way that I did.
Now I gota tell them how to solve the problems by doing what I originally said, and when they finally see the light, I gota waste more time re-doing the interface.
I once went through 5 fucking iterations of “Let’s try it this way”, Just to end up back with my original design spec cos these fuckers can’t even imagine what shit would look like, and how it will interact.

Now you would think after this happens a few times they would learn to trust my design skills, but noooo, Mr B.A. has to piss all over my ideas every time.
And every FUCKING time, we end up going back to what I originally proposed…
Learn your fucking lesson dumb ass!!!

*drops mic & goes straight to the bar*

Gotta love going to a support forum and going through three pages of literally nothing but "I'm having this issue too" with 0 input on fixing said issue.

Fucking lovely

Me: *Watching a movie*

Main Character: "Oh no, we have to hack the CIA to figure out how this machine works! Hacker girl, do the stuff"

Hacker Girl: "Consider it done!"

Hacker Girl: *Opens Linux bash*

Hacker Girl: *types 'mkdir Hack_CIA'

Hacker Girl: "They have two-factor authentication in place, this is going to be a hard one."

Hacker Girl: *Types 'cd Hack_CIA'*

Hacker Girl: "I'm in!"

Me: "..."

Friend: "Wow, so well done, so realistic!"

Me: *Dies*

[Thursday afternoon on a call...]

Client: Before we get started, can you create a sitescape outlining all of the pages and sections of the new website?

Me: Sure! I'll go through the website and shoot you a full layout in xls format as soon as possible, that way you can easily make notes on what you want added, modified or removed.

[Two hours later...]

Client: Hey, did you build that sitescape yet?

Me: Actually, I've been on back-to-back calls with other clients.

Client: So when are you going to get it done?

Me: Well, I have to go through the current website in it's entirety, which I'm guessing is about 1,000 pages. I have to determine which pages work fine on their own, which need to be combined for better presentation and which should be removed due to redundancy. That's something that is tedious and takes some time to complete. That, in combination with having an existing work queue that I need to fit you within and being at the end of the work week, we're looking at Tuesday morning to have it ready.

Client: "Existing work queue"? This is ridiculous. We're paying you good money to make our project your only priority. If we wanted to wait days for work, we would have saved money and paid for a cheaper service. You're already gouging us as it is! If we don't get the sitescape by end of day Friday, we're going with another company.

Me: I would tell you that I'm sorry for the inconvenience, but I'm not. I'm not going to feed you a line to make you happy. I'm also not going to work on my days off just to rush something out to you. You hired us because you wanted things done right, not quickly. Your current website is the result of not focusing on quality, but by how fast you can deliver it. We don't work that way. We only build quality products.

By rushing your project, not only do we alienate our current clients, affecting our reputation, but we build product of less than the highest quality. That will upset you because it isn't perfect, and it reflects poorly on us to use it in our portfolio.

If you want to hire someone to pump out this project to your unrealistic deadlines, be our guest. But you paid a 50% non-refundable deposit, so not only will you lose money, but your end product will suffer.

I'm going to let you sleep on this. If you decide tomorrow that another direction is the way to go, we wish you luck. But please understand that if we conclude our business, we will no longer make ourselves available for your needs.

Please find the attached contracts you have signed, acknowledging the non-refundable deposit, as well as the project timeline and scope, of which a "sitescape" was never originally mentioned or blocked out for time.

I hope that tomorrow we can move forward in a more professional manner.

[Next morning...]

Client: My apologies for yesterday. We're just very anxious to get this started.

-----

Don't let clients push you around. Make them sign a contract and enforce it whenever necessary.

Client: Can you build a Snapchat clone but better?

Me: I’m going to say probably not logical given the resources they have and what we have, but for curiosity, what kind of budget do you have?

Client: $2500.

Me: Get out.

Client: Where are we with the project, it's been a week and I see nothing.

Me: You asked me to do something that was not in the agreed scope of work, which has kept me from starting on the project.

Client: Do I need to plan out everything in advance on paper for you to get it done in a timely manner?

Me: Is that a serious question? Yes, you should. That's the whole point of creating a scope of work. It's to allow me to schedule out the time necessary to build out a product in a "timely manner".

Client: I don't appreciate your attitude. This is not how you should be doing business if you like making money.

Me: I don't appreciate your condescending, unreasonable, dickhead mentality that makes you think it's remotely okay to act like you're better than me. Money doesn't grant you the right to be a dickwad, and just because I'm being paid doesn't mean I have to put up with any level of arrogance or disrespect.

I am in this business to make money, but not at the cost of my dignity and self-respect. You will be receiving a full refund later today, not because I have to provide a refund, but because I never want to communicate with you ever again moving forward. Take your unacceptable bullshit somewhere else.

I just had a client complaining on the phone that she read my database design documents and that they are all wrong and need to be done again. Because things like varchar and int are confusing. And nobody understands what they mean. She asked around and nobody understood it.

Ooh, and I should place the customer name in more then one table because it would be handy to have in several places.

Spend a hour on the phone trying to explain that these documents are not intended for her. They are not for her to understand.

I make these documents to build a stable product and in case something bad happens to me its easier to pick up for another developer.

Long story short.. I'm currently making a document that explains the database design... Getting paid for it..... But fucking hell. Somebody save me.

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