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 - "programming puns"
-
-Some run marathons, I run Python
-Some have energy drinks, I have Java
-Some fight in MMA, I fight with CSS
-Some see new places, I C new Places();
-Some are quick, I am Swift
-Some go camping, I Go Compiling
-Some can judge objectively, I can judge Objective-c
-Some climb mountains, I Scala Structures
-Some live adventurous lives, I live a BASIC one
-Some go ball, I COBOL
-Some watercolor, I Pascal
-Some look for diamonds and emeralds, I look for Ruby and Perl
-Some write novels, I TypeScript
-Some banter, I SmallTalk20 -
I knew nothing about programming then i came across this amazing chilled out teacher who taught me cpp literally through jokes and puns and here I am still learning the best thing I've came so far
PROGRAMMING
P.S. Here is a meme to show what my mates think when i fix stuff up2 -
!rant
Most programming shirts/hoodies really suck. They fall into two categories:
1. Super lame pun quotes in an ugly font.
2. Memes transfer-printed onto cheap fabric
I'm not against puns, or quotes. I quite like the design from @AlexDeLarge
https://devrant.io/rants/830390/, and I've been looking for a nice shirt with Dijkstra's "simplicity is a prerequisite for reliability" on it.
But many do not put any thought into beautiful design, and shit like "No place like 127.0.0.1", "404 girlfriend not found" or "There are 10 kinds of people" really stopped being funny a decade ago.
Good design, colors & quality are so fucking important.
What are your favorite dev-related clothes?16 -
Here are few hillarious coding puns I found....
class Brick implements Throwable { }
byte me;
char acter;
float stone;
Exception taken;
string me_along;
int elligence;5 -
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