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
-
Will the bug in my code please stand up?
I repeat
Will the bug in my code please stand up?
I think we have a problem here.
*music intensifies*11 -
"Sir, I fixed the recent bug"
"Great, what did you do?"
"I commented out the code that was causing it :)"
"Brilliant! You didn't forget to push the code to production, did you?"
"No Sir, I pushed it immediately"
"Marvelous! I'll arrange a promotion for you next month"5 -
When you finally accept that the code will never be bug-free and instead make friends with the uncaught exceptions.
1 -
Manager: This code you wrote violates the single responsibility principle!!
Dev: How so?
Manager: You have one function that you call in *MULTIPLE* places. That’s too much responsibility for one function! Functions should only have one responsibility!! Creeping the scope of a function beyond that is a TERRIBLE way to write code!
Dev: But why spin up multiple functions that all perform the same thing?
Manager: Well if a function has a bug in it and you use that function multiple places then that bug exists everywhere you use that function. If a function only has one responsibility then if it has a bug that bug will only exist in the single place it is called! You really should think first before asking questions like that.
Dev: …26 -
Boss man: your code has issues , you should strive to have lesser bugs.
Me: GTA was made due to a bug in the their code.
*mic drop, leaves office, clapping heard in background*
😂
12 -
Aparently there is piece of code out there, which is completely bug free.. its called hello world.8
-
Can't find the bug for hours. Next day find it immediatly.
Sometimes try and get some distance to your code.4 -
When you hit run after an hour of powercoding:
Old Mcdonald had a bug,
E I E I bug.
And on that bug he had a bug.
E I E I bug.
With a bug bug here and a bug bug there.
Here a bug, there a bug, everywhere a bug bug,
Old Mcdonald had a bug.....
E.....I.........E............I.................
[FATAL ERROR] : Program has ended for a simple reason...not telling why though...here's a completely unrelated line of code you may want to take a look at :) -
You realize that you are a developer when you can't stop thinking about a bug that has been messing your code.
-
Mastering git has become the best thing ever. I feel like a real code monkey. Swinging from branch to branch. Eating all the bug-eeee eeee ahhhhh oooh aaaaaaAAHHHHHH!2
-
2 Days.
Thousands of lines of code analyzed.
Dozens of log files across 6 servers.
Countless pots of coffee.
Much power metal.
...
One line of code.
Bug fixed.8 -
Finding the bug. The usual flow:
"Omg! I think it's a bug in the compiler"
10 minutes later:
"OK, it surely is a bug in the runtime"
20 minutes later:
"I'm certain this is a bug in the core library"
2 hours later:
"Oh, it's a bug in my code. Again, as usual, I'm the idiot. Stupid world."1 -
My Boss: When are you going to finish?
Me: There is a bug, I'm solving it, I need more time.
My Boss: Why have you introduced a bug in your code and now solving it? It were more simple if you didn't created any bug!
Me: WTF!!!8 -
IF LIVES DEPEND ON A SYSTEM
1. Code review, collaboration, and knowledge sharing (each hour of code review saves 33 hours of maintenance)
2. TDD (40% — 80% reduction in production bug density)
3. Daily continuous integration (large code merges are a major source of bugs)
4. Minimize developer interruptions (an interrupted task takes twice as long and contains twice as many defects)
5. Linting (catches many typo and undefined variable bugs that static types could catch, as well as a host of stylistic issues that correlate with bug creation, such as accidentally assigning when you meant to compare)
6. Reduce complexity & improve modularity -- complex code is harder to understand, test, and maintain
-Eric Elliott12 -
I have been 6 hours trying to fix a bug in more than 3000 lines of code.
Removed one line and bug fixed...
WHAT THE FUCK
I will pack my things and go home...4 -
Hehe, just inherited a bit of JavaScript code. Ashamed to say I physically lol'd a little :) Guess I have an easy "bug" to fix.
6 -
I bet everyone here knows these two situations:
1. You have a bug, show the code to somebody else for debugging and the bug is gone, but as soon as you're alone again, it reappears.
2. Your program works fine, you want to show somebody what you accomplished and...
IndexOutOfBoundsException: The index was outside the bounds of the array.11 -
The worst part of debugging my code isn't the hours of wasted time, it's the fact I know I wrote my own damn bug!2
-
- there is a bug in the code.
A: I have searched everywhere I can't find the bug
B: What was the last thing you wrote?
A: I called this function
B: did you check the function for bugs?
A: no, I just coded it, there can't be any bugs there3 -
Boss: I wrote some tests and there is a bug in your code but I cannot find it. Fix it
Me: Sure. I'm on it.
Narrator: 5 minutes later
Me: Boss, I found the bug. It's in your testcode...
Seriously... WTF?!
(before someone suggests that my code should handle all test cases... He tried to measure the time the program needed to response and fucked it up...) -
Fixed this guy's code and he spent the whole day thanking and explaining to me how sad and depressed the bug had left him. I felt really sorry for the poor dude. Lol.
1 -
Hunted a bug for 8 hours, thinking it was a problem in my code....
Found out it was someone else's code generator that injected the bug...
Contacted the concerned dev... Had to convince him for another 3 hours that it was his change to the code that caused the issue. He is still sure that his change can't break the code...... What the fuck are you..? A fucking God programmer who never makes mistakes??
I mean how hard is it to just accept when I just proved it to you??6 -
Ever been stuck in a bug, you sleep it off, dreamed of the code to fix it and you woke up, tried it, and it worked??7
-
A random number generator in my code just gave "0000". I even thought that could be some bug and was investigating. How cool is that?2
-
When your team members report a bug in my code, when they actually changed the specs and didn't tell me 😳1
-
Me at QA, talking about a nasty bug I found in legacy code.
QA: what was the root cause?
Me: pos code.
QA: pos?!
Me: piece o' shit.
QA: ...1 -
My boss, who can't code, just gave me a bug to fix and said should be a quick fix...
It might be, but since you can't code, maybe don't assume
🤦♂️5 -
When you leave your code overnight with a bug and come back in the morning to see it somehow starts working
9 -
I call this the Distraction Stack.
[working on code]
"Hey, can you look at this bug?"
[
working on code,
looking at bug
]
"Can I bother you for a second?"
[
working on code,
looking at bug,
being bothered
]
"When you're done with her can you stop by my desk?"
[
working on code,
looking at bug,
stopping by your stupid desk
being bothered
]
It's enough to make me pop.10 -
When you rewrite some sloppy idiot's code to be way clearer and straightforward. Then you fix a bug you introduced... and another... until the code ends up looking more or less the same as when you started...2
-
Easy cop out for people who wrote code vulenerable to SQL injection: It's not a bug, it's a feature that let's users search using SQL syntax.1
-
I've been looking for a bug in my code the whole day. I randomly found it in 2 minutes today. That seems about right 😑6
-
I just had a dream about how to squash a bug I was encountering in my app. I immediately woke up, fixed the bug, and cleaned up my code. I thought this only happened in movies.3
-
I write blocks of code like this:
If(condition){
code
}
I'm trying to fix a bug and the previous dev is doing it like this:
If(condition)
{
code
}
Does anyone know any good nerve calming pill ? 😜19 -
When your supervisor/teacher is looking at your code and you hope he/she doesn't detect the bug you found before showing the code.
1 -
I need 15 minutes to solve this bug.
... 3 hours later: I have no idea why my code doesn't work. :)1 -
> be me a 23 y.o intern
> two years on self learned MEAN stack
> first day of intern<
> boss: we need you to become an iOS intern
> me: *whut*
> me: *thinking swift syntax is similar to JavaScript*
> me: OK, in swift ?
> boss: No, in Obj-C
> me: *fuck*
> spend 2 days to familiarize with Obj-C
> boss: Here's a bug, solve it.
> me: OK
> me: *checking their code for the first time*
> me: *fuck, fucking huge*
> me: *open up bug related ViewConttoller*
> me: *fuck, 6k lines of code*
> me: *fucking MVC*
> spend 2 hours to fix the bug <
> boss: you did great ! awesome
> me: *heh*
> boss: *announce to everyone* from now on INTERN will take over the project.
> me: *whut*
> boss: here's our roadmap plz implement features
> after 3 months <
> me fixing bug <
> me do feature development <
> me write shitty code <
.
.
.
repeat, life as an intern6 -
If programmers became musicians we would see
- Wake me up when my build ends, 21 cores, Boulevard of broken CI pipelines by Blue Screen Day
- Smoke from my cabinet by Deep For-Loop
- This is how you debug me by Loopback
- Post-release rhapsody by debug queen
- Another bug in the code by Programmer Floyd
- Smells like bad code by Coders from Botswana
- A place for my code, Cure for the bug by Likin to code at dark
etc etc..5 -
Me, talking to a colleague:
"No, thats impossible. The problem can not be in my code. Let me show you why. You see, the code does this, and than it goes here, and then… oohhhh…. I’ve found the bug."3 -
while(freeTime == true) {
if(iHavePlans == true)
waitUntilDone();
/*
* TODO: Fix bug that causes
* coding to call the gaming and
* relaxing methods so often...
*/
code();
}7 -
That feeling of reilef and rage when you find out the crippling bug in your code is because you are passing the wrong variable and not because the function is broken.3
-
When I see a bug in somebody else's code (Gnome):
- "can you please not write bugs!"
When I see a bug on my code:
-"whatever, I'm only human..."
😅2 -
Overheard a conversation between programmers:
.... Your dirty hack finally caught up with you!
.. it is responsible for bug A, B , .. E ... F..
That "temp" code was not touched in years.3 -
There was a bug that I ignoring to fix for past 8 months and finally Client found the bug and reported back to me. All I said to myself "Motherfuck".
So from tomorrow I will be rewriting a piece of code.3 -
1 little bug in the code
1 little bug in the code
put a little ; in now
compile it around
991 little BUGS IN THE CODE1 -
??????????????????? What??????
???? What???????
I couldnt solve a bug for hours.
Hours of googling.
Hours of mental trainwreck.
Hours of stress.
1:28 am.
I cant solve it.
HOLD ON I HAVE AN IDEA.
ChatGPT AI. HELP ME.
i copy and pasted the part of code thats bugging me. Keep in mind that this is a VERY large and robust system and this is just tiny percentage of code.
I told the AI to help me fix this shit bug.
ChatGPT literally explained me what the bug is as if im retarded and wrote code how to fix it.
LOOK AT THE SCREENSHOT U CANT EVEN MAKE THIS SHIT UP
HOW????
18 -
Shit you can apply this to coding too.
"When you fix a bug in your code"
Red: Actually does what you want
Blue: Completely fucks your entire program up.
10 -
Dev1: "How did you wrote this code? It causes bug on production."
Me: *checks on gitlens*
"Dev1... 3 months ago"1 -
*looks through code trying to find and fix a bug that crashes server, thinking heavily*
*Coworker comes up*
> Oh hey did you see the email I sent you?
*Forgets everything and has to reread code from top to understand*
repeat indefinitely3 -
When you're lazy to implement a little feature you thought about but the feature gets implemented anyway because of some bug in your code..
True story btw
3 -
Trying to find a bug. Found a possible line in the code where it might be originating from.
Not I put a breakpoint in there. I can't reproduce the bug anymore.
Sometimes I think I should just go home and play games :(2 -
That feeling when a bug has been bugging me for 3 days, I find that little information in API source code and using that I make a fix.
Developer life is so worth it :) -
The worst kind of problem you can have while coding is an inconsistent or intermittent bug... For code you didn't originally write...1
-
So I had this conversation with my boss yesterday...
Me: Hey, I found this bug in the other team's code that has a major impact on what we're trying to do. Can you ask them to look into it?
Boss: No, I don't want to be the one who has to tell them there's a major bug in their code. Find a workaround.
M: But... It isn't really a major bug, it just has a big impact on our side of things.
B: Workaround!
Fuck bosses who value how they think they look to other devs over a day of my time. Fuck.4 -
!rant
just wanted to share with you guys,
instead of spending 1hr writing shitty code to fix a bug quickly, i just spent tha last 10 fucking hours and finally fixed it
I'M FUCKING PROUD OF MY CODE, IT BELONGS TO A MUSEUM8 -
Be us
Be pair devs
Be doing PHP
Be explaining code to each other to find bug.
Be confused. Code checks out.
Be laughing asses off
Be realise the filename had a m instead of n
@TheCapeGreek -
This stupid fucker of my senior writes code directly in server. Whenever I give my branch name to merge and deploy, he types code manually again in the server. This introduced a bug and I had to fix it in server again.3
-
git commit message that I hate:
1. "Adjustment"
2. "Improvement"
3. "Fix Bug"
4. "I commit it but there are bug in this code"
5. "Client request"
YOU KNOW BE MORE SPECIFIC ON YOUR COMMIT MESSAGE!!!9 -
To the remote dev who ghosted me right after we discovered a major bug in your code, and whom we paid up front for development, thanks for nothing.
You’re fired.6 -
After alot of 24, no sleep, and lots if coding I went full Jack Bauer on my code. Shouting, "where's the bug!? Where is the bug!?"3
-
I feel so bad for the Devs of this app, they can't make up bullshit excuses and not bug test their code like other Devs can
-
Blaming someone and giving them a lecture on a bad code/bug then realizing it's not a bug or that I fixed it incorrectly.
-
Have you ever told yourself to code till 12am and realised that you wanted to fix that bug to the point the clock struck 5...1
-
When you encounter a bug in your code while writing a test and you have absolutely no idea what's wrong...
...and then you see it's a type problem.
-
The feeling when you leave work frustrated because of that unfixed bug and in the night you lay on the bed, trying to fix the bug writing code in your mind and getting more frustrated because your imaginary code doesn't fix the bug.1
-
Current Job Title:
Hoarder Bug Exterminator
Details:
Fixing code for projects that have not been refactored ever in 20+ years. -
Why can't software development just be software development? I hate when laws and politics, etc., get in the way
Look at this, for example: https://arstechnica.com/information...
Apple added some code to make the Chinese government happy, which resulted in a bug, which is stupid!4 -
When I was a kid :
- Bugs eat grass
Now:
- Bugs eat time
I still wonder when will the day come when I write bug-free code in my first attempt (:(8 -
Just spent an entire night eaning up my codebase...
I optimized some of the functions got rid of unnecessary global variables and changed up the whole file hirearchy so it would be easier to read. After spending all night doing this I went to run the program and for once it seemed everything worked right the first time! However a portion of my application that is supposed to happen at a certain date and time never would run. After spending all night comparing each and every line for what I changed versus my last commit I couldn't find the fallacy in my logic. Everything should still work like it did before. After spending more time looking for bugs I finally realized I didn't break anything when I switched over to this new structure it was the old code that was broken. I went through the old code and after some debugging eventually found the culprit an extra continue statement that prevented my loop from fully executing. Lesson learned sometimes the biggest bugs can spawn from one line of code.4 -
That moment when code reuse makes you reuse reused code and you actually reuse a BUG.
You decide to go for code reusing when your boss asks: "Can you add an edit popup besides that 'add customer' popup button?". You do some little tweaks to the "new customer" code and it allows that to save over an existing entry, cool.
However, after a lot of time spent on reviewing the resulting PR, turns out there was a dormant bug on the code you reused, and it woke up with its new use.
That code was a bad copy-pasta from another, bigger form, which included a whole bunch of optional fields. As it was only used to save new entries, those now missing fields were simply being saved as empty. But as you reused that to save existing entries, you were now cleaning up all those optional fields without noticing.1 -
Fixed a bug in a code wrote 11 years ago.
It took 11 years for a user to find a bug.
The user must have a prize: a Bug Bounty.
My Boss does not like Bug Bountis
4 -
Me: Writing an amazing code
Client: say nothing
Me: making a stupid bug, the client complains, I fix it instantly
Client: WOW you're amaizing3 -
Just switched to dark theme in my code editor from a custom Grey color palette.
I dunno, it feels... evil? Like it wants me to commit the overlord of a bug I just wrote.1 -
I'm sitting here at 1 am working on a side project. There's, literally, a bug in my code. It's bed time.
9 -
that feeling when you start looking at code after dinner, correct a bug or two, start implementing new features, tweak the code a little bit, you are really focus in your coding... then look out the window and realize the sun is about to come up. it's great 🤓
-
A big project in my company. Had some annoying race condition that caused data to get deleted when two processes finished in the wrong order they hit the dB and override each other’s work.
Long story short. Fixed the bug and in the process the codebase shrunk by 60%. I didn’t have to delete the rest of the code, but the bug was due to a function in the legacy section of the code, and found out that it was the only function used in that section.
So I deleted it. Rewrote the function so it upserts. And bam. Smaller, cleaner code :)1 -
One thing I learned early on was...
"If the bug is not where you are looking...look somewhere else."
I just spent 2 hours looking at 50 lines of code pulling my hair out why it wasn't working. Guess what...those lines were correct. The bug was somewhere else.4 -
When you have a bug in code that you are trying to fix for a century and then when you fix it you, make 15 more bugs by solving that bug like wtf2
-
I downloaded somebody's GitHub code to use for a project. It had a bug that broke functionality, so I fixed it and started running it to gather data. Then it stopped working for a different reason. I rechecked out the code fresh, same (second) issue occurred. It was a second bug, that once I fixed it, everything worked. But I didn't need to fix it the first time! There weren't any commits in the last two months! I blame ghosts.
-
Everything works fine until your manager starts looking at your code and all of a sudden your screen starts interacting with your manager- "Here is a bug there is a bug and you have got a lazy developer who ignores me like a dumb."
And I am here like wtf ... Wasn't it working fine earlier...
Manager in anger... Me in shock and code is totally in revenge mode...
Oh god... turn this Monday back to Sunday!!!
Scary Monday story begins.... -
Come back from a week's vacation, 3 apps in review. Sit down, set up Xcode, pull latest changes. Run code for the first time, tap through two screens, find a critical bug and I have to reject all 3 apps and resubmit.
5 business days away and I found an obvious bug in 5 minutes.
Someone's not doing their job... -
I found a bug.... it's in production for a long long time... I wrote it while optimizing some legacy code....
FUCK.... how do you feel when you discover a bug in production created by you?6 -
If you think your legacy code is bad - this is what I came across in a system I'm refactoring this morning... and this isn't even the bug I was looking for.
1 -
Just came across this in a website project of my company.... and it goes on for about 5 times of that. But it's not in the html code, guess it comes from some js framework. Not sure if bug in framework or bad code in website.
8 -
Life can be simplified with code. We're all running on an infinite loop. Eventually, we come across an unexpected bug and crash.2
-
// This part of the code should never run
Came across that lovely comment when fixing a reported bug. Guess where the bug was? You guessed it XD1 -
99 little bugs in the code, 99 bugs in the code, 1 bug fixed...compile again, 100 little bugs in the code. 🐞
-
Product Owner: There is a major bug with your code it's not working.
I then spend hour looking at code to find out.
It's a content problem! -
duration = startTime - endTime;
So much facepalm
(I may be an hypocrite... https://devrant.io/rants/384227/...)1 -
Note to self, don't fix a minor bug that will not effect the demo right before the live demo. My program that was working great didn't work anymore during the demo because of my quick bug fix I figured I had a few minutes to add to my code.1
-
Do you find yourself saying sorry to your code/computer when you find a stupid bug during dev?
https://m.xkcd.com/371/ -
that moment when you're driving home and suddenly figure out your bug and don't know when you are able to come back to your code (and have no remote access)...6
-
I had a ticket to enhance the loading of a page.
So instead of doing 40K requests to a MySQL DB in order to generate a tree and display it to to the user on each page visit, the initial query was optimized and moreover, the results are saved in a MongoDB which will then are served to the user on each page visit.
Long story short, after a code review the code got shipped to production and there was a bug which got fixed in a Hotfix shortly afterwards.
I got all the blame for the bug.
I don't deny I have a responsibility for the bug.
Do you guys think the code reviewer also has a shared responsibility for the bug?4 -
- Favourite pastime while waiting for your code to compile
- Most heroic/ingenuous bug fix
- Hardest to track down bug
- Worst legacy code you wrote and left behind leaving a job
- Weirdest project
- Last side project you actually finished
- Explain your job like I'm five/the way you do it for non-tech people
- That time your past self (almost) got you in trouble
- Software pet peeves
- Story about how you freaked someone out
- Feature that most certainly was a bug once
- Post something for your favourite previous weekly tag! -
I'm so happy that I have the first working version of the program. Just couple of bug fixing and unit testing and I'll push the code to production.
Day 1: Just couple of bug fixing and unit testing and I'll push the code to production.
Day 2: Just couple of bug fixing and unit testing and I'll push the code to production.
.........
Day 200: Just couple of bug fixing and unit testing and I'll push the code to production.
😞 -
What really grinds my gears!?
Fucking wasting my time on code that isn't the actual source of the bug!!! -
dat feeling when you code a chunk of a page for 15mins and then you test it for an hour and a half cause you cant believe there's no bug or unhandled error
-
When you realize that the solution for a bug in your code is putting
if (somecondition)
but then you put
if (!somecondition) by mistake and try to figure out why is the bug still there :-(1 -
I hate legacy code.
Introduced some new changes to our application and voila! A bug in the legacy system surfaces. It was just hiding in there, waiting to ruin my weekend.2 -
Chased a bug for nearly a week. Huge code base, over 2mn lines consisting of a mess of C++, Python and Lua glued together.. Wrote a very complex distributed computational framework. End up with a elusive compiler bug in GCC.. FML
-
Get a ticket for a low priority bug, reported internally. Fix the issue mentioned in the bug.
Moves to QA environment, the original bug reporter tests and *passes* the ticket.
Moves to Staging environment, same exact individual then *fails* the testing. Cites totally new/unrelated changes that need to be made.
Apparently our the workflow is -
Code->QA->Staging->Requirements
Makes sense! :)1 -
most memorable bug I fixed
Line 1:
- throw new Error(‘test’)
+ // throw new Error(‘test’)
yes, this was committed code in production4 -
Let
y="coffee beans"
Then (for devs)
y'="coffee powder"
y''="cup of coffee"
y'''="code"
"bug in production which requires urgent fix"=y''''1 -
If i always would say what i think during programming or Bug fixing some code, i probably get fired and moved to a anti Aggression Therapy
-
This is so nice..💙😄
<Heading>
Synopsis of Gita (religious book of Hindus)
<Stanza 1>
Code is an illusion
Today you are coding
Tomorrow someone else would do it
Thereafter someone else
<Stanza 2>
What did you learn
That is helping you in this Project
What are you learning
That will help you in your next Project
<Stanza 3>
Bug is the truth of life
It is today, and will remain forever
You think you have debugged the Bug
You are wrong
<Stanza 4>
It is continuous
In various new forms
It pops up
Recognise it Parth (Son of Hindu God)
<Stanza 5>
That's why go on making Codes
Don't think about the Bug
They will come to you
On their own1 -
Happy days, yesterday we updated form 16.3 to 16.4 and thanks to them fixing the bug in 'getDerivedStateFromProps' my broken code is now breaking.
Don't you just love it when features inadvertently depend on bugs. The entire component ONLY worked properly because of a react bug.3 -
Whole day was a debug session with several hundred lines of code and tons of if else conditions.
Found the bug.
Time to go home.
I am done. 🤕6 -
Sometimes I think that my computer is possessed.
The story goes like this (typical): adding a new feature creates a bug with something that worked perfectly until now. I find and solve the bug in a few minutes. Now the spooky part: with that sort of bug, even the code that worked up to now shouldn't have worked. But it did. Does someone knows a good Ghostbusters service?1 -
I don't know why I'm doing this but when I go to websites that aren't mine and found that there's a bug in their site or system, I kinda happily report these bugs and issues to their email with screenshots, findings and steps to reproduce the bug.
Just recently, I just went to a site and found a peculiar timeout error, eventhough it was less than a second to respond back. Only to find that there was an undefined JavaScript variable in their code.
Is there a bug bounty for fixing code?6 -
quotes of best times
"You would never have a bug if you don't write a code"
"Your code could never crash if you don't run it"
"Your program can never fail if you don't test it"
"Your startup could never be unsuccessful if you don't deploy"4 -
Have you ever wondered about clever robots that are able to code?
Finishing a project without a single bug 👍4 -
I encountered a really weird bug today in my javascript. I'm working on a CMS and one of the things it handles is adding, uploading and resizing images. So, one function adds an empty image to the dom, unselects the currently selected image and selects the new empty image. Pretty straighforward right? So the problem is the unselect function didn't want to work. The image is added and gets selected but the previous image is also still selected.
I set a few breakpoints checked every variable but everything was the way it should. So after an hour trying things I discovered that if I removed the code where the image get added to the body the deselect function works (innerHTML += element) I thought maybe a little timout between these two actions would work but it didn't work. It looks like all dom actions lock up after the empty image gets added. I didn't understood so I moved the unselect function to the above the image add code and it worked wut ??.
code before fix:
func:
body.innerHTML += html;
unselect();
select();
after:
func:
unselect();
body.innerHTML += html;
select();
Atleast its fixed now -
Code Written few months ago: Hello, I have a bug inside me.
Me: Do I know you?
Don't ask me to maintain code written in the past2 -
So my boss thinks of debugging as a guessing game. As in you just say random things that have not even the slightest relation with the code where the bug is ... now i know why it take days to fix a little bug...5
-
Wasted two hours to end up finding out EF Core had a bug :\
Next time better blame Microsoft before blaming my code lol
https://github.com/aspnet/...9 -
* Customer reports bug.
* I fix the bug.
* This highlights another issue that I haven't got enough resources to fix.
* I revert the fix.
* <insert hacky workaround here>
We have code that invokes undefined behaviour (freeing memory twice), but somehow people have managed to build around it and now it depends upon it to work.
FML. -
It's a Monday, I've been trying to fix a bug since the morning, I cannot read or write any code. I tried to review a PR, still cannot read the code. Getting frustrated by the slightest problem.2
-
Sing: "110 little bugs in my code,
110 little bugs,
Fixing one bug,
Compiling again
Now there are 121 little bugs in the code"3 -
I've looked at code I've writte and on average I fix one bug (minor) every 10-20 lines.
Is this normal, subpar, or good for a beginner?8 -
Not sure what is going to be worse. Fixing the bug in this code. Or removing all of the code I added in the name of finding the bug in this code. I have found myself asking myself why I chose coding when I come have picked something less stressful. Like flaming bull fighting.
-
for one split second I thought I had discovered a way to manage multiple states with one reducer function in react,
turns out it was a bug in my code,
I had already gone to brag about it on my react group chat, until I went back to my code and as I was cleaning up and closing brackets and all that stuff, my new feature stopped working.
I need to find that bug3 -
If you say u can write a bug free code, thats a bigger news than AlphaGo.
#alphaGo
#awesome_documentary 👏👏1 -
When you testing your exception handling by throwing an exception, but the code throwing the exception has a bug and throws an exception, so you think it works... d'oh
-
All time I try to find any interesting bug in my code but when ever I debug I find only stupid mistakes :/1
-
Couldn't sleep this morning, so at 6am I tried to tackle the bug that gave me a hard time yesterday... at 10am I found the bug, and so I remembered the number one rule when coding.
KISS? Nope.
The number one rule is that your past self is dumb and he probably created the bug in the easy part of the code... you know, the one you didn't even check because of-course-the-bug-cannot-be-there-Im-not-stupid.2 -
Dreamed about fixing an unsolvable bug in some code that made absolutely zero fucking sense and woke up with a fucking migraine.
-
"Whenever there is a decline in quality of code and rise of bugs and errors oh dear coder, I manifest to show the path of bug and error free coding" said code-god
- Chapter 1 Verse 1, Code Gita -
When I added that bug fix to my code a few weeks ago only myself and God knew what I changed - now only git knows...
-
This is just a sweet little harmless block of code, why should I unit test it?
3 months later...
Bug in production : This is why. -
Hi Devrant!
I've been doing mainly bugfixes for about 3 weeks now, and to keep myself sane, I have re-written Queens - Another one bites the dust, to fit my work. I hope you enjoy it too.
Let's go!
Dev walks warily down the street
With his brim pulled way down low
Ain't no sound but the sound of his keys
Keyboards ready to go
Are you ready, hey, are you ready for this?
Are you hanging on the edge of your seat?
Out of the hands the code rips
To the sound of the beat
Another bug bites the dust
Another bug bites the dust
And another bug gone, and another bug gone
Another bug bites the dust
Hey, I'm gonna get you too
Another bug bites the dust
How do you think I'm going to get along
Without you when you're gone?
You took me for everything that I had
And kicked me out on my own
Are you happy, are you satisfied?
How long can you stand the heat?
Out of the hands the code rips
To the sound of the beat, look out
Another bug bites the dust
Another bug bites the dust
And another bug gone, and another bug gone
Another bug bites the dust
Hey, I'm gonna get you too
Another bug bites the dust
Hey, another bug bites the dust
Another bug bites the dust
Another bug bites the dust
Another bug bites the dust
Shoot out
There are plenty of ways that you can hurt a man
And bring him to the ground
You can beat him, you can cheat him
You can treat him bad and leave him
When he's down
But I'm ready, yes, I'm ready for you
I'm standing on my own two feet
Out of the hands the code rips
Repeating to the sound of the beat
Another bug bites the dust
Another bug bites the dust
And another bug gone, and another bug gone
Another bug bites the dust
Hey, I'm gonna get you too
Another bug bites the dust
Shoot out4 -
Sigh, I have this terrible habit where I make and run my code in the same command. I'll spend an hour wondering why my bug fix didn't work and it's because the make never succeeded, but the code runs anyways. 😒😒😒4
-
Is there a name for the phenomenon whereby you iteratively modify code to try to fix a bug, with no apparent result, and then realize it's an entirely different part of the code causing the issue, but the parts you were modifying actually did need modifying too?2
-
The code life is a cold life, but I love it. And, I can't get enough of this video! "I am a different bug. I'm the last bug you see before you die."
https://youtube.com/watch/...
-
When you're trying to find a bug in your parser/interpreter but it's working fine and all this time the bug was in the code you were feeding to the parser/interpreter. Smh2
-
That moment when you spend hours on fixing some bug, and finally discover that the problem is in another piece of code..
Literally, I feel I am on dumpiness overflow ! -
Happy Monday Ya'll, may your code be bug-less and JIRA unfilled.
(I know none of this will happen but damn it dream will you) -
solutions architect was questioned because a bug was found on her code... she said... "just ignore it". 6 years later and a lot of extensions and boilerplate additions, here i am.. fixing it.1
-
The error in database entry was negated by a bug in front-end code. Two mistakes cancelling out each other!
How is your day going ?5 -
Me when I am trying to fix a bug and I skip the part of the code where the bug is, because I am sure it is correct. https://media.giphy.com/media/...
8 -
Just spent 3 hours trying to understand why my compiler isn`t even trying to compile my code until i found out it was a known clang bug.
-
That feeling when you find the god damn bug after 2 hours.. however, it made me better understand my code, so thank you tiny bug❤
-
When was the last time you fix a difficult bug and you make a crazy lunar laugh that makes you lost control of your saliva?
~ I can tell, you code fiercely.2 -
Have you ever gone through your code line by line and still can't figure out what the bug is...
That's when you know you have ghosts inside your computer4 -
The next major war seems more likely to be started by a bug in someone's code than an action taken by a world leader.1
-
So you find out a bug in your own code... a bug that nobody noticed in the month it was out and about... because nobody used that feature the manager asked for in one of those mood swings... that yet you so had so carefully built with love...2
-
How to know that you need a rest?
You see a code:
```
public function scopeEnabled($q)
{
$q->where('disabled', false);
}
```
And assume that you have a serious bug...1 -
Just woke up covered in sweat after dreaming about reading code and frantically searching for a bug.
I think I do have the flu. -
First thing that I do with weird bug: trying to execute buggy code inside runOnUiThread{} / DispatchQueue.main.async{} and see if it works ¯\_(ツ)_/¯
-
Working now 8 months at a company. (C++)
Every feature becomes a refactor and a code clean
Every bug becomes a refactor and a code clean
Every Refactor becomes a code purge. :/1 -
I had a bug in my code, I was sure I fixed it but when I tested it nothing was charged. I asked my friend to take a look, and when he looked over my code I found out what the problem was: I tested with the older version.
-
Ever happened,.. ? the whole Application crash due to a bug in one of the libraries used and you skim through the code a million times, make a billion changes but the app still crashes.2
-
This feeling when you finally fixed an annoying bug in your code that gave you headache for days... :)
-
When you reported a bug using Google's own sample code. Only changing the list item count = 1 will cause it to never display the data. Yet being marked as **WorkingAsIntended**
-
I was fixing a bug, wrote some code that was really neat, still it looked like to much.
Then I realised I could change my code to 4 simple rules vs 50 -
Nothing like trying to fix a product breaking bug in someone else's code that just ran off on vacation for a week. 😒1
-
I tried to convince the actual bug that landed in the middle of the code on my screen a few minutes ago to pose with my (AWESOME!!) stickers. He was lonely among my compiling code and took off so you get me instead :)
-
Bugs are just undocumented features...
Im that case, all the code i have ever written is all just one huge bug. -
Rule: NumberIdunno,
It's easier to figure out a solution yourself than it is to clean your code, recreate the bug in a small snippet then posting it on Stackoverflow.2 -
If you're making code changes without a Story or Bug ID, you're doing something wrong. Take the 30 seconds and open a story to track your friggin work please.2
-
5000+ Lines of Code for one IntegrationTest means you are dping testing wrong.
1 day work on software 1 week on tests.
At least I'm now sure I didn't create a avoidable bug.2 -
Sometimes I'm so overconfident that I don't test some parts of the code I write and then curse myself when QE finds a bug1
-
Somebody write more and more ugly / incomprehensible lines of code for 1-2 beautiful line.
But the bug is always in ugly code.
I hate these programmers, I hate these programs!1 -
Comments throughout code with things like "changed to fix bug #". And commented out code all over.
We have source control, why the hell are you doing this? -
I spent 3 hours without find the bug on my code. I just found, I installed the library but not the plugin
Django + Django excel + pyexcel_xls
:( #WIN1 -
Me: Writes tests while fixing bug
Supervisor: "I'd suggest fixing other bugs and then picking up test cases"
Well the reasons we have so many bugs is that you let our off-shore devs just write code with ZERO code coverage!! -
"Bug fixes and performance improvements" - what I actually mean is that I shipped some dodgy code & this patch covers my humongous arse...sort of.1
-
Anyone know any nice code quality tools/bug finders (besides find-bugs) plugins for Intellij IDEA?2
-
Every freaking time I think I've fixed my bug and can continue, I see a secondary bug showing up making me revise the code that I previously fixed..
At least I keep myself busy I guess. -
Q: What will be left in your code if you remove all the bug causing statements?
A: print("Hello World!") -
Legacy code: the digital equivalent of a haunted house. Each line of code holds the ghostly whispers of past developers, and every bug fix feels like exorcising demons. Welcome to the developer's graveyard, where the skeletons of outdated tech lurk in every commit. 💀👻
-
I spent ~12h working on a simple issue/bug.
7h was spent on rebuilding local dev environment which is a clusterfuck of maven profiles, tomcat, some autogenerated degeneracy, and 2 different build systems for JS.
5h spent on actual bug fixing, code reviews and so on.
FML2 -
when windows 10 crashes and your vagrant takes AGES to get up after windows forced reboot on the crash.
Also found a stupid bug in some validation code I have written. SHAME.1 -
Shit. Today I had to code some required Migration Script for a Client. Deadline tomorrow.
It's nearly finished. But the Last thing isn't working correct.
I'll try to find the bug when I am at Home.
Yeah. I hope I Can find it.
But.. but. The FUCKING TRAIN WAS CANCELLED. SHIT! I have to find the bug you piece of Shit!2 -
Oh, my ex-senior wrote some code for uploading files in his last project lets use it! It will be easier!
Discover it has a bug and spent couple hours to fix it! -
That feeling you get when you enter in a piece of code for a bug fix...#aweekofbangingmyheadonakeyboard
-
rant. Tried to fix a weird bug in gamemaker, with some unfamiliar technic, resulting in another bug. Then one hour later, still no solution to that bug until I look around in the code seeing that I already used the exact solution that fixes the first bug.
In gamemaker there are scripts. I tried to forcefead the fucking script with a variable when calling it. Inside the script, there where already variables working fine with the extension or what-to-call-it:
other.(insert variable).
And that pisses me off. -
Code doesn't lie, but sometimes you really feel like it is. Just curious, is there anyone here that has ever actually found a bug with a platform?2
-
Working with microcontrollers is like another level of frustration.
Beside the code not working you are on another level, which is the hardware not working...
Once spent 6 hours searching for a bug and in the end the "bug" was swapped cables for communication.2 -
Time since the last bug caused by blindly copying code in a if/else and forgetting to change a variable: 0 Hours.
-
Yes, the bug is always on our side. Other teams are immaculate and they write the purest, most perfect code possible.
-
Get a bug report, look at the code: it was fix a month ago by... Me. The look on the face of my colleague like I'm a wizard or something: priceless1
-
Not sure what's worse, finding a bug in my code or waiting in a garage for 3 x tyres to be fitted and tracking to be done on my car! 😱1
-
Just a Thought
We are not creating any feature
We are just directly implementing bug/error at first place and resolving/fixing that thing with adding more code to it1 -
Hey guys!
I am looking for good "whats wrong with this code" snippets with as little lines of code as possible!11 -
Code base is full of /*bug fix - XXXX */ coments, sometimes it feels the software is a Bugenstein's Monster!!
Not sure if this kind of comments serve any real purpose...
Commented old code is a more familiar monster; but that's a tale for another day. -
Guys, I'm refactoring a server code from es5 to es6 and I would like to know how to get es6 errors like when I'm working with React. I have installed babel, and I can compile es6 code but I get errors that target the es5 (compiled) code so it's not easy to find the bug sources5
-
A guy asked me today why his code wont run and it didnt even have a single ; or endl; i straight up ignored the guy later he was all hyped he told me that the huge bug had beeb not using ; this noob literally taught he solved some huge bug....4
-
Looking for the keyboard Elliot uses In season 1 on mr robot and I found a bug
TECHNICALLY it's displaying the correct CSS...just the CSS code instead 😂
2 -
My reaction when one little bug causes the whole Code Construct to come crashing down: https://giant.gfycat.com/ImperfectU...
-
Have you used Postgresql with EF Core code first? My migrations don't run. It says in correct syntax near GENERATE. I don't know if this is a bug or I'm doing something stupid5
Top Tags
Weekly Rant
View