Agency: " Sir, we found 3 candidates as per your requirements, now how do you want their placements sir?"

M.D: "Put about 100 bricks in a closed room. Then send the candidates into the room & close the door, leave them alone & come back after a few hours and analyse the situation:-

1) If they are counting the bricks, Put them in Accounts deptt.

2) If they are re-counting the bricks, Put them in Auditing.

3) If they have messed up the whole room with the bricks, Put them in Engineering.

4) If they are arranging the bricks in some strange order, Put them in Planning.

5) If they are throwing the bricks at each other, Put them in Operations.

6) If they are sleeping, Put them in Security.

7) If they have broken the bricks into pieces, Put them in Information Technology.

8) If they are sitting idle, Put them in Human Resources.

9) If they say they have tried different combinations yet not a single brick has been moved, Put them in Sales.

10) If they have already left for the day, Put them in Marketing.

11) If they are staring out of the window, Put them in Strategic Planning.

And.......

12) If they are talking to each other and not a single brick has been touched, Congratulate them and put them in Top Management.

😂🤣😃😁😅😜

People who send an email saying "I'm getting an error message".

WHERE DID YOU GET IT?!

WHAT IS THE FUCKING ERROR MESSAGE?!

OH NO SURE LET ME LOOK IN MY CRYSTAL BALL, I'LL HAVE IT FIGURED OUT FOR YOU IN NO FUCKING TIME.

😡

I hired a woman for senior quality assurance two weeks ago. Impressive resume, great interview, but I was met with some pseudo-sexist puzzled looks in the dev team.

Meeting today. Boss: "Why is the database cluster not working properly?"

Team devs: "We've tried diagnosing the problem, but we can't really find it. It keeps being under high load."

New QA: "It might have something to do with the way you developers write queries".

She pulls up a bunch of code examples with dozens of joins and orderings on unindexed columns, explains that you shouldn't call queries from within looping constructs, that it's smart to limit the data with constraints and aggregations, hints at where to actually place indexes, how not to drag the whole DB to the frontend and process it in VueJS, etc...

New QA: "I've already put the tasks for refactoring the queries in Asana"

I'm grinning, because finally... finally I'm not alone in my crusade anymore.

Boss: "Yeah but that's just that code quality nonsense Bittersweet always keeps nagging about. Why is the database not working? Can't we just add more thingies to the cluster? That would be easier than rewriting the code, right?"

Dev team: "Yes... yes. We could try a few more of these aws rds db.m4.10xlarge thingies. That will solve it."

QA looks pissed off, stands up: "No. These queries... they touch the database in so many places, and so violently, that it has to go to therapy. That's why it's down. It just can't take the abuse anymore. You could add more little brothers and sisters to the equation, but damn that would be cruel right? Not to mention that therapy isn't exactly cheap!"

Dev team looks annoyed at me. My boss looks even more annoyed at me. "You hired this one?"

I keep grinning, and I nod.

"I might have offered her a permanent contract"

!rant

I built a decently large project at work, and everything works perfectly. It's beautiful, it's fast, it's light, it's organized and clean, and deploying is a breeze. I'm very proud of it.

The biggest reason, though, is that it uses exclusively technology I had never touched before:
• React
• Redux
• ES6/Babel
• Webpack
• Express.js
• Material Design
• Apple lappy (I'm a linux girl)

I was completely new to all of these, including my dev machine. Every single aspect of the project was outside my skillet.

But it went from my first experimental `import React from 'react'` to production-ready in three weeks. I'm really proud 😊

Try => fail
Try => fail
Try => fail
Try => fail
Try => little success
Try => fail
Try => fail
Try => I think I've got it
Try => almost there
Try => fail
Try => fail
Try => oh, is that the problem?
Try => fail
.
.
.
=> SUCCESS

preface: I'm fucking exhausted and angry.

Why does everyone assume I know how to do frontend?
Why am I always the design girl?
Why?

You hire me to do backend. STOP GIVING ME FRONTEND DESIGN CRAP. I HATE IT.

AND STOP GODDAMN YELLING AT ME FOR NOT MAKING SOMETHING RESPONSIVE.

I DON'T KNOW HOW.

yes i can learn, but I CAN'T FUCKING PICK UP A SKILL LIKE THAT IN A DAY. Also, I fucking hate it.

STICK IT UP YOUR (min-width: 1400px) ASS.

But seriously, I've spent 13 hours today figuring out completely new things (webpack, susy, express.js, cloudinary, responsive best practices, more webpack) because the boss is in panic-mode (his preferred state) and wants this project released last monday.

guess what? it isn't done.
because i still don't know how to do everything. and ofc there's nobody to ask because there never fucking is.

Seriously, boss-man. hire a fucking designer, and stop being an illiterate sales goon while you're at it. ffs.

I didn't get paid this month can I borrow some ++ here.It will make me feel better.

Never had a teacher yet... Self taught all the way

At my next job interview. "So, do you have your lpic or redhat certification in vigor?"
Me. "Better. I have these, motherfucker."

(They arrive a few days ago, but I couldn't show them till now. If you're living outside US and worries about if you can get your stickers, be sure you will. They made all their way to Spain, and had no trouble to receive them. Be patient, and eventually they'll arrive safely and beautiful.)

Well, even MySQL server left. Hope it has found a better host

Big congrats to @AlexDeLarge for being the first devRant member to hit 50,000 ++!

A pretty awesome accomplishment highlighting great contributions and content.

Currently working on the privacy site CMS REST API.

For the curious ones, building a custom thingy on top of the Slim framework.

As for the ones wondering about security, I'm thinking out a content filtering (as in, security/database compatibility) right now.

Once data enters the API, it will first go through the filtering system which will check filter based on data type, string length and so on and so on.

If that all checks out, it will be send into the data handling library which basically performs all database interactions.

If everything goes like I want it to go (very highly unlikely), I'll have some of the api actions done by tonight.

But I've got the whole weekend reserved for the privacy site!

Poor Dijkstra is probably crying in his grave because my professor calls him "digest-tra" 😢 feelsbadman

When there is no error the first time you compile...

Programing

Can make something, out of nothing. All it takes is a little creativity...

... and 4 cups of coffee.

Nobody cares about your projects except when they aren’t working

It was 1999. I was just starting my first real job as a programmer for a major insurance company. We were working on code that would screen scrape legacy mainframe data output and convert it to a web-based UI. REALLY stupid project approach I had no input on. I happened to find a programmer in Germany who had released his code in the public domain that would help with making a certain conversion task easier. I downloaded his code and put it to work.

During a code review, a programmer who was probably about 60 asked me where I got the code and what it was doing. I didn't even get to the part about what it was doing because he made fun of me so badly, in a fake German accent in front of a room full of non-programmers, for using code that today is no big deal due to the prevalence of open source. I just clammed up in humiliation because he got everyone laughing at me. His philosophy was if we didn't buy it or write it ourselves, we had no business using it.

I guess I was just ahead of my time?

Teachers who evaluate your mini project on the number of lines of code written........🖕🖕🖕🖕🖕

When someone thinks they know the life of a coder but they don't.

Just me, explaining how my code works.

Ranted about this internship before but just remembered this.

1st internship.

The employees and the boss were having a joke/laugh. I found it funny as well so I laughed along

A little later the boss pulled me outside (as well as my internship guide person): why where you laughing along? You had nothing to do with that conversation. It was none of your fucking business. Stay out of other people's business, understood?

I was scared, shaking and trying to keep my tears in.

That was not the best internship.

it doesn't matter even if your code cures cancer. it's always the ui that matters

This is me when some software have one month free subscription for new accounts

So this fucking happened today.

Me: *sees support ticket coming in about some kind of login issue*

Me: *opens issue*

"Hello, I can't seem to login. There's an error"

Me: *sighs and thinks "at least give me that FUCKING error message then." *kindly replies with asking if they could send me the error message*

"Here it is. I don't understand what is going wrong
and what I have to do"

Me: *looks at error message*

"Invalid customer ID. Please make sure that your ID is correct. You can find it in the activation email we sent you when you registered".

😐 😶 😦

Me: *thinking okay what the fuck, are you fucking retarded or something?*

Me: *kindly replies: "It seems that you are not using the correct customer ID. You might want to look for it in the activation email we sent you!"*

"Oh okay thanks, how did you figure that out?"

Me: 😵 😐 😶 😭 🔫

Seriously what the actual fucking fuck.

Why do people at bus stations not know how a queue works...

Always

!!!rant

I GOT THE JOB!

Just fucking start it.

Don't stop before it is done.

Take breaks when needed.

And don't forget to have fun!

1. Have idea
2. Write down features that thing should have
3. Make a wireframe design
4. Write down possible names for it
5. Open GitHub-Repo
6. Never start coding it
7. Cry

Oh, man, I just realized I haven't ranted one of my best stories on here!

So, here goes!

A few years back the company I work for was contacted by an older client regarding a new project.

The guy was now pitching to build the website for the Parliament of another country (not gonna name it, NDAs and stuff), and was planning on outsourcing the development, as he had no team and he was only aiming on taking care of the client service/project management side of the project.

Out of principle (and also to preserve our mental integrity), we have purposely avoided working with government bodies of any kind, in any country, but he was a friend of our CEO and pleaded until we singed on board.

Now, the project itself was way bigger than we expected, as the wanted more of an internal CRM, centralized document archive, event management, internal planning, multiple interfaced, role based access restricted monster of an administration interface, complete with regular user website, also packed with all kind of features, dashboards and so on.

Long story short, a lot bigger than what we were expecting based on the initial brief.

The development period was hell. New features were coming in on a weekly basis. Already implemented functionality was constantly being changed or redefined. No requests we ever made about clarifications and/or materials or information were ever answered on time.

They also somehow bullied the guy that brought us the project into also including the data migration from the old website into the new one we were building and we somehow ended up having to extract meaningful, formatted, sanitized content parsing static HTML files and connecting them to download-able files (almost every page in the old website had files available to download) we needed to also include in a sane way.

Now, don't think the files were simple URL paths we can trace to a folder/file path, oh no!!! The links were some form of hash combination that had to be exploded and tested against some king of database relationship tables that only had hashed indexes relating to other tables, that also only had hashed indexes relating to some other tables that kept a database of the website pages HTML file naming. So what we had to do is identify the files based on a combination of hashed indexes and re-hashed HTML file names that in the end would give us a filename for a real file that we had to then search for inside a list of over 20 folders not related to one another.

So we did this. Created a script that processed the hell out of over 10000 HTML files, database entries and files and re-indexed and re-named all this shit into a meaningful database of sane data and well organized files.

So, with this we were nearing the finish line for the project, which by now exceeded the estimated time by over to times.

We test everything, retest it all again for good measure, pack everything up for deployment, simulate on a staging environment, give the final client access to the staging version, get them to accept that all requirements are met, finish writing the documentation for the codebase, write detailed deployment procedure, include some automation and testing tools also for good measure, recommend production setup, hardware specs, software versions, server side optimization like caching, load balancing and all that we could think would ever be useful, all with more documentation and instructions.

As the project was built on PHP/MySQL (as requested), we recommended a Linux environment for production. Oh, I forgot to tell you that over the development period they kept asking us to also include steps for Windows procedures along with our regular documentation. Was a bit strange, but we added it in there just so we can finish and close the damn project.

So, we send them all the above and go get drunk as fuck in celebration of getting rid of them once and for all...

Next day: hung over, I get to the office, open my laptop and see on new email. I only had the one new mail, so I open it to see what it's about.

Lo and behold! The fuckers over in the other country that called themselves "IT guys", and were the ones making all the changes and additions to our requirements, were not capable enough to follow step by step instructions in order to deploy the project on their servers!!!

[Continues in the comments]