Boss: "I don't want to comply with the GDPR"

Me, DPO: "I've told you the house rules. You must comply, stop arguing"

Boss: "But I don't want it. Bobby doesn't have to, and Eve doesn't have to, their moms are cool"

Me: "I don't give a crap about the other kids, you're going to be GDPR compliant. Bob and Eve will end up being raped in prison. It's that what you want?"

Boss: "What if I just pretend to do it."

Me: "I'll take away all your marketing toys. No more mailchimp for you young man."

Boss, crying: "You wouldn't touch my Facebook pixel!"

Me: "Especially your Facebook pixel. I'm so sick of that thing...."

Me: "...Look, you can still play with your toys, all I'm saying is you need to be honest and ask your buddies for consent before you put your pixels up their various holes"

Boss: "But they will never agree!"

Me: "Maybe that is good thing"

Boss: "But how will we get people to like us if I can't feed them pills and insert probes into their holes to measure their responses?"

Me: "Maybe you should focus on being a nice kid, someone people like to play with. Your buddies will tell other kids that you're a nice guy. Now, I'm not going to lie to you, it will be hard work. Much more effort than what you're doing now. But you know, those friends will stick with you for decades, instead of just until the marketing-drugs wear off"

Boss: "I think I want a new mom"

Me: "You signed a contract. You're stuck with me for the next 2 years. And as long as you're living under my roof, you will follow my rules."

New devComic! Based on a funny rant by @AlgoRythm (https://devrant.com/rants/1168834/)

3 years ago.....

*lunch break. In a table with 2 other co-workers*

Me: "I am going to quit today!"
Co-worker 1: "What? I am going to do that today too!"
Co-worker 2: "Are you serious? I was planning to do that too today!"
Me: "Holy cow! Let's do that today the three of us, but I am going last one. I want to see his face (our CEO)".

After couple of minutes and disagreement, we agreed to do that.

When I told him (I was the last to tell himm), he was sweating and his face was red. Started to throw offensive words towards me. I was expecting that and came prepared. BUT, in the middle of his words saying "I hire you because no one would hire you" etc, quietly and with a smile on my face, I interrupted him saying, "Look, is this going to take long? Because I gotta go somewhere and I am not in the mood to listen to you!"

He started to shake from that rage he had inside him. I know he wanted to punch me. But nothing happened.

I still remember his face like it was yesterday. :P

Epilogue:
My aunt's husband and him were best friends. He called him saying what happened. Of course, I was the one to blame. Since my parent knew what kind of guy he is, they told me "You did good for being quiet, not screaming and not acting like a child!"

When enraged keyboard smashing works

Stallman heart failure recipe:

1. Start your UBUNTU LINUX(don't add the GNU part) and set up your .NET Core environment.

2. Download VS Code, the superior text editor for those that do not wish to have carpal tunnel.

3. Open the terminal inside your VS Code instance while inside a .net core project.

4. Type emacs -nw and watch emacs come to life inside of the terminal while living inside of the heretic vs code editor.

Wait for stallman to get a heart attack or a stroke from this.

In Europe, we use € instead of $ in jQuery.

thats how I will handle IE support in the future ^^

As a developer, sometimes you hammer away on some useless solo side project for a few weeks. Maybe a small game, a web interface for your home-built storage server, or an app to turn your living room lights on an off.

I often see these posts and graphs here about motivation, about a desire to conceive perfection. You want to create a self-hosted Spotify clone "but better", or you set out to make the best todo app for iOS ever written.

These rants and memes often highlight how you start with this incredible drive, how your code is perfectly clean when you begin. Then it all oscillates between states of panic and surprise, sweat, tears and euphoria, an end in a disillusioned stare at the tangled mess you created, to gather dust forever in some private repository.

Writing a physics engine from scratch was harder than you expected. You needed a lot of ugly code to get your admin panel working in Safari. Some other shiny idea came along, and you decided to bite, even though you feel a burning guilt about the ever growing pile of unfinished failures.

All I want to say is:

No time was lost.

This is how senior developers are born. You strengthen your brain, the calluses on your mind provide you with perseverance to solve problems. Even if (no, *especially* if) you gave up on your project.

Eventually, giving up is good, it's a sign of wisdom an flexibility to focus on the broader domain again.

One of the things I love about failures is how varied they tend to be, how they force you to start seeing overarching patterns.

You don't notice the things you take back from your failures, they slip back sticking to you, undetected.

You get intuitions for strengths and weaknesses in patterns. Whenever you're matching two sparse ordered indexed lists, there's this corner of your brain lighting up on how to do it efficiently. You realize it's not the ORMs which suck, it's the fundamental object-relational impedance mismatch existing in all languages which causes problems, and you feel your fingers tingling whenever you encounter its effects in the future, ready to dive in ever so slightly deeper.

You notice you can suddenly solve completely abstract data problems using the pathfinding logic from your failed game. You realize you can use vector calculations from your physics engine to compare similarities in psychological behavior. You never understood trigonometry in high school, but while building a a deficient robotic Arduino abomination it suddenly started making sense.

You're building intuitions, continuously. These intuitions are grooves which become deeper each time you encounter fundamental patterns. The more variation in environments and topics you expose yourself to, the more permanent these associations become.

Failure is inconsequential, failure even deserves respect, failure builds intuition about patterns. Every single epiphany about similarity in patterns is an incredible victory.

Please, for the love of code...

Start and fail as many projects as you can.

I just noticed my file is named home.less
Poor

Seriously?? Is it really available??

Google => googled

Duck duck go => duck duck went?

🤔

Waiting for a bus. And there is a 14 year old smoking and looking after 3 10 year olds. She then gets them to role her 'fags' and then they all smoke. They are blaring rap from a speaker I'm annoyed everyone is annoyed.

They get on a bus full of elderly people.

Then I have my moment. I hear they are switching phone that the speaker is paired to, for different music. They even say the device name! I quickly get my phone search Bluetooth devices and pair. I connected all I could think was play the tweenies. And so I did.

They have hysterics of laughter, but I try act neutral containing my laughter. They keep saying they can't connect and that it's not their music. This went on for 10 or so minutes of them turning volume up and down. Until they catch on someone else is paired to it. I turn off my Bluetooth and get off the bus, you are welcome society.

I work in a company where I'm the only developer, with everyone being designers or marketing or sales. Typically like the scene from Silicon Valley.

Moto was to create a ticket selling website for their products, and make sure they worked as well. It was all fine, until deadlines were discussed. They wanted it done within 2 weeks, the entire backend dashboard, API and front end.

I told them it's almost impossible to do it, but they insisted on it. So, I made a minimal dashboard and told them, I haven't completed a few things, such as if you edit data in one place, it won't reflect in other tables. So, be careful while editing the data.

They nodded their head for everything, yesterday was site launch and 2 hours before that one bastard decided to changed the product names to something "catchy" but failed to change the same in other places.

I had used the name as foreign key, so querying other DBs became a fuck all issue, and eventually API stopped giving any response to front end calls.

I got extremely pissed, and shouted at that dude, for fucking everything up. He said, you're the tech guy and you should've taken all this into account.

I sat and hardcoded all the data into database again, made sure site is live. Once it was live, these guys call a company meeting and fire me saying I was incompetent in handling the stressful situation.

At that moment, I lost my shit and blasted each of those people. The designer started crying since her absurd designs(though great) couldn't be realised in CSS that too within 2 weeks time.

One of the worst experience for working for a company. I could've taken the website down, and told them to buzz off if they'd called, I couldn't get myself to do it, hence ranting here.

I seriously feel, all these tech noob HRs need to get a primer course on how to deal with problems of a programmer before they get to hire one, most of these guys don't know what we're trying to tell in itself.

I find devRant to be the only place where I can get someone to understand the issues that I face, hence ranted.

TL;DR: Coded ticket selling site in 2 weeks. 3 hours to launch, data entry dude fucks up. I clean all the mess, get the site online. Get fired as soon as that happens.

Live long and prosper. Peace.

Dev: Microsoft is shit

VS Code: (ಥ⌣ಥ)

Dev: Oh not you dear! You're not like the other guys

VS Code: (｡◕‿◕｡)

My "Coding Standards" for my dev team

1.) Every developer thinks or have thought their shit don't stink. If you think you have the best code, submit it to your peers for review. The results may surprise you.

2.) It doesn't matter if you've been working here for a day or ten years. Everyone's input is valuable. I don't care if you're the best damn programmer. If you ever pull rank or seniority on someone who is trying to help, even if it isn't necessarily valid or helpful, please have your resume ready to work elsewhere.

3.) Every language is great and every language sucks in their own ways. We don't have time for a measuring contest. The only time a language debate should arise is for the goal of finding the right one for the project at hand.

4.) Comment your code. We don't have time to investigate what the structure and purpose of your code is when we need to extend upon it.

5.) If you use someone else's work, give them the credit in your comments. Plagiarism will not be tolerated.

6.) If you use flash, you will be taken out back and shot. If you survive, you will be shot again.

7.) If you load jQuery for the sole purpose of writing a simple function, #6 applies.

8.) Unless it is an actual picture, there is little to no reason for not utilizing CSS. That's what it's there for.

9.) We don't support any version of Internet Explorer and Edge other than the latest versions, and only layout/alignment fixes will be bothered with.

10.) If you are struggling with a task, reach out. While you should be able to work independently, it doesn't make sense to waste your time and everyone else's to not seek assistance when needed.

11.) I'm serious about #6 and #7. Don't do it.

devComic #3 "The Pizza Paradox" adapted from a rant by @molynerd (https://devrant.com/rants/178708/)

A SEO couple had twins. For the first time they were happy with duplicate content.

Welcome to hell 😂

Boss wanted me to make changes in company's website which was based on wordpres s.

I knew it could be done by tweaking some JS code, but I have very less experience with wordpress

But wordpress is easy man(Internet told me).

Give me 5 minutes, you will see the changes in production.
Being lazy af I directly logged in to ftp, checked out some files, updated some code, I was good to go.

Before pushing it, I opened the website and it was GONE ٩(๑´0`๑)۶

Now there was no public_html in the root.
I was fucked. I have accidentally deleted the website that had no backup.

And the best part I was on leave from
next day.

I was looking everywhere for backups, looked into google cache to get the contents. I have to recreate the complete site now.

Just when I was asking questions on choice of my profession and simultaneously looking here and there in FTP for backups,
I found the jewel "public_html".

It happens out that I have accidentally moved the folder to some other directory.

Phewww.

Moved it back to root. Site was up and running.

Reassured myself that I deserve to be a dev.

Backed up complete site, made the changes.

Uploaded it.

And the best part, amount of wordpress I learned in those three hours was way more than I could have learnt in many weeks.

Lessons Learnt :

A) ALWAYS keep backups.
B) You SHOULD NOT make changes on prod directly
C) You become superhuman when your brain know you are going to be fucked 😂

CS Professor: “What M word is the black hole to all productivity?”

Student: “Management”

CS Professor: “Was going to say meetings but that’s better”

Windows innit

New devRant comic! Based on a clever rant by @saiprasad (https://devrant.com/rants/262624/)

Issuing transfers to unix for every developer

Found this in 9gag

Sometimes I really hate reading comment section and rants from

"my coworker/senior-dev/manager/boss/professor doesn't know X. I'm so much better and so underpaid"

It's like something is new to you or you didn't know something your mostly a dumbfuck which doesn't deserve his position or shouldn't be there ignoring all the other shit which brought you there. Ignoring a person's background or function. Sometimes this stuff is funny because you think he/she should know X but to call someone dumb/stupid/moron or so just because of this, I'll never get it people must have hughe inferiority complexes or so

Got call from extremely angry customer, our product is shit and doesn't work. At all. Important customer so I went to visit.

He had the perfect setup, our product to the left, our competitor's to the right.

He connected the Ethernet cable to their product, it worked. He plugged it out and connected to ours... Nothing. Shit.

I started to debug on the premises, took logs, everything. It seemed like our product didn't receive any data at all. What the fuck? Tried everything, debugged low level, still nothing. Sweating as hell.

After two hours I got a strange feeling. So I swapped place, our product to the right, competitor's to the left. Now OUR product worked, competitor's zilch.

THE FUCKING ETHERNET CABLE HAD A GLITCH. IF YOU BENT IT TO THE RIGHT IT WORKED, IF YOU BENT IT TO THE LEFT IT WAS BROKEN.

I had never seen a customer be this embarrassed in my life. He apologized to me, my boss, his boss, the Queen, everyone.

We got the contract.

Don't refractor for fun!

An anecdote from my previous company. A developer had written a shitty java console app for fetching stock prices. About 3000 LOC. just one java GOD class. So, when me and my friend looked at it, we were amazed how that code works with all that if conditions spanning 100LOC. so. My dear friend underestimated the complexity. Since it just fetches stock price and puts in database right. I can write it in few days and much better one. So, he started writing code in an OO way. Three days later I see he still working on it. Having a glimpse at code. The app is now Object oriented shitty and ugly.

Guess what new code never goes in prod too.

Learning
Don't underestimate complexity of app.
Be empathic about fellow developer. Don't think he has written a shitty code. Think why he had to do so.
Don't work on refractors if there is no one to guide you.

She: “Execute garden job!”
Me: “Command failed: broken dependency”

Issue 0 of devRant Comics! Based on the epic rant by @cdrice (https://devrant.com/rants/451202/) Let me know what you think!

Ranting time;

Yeah so OK this ancient legacy clusterfuck we've been maintaining and keeping alive finally broke. And even though I'm very pleased with both being right, and the well deserved right to say I TOLD YOU SO, SO MANY MANY FUCKING TIMES to all in management, it's the definition of hate to work 18 hours a day to fix the shit someone else built, that they refused us to refactor. Ah, but wait; there's more! Everyone thinks it's our fault (R&D), because historically it was our department that built the system. Ten years ago. So sales and support are now all over us, those responsible for us being in this mess are either gone or so high up in management that they refuse to take part.

Taking the fall and blame and workload, for something we warned repeatedly about, but were refused to do something with, because shiny features and new apps is what is important!

I'd understand it if the numbers were red, but they arent!! We are growing so fast it was inevitable!

I fucking hate companies who dont listen to their devs..... also companies who places ops on dev shoulders.

Yaaaargh! Also; two developers means twice as fast? No? Fuuuuuck!!!