"Are you familiar with uploading your code to Google Drive?"

I left the building at that exact moment.

Dear coworker, please stop using the fucking reply all button to just send a winky face to everyone on the mailing list. I am almost to the point of just filtering all your mail to the trash because you hardly send anything relevant anyway.

This popped up at work, so I had to.

Recently made an account on Instagram.
Uploaded two pics
Deleted both of them
Now I've -2 posts

"warranty void if seal is broken"
Me: "seal isn't broken"

"This is not an application: it's a bug pretending to be an application." (This comment was left as an app review on Google Play Store)

"I can write a script to do your job"

"What took you so long to do it? It looks simple."

"It looks simple because I spent time making it simple."

New webdev job ad in a small town where I live:
"We need a junior to mid level full-stack dev - Python, Flask, Django, ES6, Angular, TypeScript, Git, etc..."
ME:
"Fuck, I tick all the checkboxes! - And it's like the only Python job around here! Yey! I so want to work with Python" excited sends cv and an extremely well crafted cover letter.
Company calls after few days:
"Hi! So we'd like to invite you for interview. Some of the tech we work in: Shopify, Wix, and SquareSpace. We're also trying to get into some other frameworks and started looking at Magento and Wordpress.... It's not really much coding, mostly content management...."

What the actual fuck!?!

I still agreed to interview...

I wonder when there will be the first manufacturer to introduce the "cool" new notch design to normal screens. 🤔

I've never had a great experience working with designers, but this one might be the laziest! Props if it's for a friend and unpaid though.

Some empty-headed helpdesk girl skipped into our office yesterday afternoon, despite the big scary warning signs glued to the door.

"Hey, when I log in on my phone, the menu is looking weird"

"Uh... look at my beard"

"What"

"Just look at this beard!"

"Uh.... OK"

"Does this look like a perfectly groomed beard"

"Uh... it's pretty nice I guess"

"You don't have to lie"

She looks puzzled: "OK... maybe it could use a little trimming. Uh... a lot of trimming". "I still like it though" she adds, trying hard to be polite.

"I understand you just started working here. But the beard... the beard should make it clear. See the office opposite to this one?"

"Yeah"

"Perfectly groomed ginger beards. It's all stylish shawls and smiles and spinach smoothies. Those people are known as frontend developers, they care about pixels and menus. Now look at my beard. It is dark and wild, it has some gray stress hairs, and if you take a deep breath it smells like dust and cognac mixed with the tears caused by failed deploys. Nothing personal, but I don't give a fuck what a menu looks like on your phone."

She looked around, and noticed the other 2 tired looking guys with unshaven hobo chins. To her credit, she pointed at the woman in the corner: "What about her, she doesn't seem to have a beard"

Yulia, 1.9m long muscled database admin from Ukraine, lets out a heavy sigh. "I do not know you well enough yet to show you where I grow my unkempt graying hairs... . Now get lost divchyna."

Helpdesk girl leaves the scene.

Joanna, machine learning dev, walks in: "I saw a confused blonde lost in the hallway, did you give her the beard speech?"

"Yeah" -- couldn't hold back a giggle -- "haha now she'll come to you"

Joanna: "No I already took care of it"

"How?"

"She started about some stupid menu, so I just told her to smell my cup". Joanna, functional alcoholic, is holding her 4pm Irish coffee. "I think this living up to our stereotype tactic is working, because the girl laughed and nodded like she understood, and ran off to the design department"

Me: "I do miss shaving though"

People who complain about wordpress have probably never tried working with Magento.

I've been going through their documentation for about 3 hours now, trying to figure out how this entire system works. And I'm no where close to understanding it...

fucking exams (._.

Attention Europeans:

Your government sucks.

In Japan, they have technical books written in comic/manga styles.

Can I somehow filter out rants containing images? My mobile internet is not that reliable and sometimes there are 30 rants with images in a row.

Also can I filter out rants with emojis? They just annoy the shit out of me

Me, doing QA

PM: "stop submitting bug reports about screen size, we're only supporting one resolution for now"

Me: *What do you mean you're only supporting one resolution it's a website and it breaks on screens <1400 px tall*
*Sigh*
"okay, what resolution?"

PM: "No one knows"

Me: *dies*

They just brought an Xbox in the office

Management : "How long you think it would take?"

Me : "now this is a rough estimate, but I think building the back-end and database alone could take 6-months minimum"

Management : "WHAT ARE YOU TALKING ABOUT? YOU ARE NOT SERIOUS"

me : "its a big proj..."

Management : "I thought it will be something like 10 days, already told the client it can be done"

me : "but we are not ready"

Management : "how are we not ready? we already have the virtual 3D shop, and we can use this ready-to-deploy eCommerce service as our data base "
... "you need to figure this out, this is not acceptable" he continued

* 2 Days Later -talking to my direct boss *
Boss : "since you don't know how to do it..."

me : "what ? I didn't say I can't do it, all I said it will take six months"

Boss : "yeah yeah, anyway there is this studio, a professional polish studio, we called them and they can do it, we will sign a contract with them, this will let you focus on the front-end. good?"

me : "well alright then"

Boss : "please write a doc, explaining everything needed from the backend"
-to me that was the end of it, took a long time to tell me they made the deal-

* 5 Months later *
- "Abdu, can you come here for a minute..."
- "yes boss?"
- "the document we asked you to do for the Polish studio, did you specify that we needed an integration with the API we are using for eCommerce?"

scared to death I answered : "why of course I did!"
I ran to my PC to check it out because I didn't know, I forgot because no one even comment on my doc. I check it out, and it was clearly explained... I got relaxed...

turns out they didn't even do what we asked them for. took them 5 months, and with no communication whatsoever. all their work was useless to us. complete dump waste.

----------------
never mentioned this until a year later... in a heat of moment when they were asking me to make an impossible task with no men and no time... I reminded them of this story... management didn't like it. but it was the truth. they didnt push this crazily this time

Meanwhile at NSA:

Alice: Uhm... Bob? I lost my SSH key...
Bob: *facepalms*
Alice: ... but i still have the public key! Could you please recalculate the private one for me?
Bob: Sure, give me a second. I'll fax it to you when it's ready.

Me: *wakes up from nightmare*

Ahem ahem.
*clears throat*

Front end bois, listen that carefully.
YOU DONT FUCKIN TELL THE BACKEND HOW TO ACCEPT REQUESTS.

Backend creates the fuckin methods, the parameters and the responses, AND YOU FUCKIN ADAPT TO IT.

This guy at my work, we are both from Uni but i picked backend because i suck at frontend and i like using backend languages, sends me a message and tells me he can't make the project work.

At this time i have almost finished my part, i have made the method, have checked that they work, and i closed the work computer.

And now he tells me he wants to make a GET request instead of POST. LISTEN HERE MOTHERFUCKER. The methods are ready, adapt to them and shut the fuck up.

And before you tell me some methods don't work, make fuckin sure your part is correct because if i boot up the work laptop again to check why the method you have told me doesn't work, and it still does the job it was intented to do but you can't fix your part, i will fuckin cut your throat.

Sucker.
I do my part, and have to study for uni exams, since you don't have to because you have passed them, do your self a favor and fuckin learn to do things.

It's not my fault that i got experience on my own while you were just only doing our uni retarded projects and didn't bother to learn anything on your own.

I don't mean by any needs that i'm better than you but fuckin accept that i have learned something else that you have not and i would like to share the knowledge with you since you didn't bother.

Currently sat in an airport writing shit code. But soon be in Italy writing shit code.

CAPTCHA meaning: "Completely Automated Public Turing test to tell Computers and Humans Apart".
Proof the the CS community is bad at creating acronyms.

ɥʇᴉʍ ʎɐld oʇ unɟ sᴉ uʍopǝpᴉsdn

Oh god where do I begin, built a JSON parser that supported comments, build a basic debug terminal for web pages, I could go on forever

Early in my career I was assigned the task of implementing a 3D pie chart into our application that you could spin and rotate with your mouse. You know, because sometimes you want to see the sides and the back of a pie chart.

There's a huge spider in my room but I'm too lazy to put it outside. I'll look into it if it's still there tomorrow.

Job title :
"PHP and MySQL Programmer"

Job description :
"We are looking for a Flash Developer with a high level of proficiency developing ActionScript solutions.... bla bla Development in a 2D and 3D environment"

doesnt say ANYWHERE what is require to know in php nor mysql

EDIT: actually it does but why would they put php and mysql programmer if thats not the main things they are looking for

My most satisfying bug fix?

I found a core concurrency issue in this gnarly homegrown ORM and reported it to the lead devs, who (very defensively, having written the damn thing) argued that it would never pop up in a prod environment and I was stupid for even bringing it up. Theoretically, this bug could cause pretty much every foreign key to be assigned to the wrong parent, but only if multiple instances of the application were open/running at once. They were so certain it would never happen on live that they explicitly instructed me not to fix it. After all, this bug had been active for many years on a previous project and nobody complained.

Problem was, that previous project was something that only a single user had open most of the time (think: a manager). The new project was something that would be used by multiple people at the same time (think: all the employees). Once we released this new-project-with-old-orm, it didn't take long at all for our customers to start complaining.

After that, they let me fix the bug. :)