Client: This works correctly, but I don’t like the code.

Me: What exactly do you not like?

Client: There are barely any lines of code. You need to add more to make it better.

I...I don’t know what to say.

Just me, explaining how my code works.

Reading other people's code.

bad code that works 👍

source: reddit.com/r/ProgrammerHumor/

When you write BS logic, but the code works anyways...

Hoorah! My code finally works! Now gotta remove those 1000 print statements I used to identify the bugs 😥

When your code is a mess but still works

"Let me write the code that works first, I'll reformat it later."

*After a month*

"help. ;-;"

When you code in Python 3 and the final library you need only works on 2.7

Code not working.
Comment out code.
Slowly rewrite it bit by bit till it works again.
Check against commented code.
They're the same.
Wtf.

Seven hours wasted on this shit :/

When your colleagues have no tests for their code and tell you not to touch it, because it WORKS!

When you write code straight for 2 hours and it instantly works 😊

removed 700 lines of code. Works better :/

"Don't waste your time on writing comments or documentation, as long as the code works!" - My (Ex-) Coworker

Me: I love programming.

Friend: Are you serious?

Me: My code works

Friend: Oh, that makes sense.

I don't have a degree but my code works....

1. Code works
2. Add if statement
3. Code breaks
4. Comment out if statement
5. Code works
6. Uncomment if statement
7. Code works
8. Wtf??

Your app works.
You do some changes.
It doesn't work anymore...
You restore the old code.
It still doesn't work... WHY?

Writes code.
Doesn't work as intended.
Debug.
Works as intended.
Tests other scenarios.
Don't work as intended.
Debug.
Works as intended in scenarios.
Scenario 1 fails.
Stares at code.
Staring doesn't work as intended.
Fuck...

When you don't find what is wrong with your code so you do some shit and it works miraculously

"My code works, but I have no idea as to why or how. Even StackOverflow says it shouldn't work." -Me

Spent hours finding the problem in code. Suddenly something happens! Code works! Now I'm spending hours finding what made it work.

Hollywood be like

"Oh no they shot a hole in my CPU, let me just rewrite the code so that it works again. I'll be 5 minutes."

When your code breaks, but it all works out.

>me on stackoverflow
>a nice question
>i provide a 3 line code with explanation
>comment: 'doesnt work, throws exception'
>i run the code and provide a screenshot that it works
>'doesnt work for me'
>19 line code gets accepted

10/10, would answer again

I'm confused...
My code works but... It's really not supposed to...

Fuckin hell!!

Code works everywhere except at one client. Ok, I check logs & see something missing.. I go check the code that handles excel files.. try catch and do nothing.. great.. :/ ok let's log this shit to see what is not ok...
Insert logs, build, update, run.. now it freakin works o.O

When my code works as intended on the first go on a new language

Me: *explains how my code works*
Anyone within 30 feet: "In ENGLISH please"

god knows why the code that works on Friday does not work on Monday

When the code finally works after days of debbugging

Code works.

Rename a variable for clarity.
Third-party lib behaves differently, breaks things.

Change the var names back.
Still broken.

Stash changes and checkout previous commit.
Everything works.

Diff with stash.
No notable changes. (some comments, ...)

Checkout branch again, pop stash.
Broken again.

... What?

Code works.
I'm happy.
Maybe she's happy.

Code doesn't work.
I look frustrated.
She's definitely not happy.

Witchcraft: Code that has been optimized to a point at which even its author has no concept of exactly how it works, only what it is used for.

Tested and checked in code. Left on vacation and came back.

The code I checked in still was there, still works, and didn't cause any fires while I was gone :)

Success!

It always feels like this

My team member just rewrote all of my code and it looks beautiful and it works but and now i feel like I'm a terrible programmer :'(

My code works in first run , but why ? -_-

Any fool can write code that a computer can understand. Good programmers write code that humans can understand.

So far, this is my inspiration to refactoring the code right after it works as gift to my future self.

Whenever i have a problem in code, i visit here to think. it works everytime 👍

That creeping realization how the legacy code works.

The "it's not possible. They couldn't have... yes. Yes they did."

It should have a name

I started learning php at age 15, copying code from tutorials, changing stuff until it worked. Now 10 years later I still copy code from tutorials and change stuff until it works...

Nobody cares what the code does when it works. Everybody cares about it when it doesn't work. You just can't win. 😤

WTFFFF!!!
when you're out of rant because your code 100% works

When my code works the first time

Genuinely for me the satisfaction is when you write code that does really complex shit and your happy that it actually works.. Seriously satisfying

That feeling when you wrote alot of code, without being able to test it.. And then when you put it into the project, it just works!

I stole this but it’s true when code works on the first try

Find a great project on github=> want to find out how it works => open the source code =>zero line of comments

Do you what I am talking about?

The happiness we get when the code works.
Is there any one word for it.

When code works and you don't know why

When you code a bunch of stuff while horribly stoned, and the next day it all still works really well, but you cannot for the life of you figure out how or even why it works.

Junior dev:Hey,see my code works :)
*After analysis of code*
Senior dev:Let's talk about complexity bro
Junior dev: shit :(

That feeling when your code works how you want it to 🤗

When I push the code into the prod and it works as expected...

My cousin just messaged me and asked me to make him a discount code for an online retailer.
THATS NOT HOW IT WORKS.

The more code I remove the better it works

The best feeling in the world is when your code works the first time or when you close 100 tabs when you finish work

My JS function is now lazy loading, expressive, and uses 12 fewer lines of code! 😃

It no longer works, but
... no one is perfect. 😅

Fun fact!

Vs code actually works with 550k lines of html dom.

bad code that works is bad code.

Do you guys commit after your code works or when the day is over?

When your code actually works in first try

You know that feeling, when you code, compile, run. It just works ?

That’s the moment I get insecure

that moment when u run the code and it works, and then u run the very same code again and it fails.

When your code finally works but you have no idea how:

The feel that it gives when your code works after so many hours and attempts to debug it...

😇😇😇

I saw a piece of code that, to my knowledge of software engineering, should have never worked in the first place. The code doesn't know that, and it works anyway.

I call this a "bumblebug".

I am an atheist but sometimes I thank Jesus when a change to some old messy code actually works

Fond this gem in teams code;
Var temp = "",
Var tmp = "",
Var tmp2 = "",
Var tmpIDK = "";
Asked the creator only 4 hours after the commit what his code does. The answer; I have no idea, but it works, don't touch it.

You know that you are a Programmer when you do code mentally and when testing it it works at first try

Me: *rewrites chunk of code*
"Time to test this baby. This is gonna fail spectacularly"
Code: *works*
Me: "Fuck!"

When I have tons of warnings but my code still works

If it works walk away slowly and never touch the code again.

Copy-pasting code from StackOverflow and hoping that it works straight away

This moment when you test your code and all works perfectly! 😍

Code on
Dev Env.: Works Fine
QA Env.: Works Fine

Production:

The same code works in the console but not in my script. Freaking hell.

Thanks, Capybara.

"Well this is Java, that's intelliJ"
-Guy in my CS class figuring out why my code works and his doesn't

When the code we have never tested during development works perfectly in production

When you code berserk style for an hour, and the first test run just works perfectly!

*me* finding solutions on StackOverflow, Medium, API Docs for hours
*senior dev* walks in and changes one line of code
*works* O.o

javascript... the language where your code works even if you forget ';' and declaring your variables.

wtf

When your code finally works! Hahaha

Wk54

If I were to code a unknown thing to man, I would probably code a time travelling machine. Dont ask, how it works xD

Me at the new company:
My code doesn't work, I don't know why..
My code works!, But still I don't know why

Having one of those days where the code works on the development VM but not on the production box.... FML

I might have found out why non of my code works...

This junior dev is killing me with all of the bugs in the code ... like did you even test it to see if it works fml

Just implemented a design from a UI/UX designer in code. Works perfectly on iOS, now to test on android.

Just found the first CLI game I made in c++. The code is a mess but it still works just fine.

I think what would help is to teach them these things:
- awareness for security in code
- how to use a fucking VCS like Git and how it works

Nothing makes me more suspicious than when my code runs and works on the first try

When your code works perfectly fine, and you go to dinner and return and the same code starts crashing.
And I'm like.....
.... Is my computer doing things on its own while I'm away from my desk?..... :/

When your code works one day but not the next.

me: "my code works"
him: "no it doesnt, it crashes"
me: "..but it works on mine......"

and then i have to redo it again

it's not always about good code. sometimes all they need is a program that "works" asap !

When your code works from the first time

Visual studio code:
Debugging that "just works"

Me after several hours:
Yes! I finally got the vscode debugger to attach!

When you write a messy code and it works perfectly the first time

Leaving work with no bugs in the code! Everything works flawlessly!
Coming back the next day and all of a sudden nothing works and we need to spend the whole day getting it to work as well as it did yesterday.
There seems to be programming gnomes, ruining our code at nights!

Instead of worrying about API rate limits I made my code manually parse the html from a website.

And the code still works great!

People learning to code who seems to have more interest in that their code works than in why it works. Do yourself a favour and learn something you have an interest in.

when your code is messy af but somehow compiles and still works!

Writing tons of code without testing and it all works

You're a great coder only if you can deliberately write bad code that works but no one can understand.

Those little moments when you finish writing and refactoring the code and the result is elegant and just works

copied a code for android from stackoverflow and it worked
edited the code no more works
removed the code and pasted the original code from stackoverflow and still doesnt work
clean and build and now the code starts to work

Progress. The backend is deployed and works on my server. Tomorrow, deploying my fronted code to work with the backend.

Most excited I’ve been for code?

When I refresh the windows and it magically works.

I have reached a stage in my career that when my code works in the first try, I'm more skeptical than excited about it.

Got stucked in a problem with recursion in php, almost 2 days no sign of progress until i told my co worker how my code works, then i found the error and it work. I think developers need to talk about the code to realize whats wrong with the code.

We all get replaced by AI and nobody can understand their source code...

And everyone else just goes: hey it works ¯\_(ツ)_/¯

I am scared... I'm scared because the code works.. but it shouldn't work I mean it's not supposed to get triggered and I have no idea what triggers it. It feels like my program got cursed and started doing things on it's own. I even put up blocks to stop the function from triggering but it still works... It always works.. I am scared...

I just hate it when a co-worker says "AS LONG AS IT WORKS. It doesn't matter how you code it as long as it outputs what the client/user wants. They don't check how you code it anyway" *facepalm*

We effin' follow standards so that it will be convenient for everybody!

Bad code is still bad code if you don't follow standards even if it works.

Code works yesterday with the hardware but but doesn't work today (ﾉꐦಠヮಠ)ﾉ, they only work when they want

Don't you just hate it when your code works but you have no idea why, so you spend 30 minutes trying to figure out why it works?

Had to look into some old code today and had the "Is this my code?! This can't be my code!? No one else worked on this code, so it must be mine... But, but, it's so... good! And clean! And logical! And well documented! This can't be mine... Can it!? Hey! It works!" moment.

!rant

The AH-MAZ-ING feeling you get when you write 200 lines of code without compiling and everything just works as planned!!!

YAY!

That awesome feeling when your code works from the first try.

How I feel when my code works.

Any Stromae fans on devrant

His music get me in the zone...when code works and test pass 😅😅😅

My code works at first run.
This can't be right.
Something must have gone terribly wrong.
I don't trust you computer!

Oh, I did it again!
Everytime I think I will write proper standard code with full documentation, but well, guess who didn't write documentation... And now forgot how his own code works.

I don´t know what my code is doing there.

But it works.

I hate wen my code works perfectly; then all of a sudden a million errors popup out of nowhere. 😠😠😠

Finally a night I can sleep knowing my code works!

Programmers have two moods: "code doesn't work" and "code works"

That feeling that your code works.

*errors in code*
me: why....?
*fixed the code and it works*
me: ........how....?

Biggest achievement : code which ran last evening , works same way in the morning 😂😂

*has a test in school on html and javascript*
*Studies a lot and checks to see if code works*
*it works*
*goes into test confident*
*None of the Javascript works* (legit nothing)
Kill me

Algorithm: A word used by programmers when they don't want to explain how their code works

It's terrible how my mood is greatly dependent on whether my code works or not.

Feeling like shit at the moment.

When you spend 2 days writing ~1500 lines of code and you finally put everything to the test and nothing works properly, FML :/

well, fuck... how about everything that works in visual studio but feels like garbage in VS Code???

don't get my wrong I use VS Code for every other language... but C# has just always felt better in visual studio than in VS Code. oh well

Hypothetical Question:
Write a complex code to make it efficient Or
Write a simple code so that the next developer who works on it understands the code easily.

Build failed
Click build solution again
Build works.

I can't tell if it's me, the code, windows updates or visual studio updates but something fucked up.

HAPPINESS IS

...when the code works!

"especially when vertical align works in a way you never thought it would..."

The “if” statement works the same in every* language, so if you can code in one language, you can code in most of them.

*Terms and conditions apply.

tfw you code without building for an extended amount of time and it just works. Where is it? Where is that damn problem that you know is there?

My code works exactly as intended, the first time, every time.

When your code compiles and works 60% of the time, everytime.

(▀̿Ĺ̯▀̿ ̿)

I think the best moment of writing a code is removing curses from comments and renaming variables from like "FUCKING_ITERATOR" to something more normal after everything finally works.

Everytime I run my code and it works. It's the little things in life lol

Writing code an testing it: works fine.
Not touching it for 3 weeks: can't compile it due to an gradle error

I hate Cordova!

three days trying to code magento payment method, our seniors didn't help me (because they lazy), went to other company senior, 10min and everything works...life sucks

“fixing” your code the night before you hand in your thesis.
that always works the next morning, when you present it to the professor ...

The next time I hear some idiot defending his shitpile of code with the argument " BuT iT wOrKs wHy ChAnGe" some heads gonna' roll.

Did a big refactor with no tests and the code works first try 🤔🤔

When your code works correctly the first time 😏 👌

TL; DR;
I'm one with code and the code is one with me.

Everything in my life has been inconsistent and as soon as I start building expectations from someone or something, it disappoints. Be it my friends (😂😂) or my ex girlfriend or my studies or my college or my professors or work, or food (sometimes).

Coding, or programming, has been the only consistent and non disappointing thing since 2010 for me. It just works. If I write a wrong program, I know its why and where its wrong and then fixing it works. Sometimes it works in one go. And sometimes is works beyond my expectations. Its like coding chose me rather than me chosing coding.

WHY WON'T YOU LET ME HAVE THE SATISFACTION?!!

My code works, their test case is garbage.. 😒

!rant

Learning many new things and churning out good code is so fucking satisfying!
And the best part is: it actually works! 😏🚀

- Writes a short decent code. Doesn't work.
- Refactores it with variables and function. Automatically works.
- Changes back to the original form. Freaking works now.

Wtf.!!!
Oh! The lord of bugs and errors, have mercy on me.

Hmm. This code needs refactoring.
*recodes on Local and uploads*
Works on my branch.
*git push origin master and merge*
Works on Dev.
*deploy to Test*
Works on Test.
*deploy to Live*
Doesn't work.
*compares Live to Test, Dev, and Local*
No f$@%^%%$# difference!?!!

*quits development and lives under a bridge*

When you don't get a server 500 error on your JDBC application.

legends:- This code works on my machine!!

My most anxious moments are when I don't know why my code works.

So I'm writing this code, that does 2 important things, that cannot be seperated. I run the code, thing1 is correctly executed, thing2 not. No fucking idea, why this happens. Execute again, same result. Debugg the wohle thing, now everything works fine.
WHAT?
I check the code, there are no background tasks, no paralell processing, nothing that should go wrong.
Asking a Senior developer for help, he also has no fucking idea. He tells me to try to wait one second between the two things. Looking for a delay() or wait() function in my programming language but there is none. Ok, building my own delay, writing a "do 1000 times" loop, calculate some shit in it. Execute the code, it works perfectly.

Nobody has a fucking idea, why this is happening and why this solution is working, but now the code is productive and it works fine.

Best advice so far: "KISS: Keep It Simple and Stupid"

That works every time because your design of the code will be understandable. Your code must seldom to be refactored. You aren't that asshole who never comment and document anything. And the most important part: The code works as designed without flaws!

That moment when your code works and the results are flooding in. But still waiting for something to fail

Code works in my local 🤷‍♂️🤷‍♂️🤷‍♂️

Hey guys, need an opinion.
Please have a look at the picture and let me know if it's a good practice to code like that. The code still works and I still get the output.

Code doesnt work, i dont know why
*comments then uncomments same line*
Code works, stilll dont know why

TFW you add a substantial portion of code, without testing every little step, then you run it and everything works.

Wish I could experience it one day.

Gotta love those moments when you expand your code and the legacy part magically works just fine. Congrats, past me, for writing a stable core.

Experienced programmer:
Code works in head; code almost works in computer; code never works with client.
Beginner programmer:
Code almost works in head; code never works in computer; code will never work with client.
Long story short: it's hard to begin but when you let the code flow, you became a programmer

Wrote some code. Didn't work.
Cleared all build caches, deleted project files and re-opened the project from scratch. Code still doesn't work.
Copied the same code over to a new project. Works.
I FUCKING HATE DAYS LIKE THESE!!!

if you know how the code works is it fair to say that you have written it

Code Works

When you add a bunch of entity framework relationships in code, and it works the first time... Wtf.

It works. My code fucking works. It shouldn't. I got tons of errors, I changed to some obscure shit, expecting it to fail, but it fucking works. I should be happy, but I'm mad for not understanding how.

Ye Ol' Reliable...

When your code works in one go...

you know it's a good day when you copied that funky looking code you wrote, copy pasted in current project and IT JUST WORKS!

The best feeling you can have, is when rewriting big parts of code and it works perfectly first try.

I always try to break my code when it works without errors the first time.

Just to be sure that the code I wrote is being used.

Anyone else?

When my tests pass AND CI succeeds. Or just when my php code works haha

It’s not funny when you don’t know how your code works.

Not caring about code styling and just committing because whiny people annoy me. It works; it works. I should probably abid by code styling standards and do a precommit but bite me 🖕🖕🖕

Algorithm: A word used by programmers when they don't want to explain how their code works.

delete random, unused column from production database
entire app blows up
re-release last change on code pipeline
everything works beautifully
¯\_(ツ)_/¯

When your code finally works

Code review moment that I hate

Me: This is a bad practice. You shouldn't do this
Developer: But it works

*Showed articles and examples why it's bad*

Developer: I see. But it works. Why should I change it?

I've found a new genre that is really nice to listen to when I'm doing homework or the rare time I code some.

Bluegrass banjo music. It's pretty simple and it's never slow. It's off but if it works, it works 🤷🏻‍♂️🤷🏻‍♂️

Things which make me feel badass tester (and dev too) are: dark themed IDEs, using command prompt/ terminal (still as exciting), and when my code actually works lol

*Code actually works first time debugging*
Me:

I'm still worthy!!

Trying to put together all the code of my ajax request into a function so I do not repeat myself. The code works perfectly outside but not in the function. Well fuck JavaScript. I've been stuck here for two days.

Friday afternoon 5:00pm: everything works wonderfully fine, let's go home!!
Monday morning 9:30am: Let's do some more test on the latest code I have wr.... KABOOOOM!!!

My code doesn't work> I have no idea why !
My code works> I have no idea why !
........ :-/ ........

*Write code → run it → works.
*dont even touch that→ run it after few days → doesnt work..WHY?!?!?

That moment when you try several days to get the code to behave like you want and at a random moment everything suddenly works....

Better not to touch it (the code) anymore before it breaks again...

When the code finally works and you make the commit

Nextjs is good. U just write code and it works

If you don't understand your code, but it works, then it's not really a problem

"Here customer, have the username, password, and URL of our developer's CI environment! You can test all of your features there. "

" Devs: Please don't make any changes to dev code that would cause the CI system to run."

That's not how this works. That's not how any of this works.

Writing code and then testing whether it works... This was pretty badass, until it wasn't.

Do love it when your code works and the system to implement it works.
But when you run it, it doesn't work.
(╯°□°）╯︵ ┻━┻

It's a headache when your code works in IE, but not in Chrome or Firefox.