Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "humor code"
-
A programmer and a business analyst are sitting in the break room one day eating lunch when suddenly the microwave catches fire. Thinking quickly, the analyst leaps up, unplugs the microwave, grabs the trash can, fills it with water from sink, and dumps the water on the microwave to put out the flames.
A few weeks later the two are again having lunch in the break room when suddenly the coffee maker bursts into flames. The programmer leaps up, grabs the coffee maker, shoves it into the microwave oven, and then hands the trash can to the business analyst, thus re-using the solution developed for the previous project.4 -
Stop it with the Linux shilling already.
I'm 27 years old and I love Linux and git and vim just as much as the next guy (yeah fuck you emacs!). I have discovered this place as a room for discussion, advise, humor and rants of course, and I had my good share of giggles.
But lately it seems that every other Post is "look at me I installed Linux" or "hurr durr he doesn't use git" or "windows omfg kill it with fire". And to some degree, those rants have a good point and are absolutely right. However, most of them are not.
This is why you're part of the problem. Constantly shaming and ridiculing any technology that's not hip in nerd culture, regardless of the circumstances. This makes you look just as bad as the peoples you look down upon for writing their code in notepad++ on windows xp with McAfee installed. Even worse, from a professional point of view, it absolutely voids your credibility.
How am I to take you seriously and presume a fair amount of experience and out of the box thinking if all you do is repeat catchphrases and ride the fucking hype train. And yes, I know there are a lot of minors or peoples who are just getting started in the industry. But I have seen enough self-righteous hateful spews from peoples who claim not to be.
Anyway, this is getting long and I think I have made my point. Maybe I am just too old to be joking around that shit all the time anymore. But from what I have seen, I wouldn't hire the biggest part of you. Not because you are bad at what you're doing, but because what you say makes you look absolutely unprofessional.
But then again, this is devrant and I love you all. Have a great week everyone!21 -
Life is mostly about waiting.
Waiting for code to compile.
Waiting for payment confirmation.
Waiting for food.
Waiting for gas to fill up tank.
Waiting for lights to go green.
Waiting for beer.
Waiting for waiter.
Waiting for call.
Waiting for school to finish or start.
Waiting for exam.
Waiting for job.
Waiting for application to start.
Waiting inside prison.
Waiting inside workplace.
Waiting for summer or winter.
Waiting for movie to start.
Waiting for girl to dress up.
Waiting for birthday.
Waiting for birth.
Waiting for death.
Fucking timers everywhere.
Someone got big sense of humor when developing this world.5 -
Artists asked to give them some code to draw it on robot-boss's screen animation. I gave them this:
if (humans.count > 0)
{
weapon.charge();
weapon.aim();
weapon.killAll(humans);
}
dominate(world);
tactics.recalculate();
ai.analyze();3 -
I saw this on the first page of a book that discusses techniques for writing clean code... The more I think about it, the more accurate it tests.
-
“Just make sure you change the code a bit so it doesn’t look like you copied it from Stack Overflow.”2
-
Frustrated that my build system wasn't recognizing a file change I added to my code. It kept telling me that a function didn't exist in the linked object (linker error). I checked everything and stared at this shit for about 15 minutes or more. The signature matched, the function existed, the relevant source files existed. I was starting to imagine impossible scenarios. I cleaned the project and recompiled. No errors, everything linked just fine. Fuck you? I guess...
So I decided to needed to walk around so I went into my bosses office.
me: I don't want to program anymore.
boss: What do you want to do?
me: Shovel shit.
boss: They are the same thing.
me: True...
TLDR: Tool and possibly skill issue results in frustration and humor.6 -
"Ha you commented your code that nobody is going to read! That's funny dude good humor!"
If good coding practice is funny then I'm in good standing.3 -
I’m convinced that CSS is black magic and those that can visualize what it’s going to do before changing code are witches/warlocks.
Usually my attempts end up in humor as the website ends up /comically/ broken. Elements shifted around to not anywhere near they belong, drop downs appearing from completely nonsensical places...
No idea how you all do it.2 -
At college you learn like dozen of languages but end up getting job in Java/C#
Welcome to India 🤗🤗1 -
Quick tip:
When an answer in SO has more upvotes than the question, has so many comments, and has so many explanation, so many code, and so many links, IT HAS A HIGH POSSIBILITY THAT IT IS A TROLL.
God damn i hate when programmers don't have any humor, and leave a comment saying
TROLL. PLEASE STOP THIS. FUCK
Good thing, devRant is full of people who HAS humor. Thank goodness.
tl;dr gone off topic -
The senior iOS dev I was working with in my first job after uni - he showed me so many objc tricks and his self-written libraries to make working with UI stuff in swift more concise, it blew my mind. At the same time, he was very humble and calm, and had a funny humor at times. Also his code and the architecture in an older app we needed to work on was super easy to read and understand. That's why I want to be more like him - and eventually grow a beard :-)2
-
everytime i see posts of code humor of doing ordinary things (for example while hungry eat) i wished i was dead.
they are too lazy and beginner. and they exist because the internet gives everyone some chance of exposure.
while this may seem like a positive and democratic thing, it results in too much low quality and everyone's standards getting lowered.
i don't mind people telling bad jokes to friends and family, because at least then even though sometimes people laugh, a frown will surely happen.
while in the internet, you don't get that reaction. In fact, the shittier the thing you post, the more points you get!
this is my version expressing how i feel about the matter:
while !is_dead()
eat_excrement_from(corpse)
bile_and_shit = vomit()
eat(bile_and_shit)
while it is true that most things online are garbage, that also means that some isn't.
for example, code-poetry.com has very clever code poems that actually does run and has some interesting STDOUT. and those do are worthwhile.
let me also do a preemptive comment to the first fucking idiot that posts a "you must be fun at parties". fuck parties and fuck you too.1 -
**Front End Job Interview**
Recruiter:We want people that have 7 years in react
Me: Well I have 5 considering react came out in 2014
Recruiter:So why did you come here ?
Me:I’m broke, I need a job and I have skills
Recruiter:Ok then..
Recruiter:For your code question,we want you to make a responsive web page with these frameworks and the source code.
*gives link to source code*
Me:Ok I can finish this in 3-5 days
Recruiter:we expect that you have 2 days to finish this
Me: Ok challenge accepted
*Finished website in 2 days*
Recruiter:This is a well made website, I’m impressed
Me:Thank you, it took time but I did it
Recruiter:You know what that means
Me: What?
Recruiter:Welcome to the club, you start next week
Me:LET’S GOOOOOOOOOOO, WOOOHOO, I’ll make you proud with my skills!!!!.
Moral:If you have a little humor and skills, you WILL get the job
I started the job a week later and it was AMAZING
*Based on a true story*2 -
The debate between using tabs or spaces for indentation in code is a long-standing argument among software developers. Those who prefer using tabs argue that it takes up less space and is more efficient, while those who prefer spaces argue that it allows for more consistency and easier readability.
Many developers have strong opinions on this issue and believe that their preferred method is the only correct one. Some even go as far as to say that using the wrong method can negatively impact their ability to work with the code.
Regardless of which side of the debate someone falls on, it's a common source of frustration and humor among developers. The argument often devolves into jokes and sarcastic comments, with both sides poking fun at the other's preferred method.
Despite the often lighthearted nature of the debate, it highlights the importance of code readability and maintainability, as well as the differences in personal preferences and workflows that can arise within the tech community.19 -
Craziest prep for interview :
Step 1 : Given sufficient time for the scheduled interview by any company, start by searching "How to prepare for Google interviews". Awe at the information before you and get all pumped up to jump in.
Step 2 : Starting with Algorithms, study each one and try not to mix any of them in confusion. In case you are stuck in whiteboard coding, close your eyes, take deep breath and visualize Don Kunth. If that doesn't help, well you are ruined anyway.
Step 3: Practice coding without internet connection, till you are able to write code while you talk about how the weather is really great today. Libraries and methods should flow like poetry. SO is sin.
Step 4: The X programming language which you added to your resume because you can write Hello World, head over to Wikipedia and read more about it just in case.
Step 5: Read some xkcd comics so you can impress the interviewer with some humor. You can try Dilbert too. -
I saw an article that stated that Java is the most used programming language... NICE SENSE OF HUMOR...what can I say.6
-
Once upon a time in the exciting world of web development, there was a talented yet somewhat clumsy web developer named Emily. Emily had a natural flair for coding and a deep passion for creating innovative websites. But, alas, there was a small caveat—Emily also had a knack for occasional mishaps.
One sunny morning, Emily arrived at the office feeling refreshed and ready to tackle a brand new project. The task at hand involved making some updates to a live website's database. Now, databases were like the brains of websites, storing all the precious information that kept them running smoothly. It was a delicate dance of tables, rows, and columns that demanded utmost care.
Determined to work efficiently, Emily delved headfirst into the project, fueled by a potent blend of coffee and enthusiasm. Fingers danced across the keyboard as lines of code flowed onto the screen like a digital symphony. Everything seemed to be going splendidly until...
Click
With an absentminded flick of the wrist, Emily unintentionally triggered a command that sent shivers down the spines of seasoned developers everywhere: DROP DATABASE production;.
A heavy silence fell over the office as the gravity of the situation dawned upon Emily. In the blink of an eye, the production database, containing all the valuable data of the live website, had been deleted. Panic began to bubble up, but instead of succumbing to despair, Emily's face contorted into a peculiar mix of terror and determination.
"Code red! Database emergency!" Emily exclaimed, wildly waving their arms as colleagues rushed to the scene. The office quickly transformed into a bustling hive of activity, with developers scrambling to find a solution.
Sarah, the leader of the IT team and a cool-headed veteran, stepped forward. She observed the chaos and immediately grasped the severity of the situation. A wry smile tugged at the corners of her mouth.
"Alright, folks, let's turn this catastrophe into a triumph!" Sarah declared, rallying the team around Emily. They formed a circle, with Emily now sporting an eye-catching pink cowboy hat—an eccentric colleague's lucky charm.
With newfound confidence akin to that of a comedic hero, Emily embraced their role and began spouting jokes, puns, and amusing anecdotes. Tension in the room slowly dissipated as the team realized that panicking wouldn't fix the issue.
Meanwhile, Sarah sprang into action, devising a plan to recover the lost database. They set up backup systems, executed data retrieval scripts, and even delved into the realm of advanced programming techniques that could be described as a hint of magic. The team worked tirelessly, fueled by both caffeine and the contagious laughter that filled the air.
As the hours ticked by, the team managed to reconstruct the production database, salvaging nearly all of the lost data. It was a small victory, but a victory nonetheless. And in the end, the mishap transformed into a wellspring of inside jokes and memes that permeated the office.
From that day forward, Emily became known as the "Database Destroyer," a moniker forever etched into the annals of office lore. Yet, what could have been a disastrous event instead became a moment of unity and resilience. The incident served as a reminder that mistakes are inevitable and that the best way to tackle them is with humor and teamwork.
And so, armed with a touch of silliness and an abundance of determination, Emily continued their journey in web development, spreading laughter and code throughout the digital realm.2