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
-
When you implement a 3rd party payment system, and it doesn't work... and their support can't fix the problem... So you debug their code and send them the revised code and they update their GIT repo and update their documenting.
14 -
*can't figure out why code doesn't work for hours*
ugh fuck this.
*angrily leaves for bathroom break*
*come running back*
I KNOW HOW TO FIX IT!!!!6 -
Reading through legacy code, only to discover the comment:
/*
* to the poor guy who has to fix this
* ...
* I'm sorry
*/3 -
My friend called me for help with her CSS. I was like no problem go to Teamviewer.com and install that software. 10 mins later she called saying teamviewer didn't fix her code. I'm done!4
-
"If it's not broken, don't fix it"
Follow that and you will be blessed with lots of ugly, duct-taped, hacky and unoptimized code -_-11 -
This fucking customer...
I've told that person so many times that they need to FIX THEIR CODE, because it get's pwned all the time.
To make stuff worse - they are still using Debian 5, and we are unable to upgrade because all their shit will break.
I found his fix today - he installed an old version of NGINX because it is "better".
No fuck you.10 -
When you're trying to fix your code but you don't want to delete anything valuable so you just comment out half of the file 😂8
-
/***********************************
/* a temporary hack, fix it later *
***********************************/
That was 7 years ago. I mean it was last edited 7 years ago when a temporary hack was created. It is now a permanent solution as nobody know what we are supposed to fix
.... Nothing is more permanent than a temporary fix. Not even clean refactored and tested code.13 -
How to fix an error?
Just comment out the code in the actual framework which throws the error, than fixing your code.😂😂
4 -
*Doing a Peer Code Review of someone senior to me*
Me: This fix doesn't look like it will work, but maybe I don't understand. How does this fix the defect?
Senior Dev: *Blinks* It works on my machine
Me: But how does it work?
Senior Dev: It works when I run it on my machine...
Me: Do you know if this will fix the issue?
*Silence*
Never seen QA punt an issue back to development so fast.7 -
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 -
I've never had a code review.
Eventhough I proposed to my boss that we at least review our intern's code once a week, he doesn't think it is needed.
Our intern writes ugly, shitty code...
it usually takes hours for me to fix his abominations... but yeah, what the boss says is always the best.3 -
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 -
My dad said if I fix his old car then I can have it once I pass my driving test. I can't seem to find the source code...18
-
Code archaeology.
Almost everything I fix/update/build requires a ridiculous amount of digging through and carefully studying the mountains of neglected, decaying, and shoddy code that make up these projects.
I spend maybe 10% of my time (and likely closer to 5%) actually writing code now. I miss it so much.7 -
A week in code:
Mon: Write all the code💻
Tue: Review all the code🔍
Wen: Fix all the broken code🔴
Thurs: Deploy🚢
Fri: Review all the code🔬4 -
When my manager asks me if I can fix all the bugs on the board by the weekend: 'look, I have a covenant with God: I don't do miracles, He doesn't code.'4
-
Saw this from a friend of a friend of a friend and made my own meme.
2 unit tests 0 integration tests. Hacky code to fix it.
3 -
You write code.
A strange issue prevents you to proceed further.
Try one fix. Fails.
Try another Fix. Fails.
...
Try fix #28. Fails.
You decide to ask for help in the support forum.
You start writing your post, mentioning everything you've tried so far. You feel your social anxiety and fear the humiliation of being told "because you didn't try X, you idiot". Then you come up with an idea for fix #29.
(fix #29 normally involves Wireshark or similar low-level inspection tool)
Try fix #29. It succeeds :)5 -
No, listen to me. I cannot approve this PR because your code does not comply with our code style. All the imports and annotations must be sorted in ascending order by length. They must all make fir-like blocks of code. Because it looks nice.
Now go and fix your code
I just smiled and walked away to obfuscate my code with firs . I had no idea what to even say to that... I still don't14 -
My school's mascot is the duck, but I like to think that someone had some heavy code to fix up and just took over the campus
2 -
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
-
Senior Engineer -
Hey. I have a code that hits API to get details and multithreading is implemented. Can you just change the URL formed to hit Api?
Me
Yeah sure why not.
Me
After some time I discover that the initial code itself wasn't working 😐
I realise i need to fix code, fix multithreading and then make the URL changes.
Just finished......Realised had to rant....1 -
*PM looks at my code
*Deletes my constants, replaces with inline strings
*Changes order of conditions (that I tested)
*Hits save --> autoformats code into shitty looks
*Commits: "fix"9 -
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 -
Fibonacci for developers.
One Developer writes bad code and leaves. Company hires two more to fix the code and cycle continues. Now you know why software developers are in demand.2 -
Lately I've been losing sleep dreaming about how to fix my code, but client I have been praying hard to make you happy 😜😜
3 -
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
-
Invited by a company who desperately needed me to fix their messed up code and the reception lady talks crap and threatens me.
:(
Guess who is not replying to their emails ever?4 -
- Let's use jquery to fix this
- No
- But it will work just fine
- I'd rather re-write the code and not use jquery in an angular project
- ...
- NO!10 -
Manager: "<third-party vr app> isn't working. Think you could fix it by tomorrow?"
Me: "I can't fix it without the source code."
Manager: "Didn't you install it?"
Me: "I did, but I'd need <third-party>'s source code if you want me to make changes and that problem would probably take at least a day to fix."
Manager: "Can't believe you don't have the source code. Aren't you supposed to have your code available?"
(Just....)18 -
I had a dream last night about how to fix a bug in my code.
I couldn't sleep the rest of the night because I was too excited about fixing it.
Plus side: the fix worked this morning.
Down side: ive drank so much coffee I can smell color5 -
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 -
CEO: if we would not give new features, clients would be bored and would not pay for tool.
me: but don't you think we should fix buggy old code, that would reduce effort and time that we daily invest in prod bugs?
CEO: I'm not saying we should not fix them but we should maintain the balance which is 80-20. 80% of our work would include adding new features.
😑
Next day in morning receives email:
There is a production issue, fix it asap.
😬10 -
Lecturer who is supposed to be teaching us to program somehow cannot debug his own code, instead I am telling him how to fix it... 🙈3
-
Just spent 10+ hours refactoring a code, and at the end I've figure it out a one line fix to the problem... just wasted 10 hours of my life.. :)7
-
I took my old project and I was like "Why don't fix it and open source it?". So from 2785 lines of code in main class, I've cut it to 1662 lines of code while keeping same functionality plus some more...4
-
while(freeTime == true) {
if(iHavePlans == true)
waitUntilDone();
/*
* TODO: Fix bug that causes
* coding to call the gaming and
* relaxing methods so often...
*/
code();
}7 -
Devrant...
... give me the serenity to accept code that don't work
... The courage to fix code I can
... And the wisdom to find the typo before I throw my pc out of the window.
Amen.2 -
How much legacy code do I need to understand and fix before I add Software Archeologist to my LinkedIn?6
-
Code comment rant of the day... fcking excel just cost me over half an hour to fix the fking formatting...
1 -
If ever your code breaks, just utter these words and it will magically fix itself:
"Wtf. Hey [coworker name], Can you sanity check this code? I don't know why this segfaults! It looks fine but you just run it and it bre- oh wait... I swear it didn't work a minute ago."6 -
Has anyone told themselves they just want to fix one thing, then have it turn out to be writing a whole new class with 385829 lines of code?1
-
Coding has taught me that there are 10 kinds of people...
* Those who code for a living
* Those who want you to fix their laptop/printer/phone/etc.1 -
Here's to the next orbit around the sun y'all!
Hope we all push unit tested code with the least number of to-do's, and fix more bugs than we create!2 -
My Friend: putt all the code into one huge file
Me: hey, there is an issue
Friend: go fix it by yourself
Me: Where is it
Friend: Don't know
There weren't even comments 😡2 -
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 -
when you know the code is inefficient but they wanted it fast so you say "fuck it, I'll fix this later", but you never do...3
-
??????????????????? 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 -
ENV: *runs flawlessly for months*
DEVS: *deploy a code change*
ENV: *crashes and bursts in tears*
DEVS: "PerfEng Team, your environment is broken! Please fix it ASAP" -
*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 -
Spent 4 hours trying to fix a problem which fixed in just 4 lines of code.
My wife feels sorry for me.5 -
Found this in a code review today.
Technically, I guess, that is one way to fix a divide by zero error.
14 -
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 :) -
Monday morning: The last straw.
After talking about in a previous rant about how my client wants to fix bugs that keeps popping out after bug fix.
Today I discovered, that all C-levels, worked all Saturday to "fix my code" because it "didn't work" and we "needed bug fixes not pretty things".
The app version I was working on for the last week is gone. Without mentioning that their "CTO" wrote a fucking crappy code to disable features that I added, breaking the build step.
This shit is enough for me, I'm done!3 -
No. Just no. The null pointer exception didn't come from my DB, it came from your Java code, so go away and fix it.2
-
Me in front of an year old code snippet:
1) "omg, wtf did i write that time?"
2) "i'm going to fix it"
3) after 2 hours lost trying to get new code working... reset from git
4) look around feeling guilty -
I need a room to scream. Fuckin fuck every asshole cunt who sees shit code and decides its ok to write more shit code rather than fix it, absolute fuckin cunts10
-
!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 -
So, a friend of mine just got a NullPointerException from his shitty Java code, and decided to fix the problem by catching the exception.
Great fix bro, real smooth..1 -
tl;dr - My company makes me pass around code over email. Is this normal?
How we fix bugs at my company.
1. Simulate bug in dev env (ok, cool)
2. Get the required code from svn and make changes locally (so far, so good)
3. Deploy changes in dev env and test (yeah!)
4. Take screenshots of fix in action along with the files you've changed and mail it to the respective leads (really? send code via mail?)
5. Keep changing your fix based on feedback and keep repeating above steps (what!)
6. Once approval mail comes, check-in your code in the svn branch for deployment and testing in the test env (QA team)
My question to you fine folks is, is this normal? Is this how most companies work? Passing around code over e-mail? Where the different versions of your fix are just attachments in emails. Or have I committed a sin by being a part of this heinous act?9 -
Looking at broken code you're going to fix:
"I know visual studio, I know...the pain will all be over soon, I promise"1 -
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 -
Web dev prob:
When you modify a code then refresh your browser, It doesn't change anything and you think your code has the problem, Modifies 100+ lines and refreshed the page, still nothing happens. Asked someone about it, Fix? Fucking cache! Fuck you google chrome!10 -
#FuckPHPInTheAss
>Start working on PHP after ages.
>Found that mail() is deprecated through server support
>they suggest to use PEAR Mail
>Suggest to use deprecated PEAR code
>Fix deprecated code and magically runs on localhost
>ohmygodyess.php
>try to run on server
>fuckMyLife.exe
>Try using PHPMailer
>WTF is this How the fuck this works?
>Spends hours to understand with example code
>WorksFinOnLocal.exe
>NopeIWon'tRunOnServe.lulz
>about to use YiiMailer.
#Sleepless24 -
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
-
"We've refactored most part of the code to follow best practice. Many of the unit tests are broken. Please help us to fix them all".
Me: Oh joy!!!5 -
1- Copy/Paste (code)
1- Googling before trying to fix a bugs by myself first.
1- Never finish my side projects.
2- (Worst) Still doing all the above.3 -
When you come to work eager to code, and the whole day goes to trying and failing to fix some network shit -_-2
-
I think there is always that guy in the company who makes shitty code, and someone else needs to fix/rewrite it. but he is always good with PM and superiors.
-
Reviewing code in a project, found this one:
# Todo: Fix horrible parent member check. People may have been killed for better code
-- horrible code here -- -
So I had a guy in my team, all day shouted "shitty code this, shitty code that"...
Today I had to fix some things, seen some really crappy code, said to myself "I've got to check who's the author of this beauty"... It was him... How the fuck can you shout shitty code on other peoples work when yours ain't better?!?6 -
Code FUCKING Rape!!! that kids is when companies throw lots of creative and talented programmers / coders / developers at a system and say FIX IT!
-
Sometimes, rewriting a project can be faster, more time efficient and better to read than trying to fix the single inefficiencies in parts of the code.
-
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
-
When you boast to your dad/mom about the code write,
And they ask you to fix their washing machine.
:'( -
Client: "documentation, oh you mean those grey texts the previous code guy wrote on the code files"
Me: I kinda need more than "grey texts on the code files" if you want me to actually fix the system and implement the new specs.
Client: oh you mean the Microsoft asp books
Me: It's a Laravel system sir, it's php not asp.net
Client: what are those?
Me:.................2 -
Troubleshooting code...
Me: "ok cool did that fix it?"
Program: [same error]
Me: "alright, so can I break it harder?"
Program: [new error]
Me: "now we're getting somewhere!" 🎉2 -
you're doing a code review and you ask for a simple fix and the reply you get back is: "that's not my code. I just copied and pasted it from somewhere else."1
-
Dear Managers,
Don't just have one person maintaining something forever. Don't ask that one person to also fix an issue in a module just because they merged in that code a few years ago. Don't ask them to fix issues introduced by others. Grant leave when requested especially when there is no formal leave policy and they are sick.
Fuck you.2 -
I have to fix a memory leaks of two jest test files of
2 FUCKING THOUSAND
lines of code each.
The End.15 -
!$rant
Well I feel accomplished today :) Got a lot done on my little devrant-widget project. I'm gonna try and make it open source soon, just trying to fix all this spaghetti code I created xD -
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 -
There is always that one guy.. who doesn't give a fuck about testing and thinks he's not responsible for them...
Le Guy: lemme just push ma new code maan
Jenkins: Unit Tests failed - pls fix
Le Guy to the one who cares about testing: hey fuck uu, ur stupid tests are failing... fix them its ur problem.
*sigh*7 -
Had to fix a bug in flask App built by 3 ppl !
So I some how roughly figured out the code and was trying to fix.
The bug was
I click on submit, two times the record was entered into database.
(Second time, duplicate error).
So to figure out ,I just commented the code which inserts to DB!
Whola!
Now only one record is inserted!
I still don't know where it's actually inserting !, And IDC , problem fixed
Shall I boast about my skills!?😂3 -
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
-
When the legacy code has a misspelled CSS class selector but it'd break more than it'd fix... And forced to use the mispelled word. Omfg people.1
-
Gah! Person in work has an issue I suggest a fix and even give them the bleeding code. For them just to say it won't work due to x y and z, I know it will work heck I use this 'fix'. Then later someone who has been there longer gives them the same fix and they are suddenly all appreciative. Ffs wouldn't be so annoyed if this was the first time this has happened.1
-
Just committed a code review change with a heart emoji included, Turns out Crucible does not support this and it broke the code review, Spent the last half an hour trying to change my commit message to fix the review
FML6 -
CoWorker: I fixed the code so it doesn't throw any errors or warnings anymore.
What He did? Well.. he just commented the whole important part and it's my turn now to really fix this C mess.1 -
That time when one of the npm modules you use gets a patch that contains a breaking change. You fix your code. Then a week later the module patches again and revert the breaking change. :/
-
The moment you hear that a piece of code you carefully cleaned up (which was 'needed' and took days to fix) is not going be used and better be thrown away... 😠😑😣😒3
-
So...
How i thought development looks like in my pre-coding days: some crazy assembly code.
How development really looks like: spending three days googling how to fix background color of Spinner in Android Studio..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
-
Why people are saying Python is an easy language? I mean yes, if you write c/java code with python it may seem easy, but writing proper python code, in a pythonic way is not so easy.
SO DON'T TELL PEOPLE THAT'S IT EASY LANGUAGE because new commers later they come with absurd code and ask people to fix it.7 -
duration = startTime - endTime;
So much facepalm
(I may be an hypocrite... https://devrant.io/rants/384227/...)1 -
Hi everyone.
I wish you all a 2017 full of code, of problems to fix, of oportunities to learn new languages and above all full of bugs to fix because from this, is from wherr we learn the most. -
Pic without code as my light bulb has burned and I will not be able to fix that this week.
But I can update the picture later.
1 -
Golang code review be like
> oh no, you used prohibited `else` keyword
Context? Dosent matter. Its banned, mkay?
Fix? Oh you know its hell to read now22 -
Every time I talk about a bug/error in my code with my colleague, I end up coming up with the fix myself while explaining it. I accidentally use him as my rubber duck...3
-
Right now I need to fix 10 years old php code handling data sets coming from a database. Normally I work mostly on C#.
God, do I miss LINQ!8 -
Sometimes I get bored and fix people's shitty code on stack overflow for fun
It's actually entertaining...
But as infuriating as you'd imagine4 -
In my current team, when someone else's code breaks, I fix it. When my code breaks, I also fix it. I feel like there's something wrong here...1
-
A colleague is walking me trough some of the source code because we try to fix an issue.
colleague: Oh we don't use this anymore
Me: ...
LATER
colleague: This part we should refactor someday
Me: ...
LATER
colleague: Oh I think this is old code and does not exist anymore.
Me: .. .. ...
Great Colleague BTW :)
PS: fix will be posted Later.3 -
Typical Git work flow on a feature branch:
Commit#1 : The silly feature itself that took 10 minutes to code
Commit#2 : Added unsaved files
Commit#3 : Fix unit tests
Commit#4 : Fix
Commit#5 : Fix
Commit#6 : Fix
Commit#7 : Various Fix
Commit#8 : Added unsaved files
Commit#9 : Merge
Commit#10 : Fixed unit tests
Commit#11 : Code Review tasks
Commit#12 : Revert- Code Review tasks
Commit#13: Refactor part 1
Commit#14: Refactor part 2
Commit#15: Deleted unit tests
Commit#16: Added checking for null
Commit#17: Completely different feature's bugfix
Commit#18: Code review spacing corrections
*Approved*
Trying to merge, then merge conflicts.....2 -
TL;DR: Clients are still dumb.
The sequel to a previous rant ...
https://devrant.com/rants/1210209
——
Client IT Lead: "We've loaded your code into our website, but *this* particular part of it isn't working."
Me: "Fair enough. I'll make a fix and have it deployed."
... an hour later, my changes are deployed, and I notify the client that the fix is live ...
CIL: "Thanks for fixing that so quickly! Just a heads up, but I've noticed that some of our own code needed fixing, so I've gone ahead and made some tweaks <that will most definitely break your code>."
... another hour passes ...
CIL: "Hey, so, I don't know what happened, but that fix you pushed stopped working."
——
🤔🔫 -
After 30 minutes of trying to figure out why a guid is empty, I realize it's because it is initialized, but not assigned.
I'm not ready for Monday. -
make dumbass solution duplicating code because you can't figure out how to do it correctly
nobody corrects you on code review
later somebody on another team has their stuff broken because of you and kindly offers to hopefully fix and not break what you got out of it3 -
I'm pretty sure that I have some guys inside my computer that sometimes fix bugs or break builds overnight without me even touching the code.1
-
Reading through old post-it notes and found a TODO that says "fix code" with no indication of a project it refers to lol1
-
When a website you use doesn't work and you have to fix it yourself.
Looks like someone hasn't been testing their code before pushing it live...tut tut2 -
Last year i had to resolve a really annoying bug, and figuring out how to fix that was a HUGE PAIN IN THE ASS.
Now i have to make some adjustment to that fix, and the only comment on that piece of code is: "this is a huge mess, good luck if you need to modify something".
FUCK YOU MYSELF FROM THE PAST3 -
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 -
Them: let's do iterative pull requests
Me: Great, can I have a review
Them: Your code touches a code that doesn't feel right, I can not approve this folly unless you fix following 30.000 lines:7 -
today when I was asked to fix some code I couldn't help but count if those variables where used more times :D
2 -
Man all I ever do is fix bugs in a giant overgrown calculator, that has references to code before I was even born. It might be new job time
-
Picking up some uncomment code:
var_dump() and console.log() everywhere
1h later: shit I think I lost it again...
2h later: It was a 2-3 lines fix..
fml1 -
How greedy can you get?
> boss takes half assed gdpr project : branch xyz
> branch xyz requires deprecated version of npm/node
> I re-install node this time with deprecated version
> Wow this node is configured with ant build
> ECMA 5, config but code is shit as fuck
> still I get the job done , cannot test it because code is shit as fuck and I will never any thing to fix that un healthy code
> code doesn't run on client side,
> no shit Sherlock
> get a call from boss, it urget look in it and fix it -
I was finally able to fix this other persons code when I accepted the fact that they don’t know what the fuck they’re doing1
-
Everyday I come to work. I feel miserable. Everyday write code. Fix difficult bugs. Go home dinner sleep. Tomorrow repeat.
I am reading Jia jiang's story. Mel Robbins 5 seconds. Christ grace's lectures. Still feel miserable. What is the meaning of life? All I want is to teach people code.7 -
I felt so good after revisiting a project and everything runs ok
Code readable
Managed to pick off where I left off and fixed some existing bugs
Added new features and uploaded the update2 -
Don't try and fix parts of the code that isn't 'broken' in the clients eyes.... You'll spend hours fixing something they'll neither appreciate or understand
-
When having to fix parts from an other programmer's code, do NOT concentrate on the small code expected to be wrong, instead read and understand the whole program around it!
Best practice:
1) Why is this code here
2) What does this code do
3) How does the code solve the problem
(just happened to me 😅) -
principle software developer who does not code, design, or architect,
instead, do random eslint fixes which create conflict with everyone's branches.
1 line of code "fix" per commit.
there goes 26 commits1 -
When McDonald's janitors are writing code...
Dev1: *creates a MR*
Code: for each HTTP request do
// stuff
Executors.newFixedThreadPool(validators.size()); // effectively meaning will start 7 new threads for each incoming request
// other stuff
Dev2: ^^ ??? Fix that shit. This will cause performance problems.
Dev1: *updates the code*
Code:
// stuff
int THREAD_NUMBER = 10;
Executors.newFixedThreadPool(THREAD_NUMBER);
// other stuff
Everyone: 🤦♂️🤦♂️🤦♂️🤦♂️
Can I BE facepalming any more?4 -
Google did it again. Damn.
Create a project in flutter -> Android code AUTOMATICALLY GENERATED is full of errors that i can't even fix.
One of the biggest tech companies, 2020.7 -
FUUCCK! These two lines of code just cost me 6 hours of debugging... At least I learned I need to fix my Deserialization code too.
servicePassword: this.APIUsername,
serviceUser: this.APIPassword -
The overwhelming code smell when you finally got a chance to do a quarterly project-level code review as a team lead.
It's my fault for feeling like they are teaming up against me, and I don't know how to fix it.8 -
When an app repeatedly crashes, has a bunch of open bugs and you think.
"Oh just give me the code I'll fix it myself!"
Quickly followed by the realisation that you're now channelling a young RMS... -
Fuck being asked every time if I fix computers, Bitch I code in them!
It's like being asked: do you fix cars? No? But if work using your car, how come you don't know how to fix them?2 -
I hate the jitsi_meet package, so I decided to fix the bug myself instead of waiting for the code owner to fix it. I forked it and pulled requested the updates. All they have to do is review, test the updates and merge the code if there's no error.
And the fucking problem was wrong data type, old version of Kotlin was used, and was android embedding V1 instead of V2. Solved by a "little" adjustment of the code. I wonder do they test the code before publishing their packages?
For those who are stuck on the issue, you are welcome. Now you have the solution.
Refer: https://github.com/gunschu/...
1 -
* 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. -
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 -
I fucked up my sleeping schedule and I don't think I'll be able to fix it... just as the code I was trying to do because of deadlines on sunday and monday.5
-
Repair printers... Somehow writing code translates to the ability to fix any printer problem in their minds.2
-
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
-
In the programming aspect of CS, you should have to debug and fix a previous student's project for your final grade.
You don't really learn to appreciate the value of clean code until you've had to fix shitty code. -
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...
-
Helping to fix legacy code on a staging server. No version control (at least not that I am aware of). Besides rare code comments, no way to see the author, time, or even purpose of customizations that have been made. No fun!1
-
The struggle when you have to work on your muscle memory every time you get a new laptop/keyboard. For extremists - using someone else's keyboard/setup to do a code fix.7
-
So, today a developer from a web app consuming our services requested to fix a 429 http error code (too many requests) they are seeing. The request is on an email with our managers cc'ed4
-
TMW your showing your boss your code and the output, then asks if you can do something else with it. Knowing that it's implemented you try it. Massive amounts of bugs. You think it's a simple fix and make it worse by quickly trying to fix it. Then he leaves. You undo a few changes mess around with the code for a minute and then everything works fine again.
TLDR: Bugs show up when your boss is in the same room as you. Disappear when he's not.1 -
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
-
That moment when you find a function called with faulty arguments or a referece mistaken and fix it and code actually works now aaaaand you wake up.. i started to dream about the same code cause i keep rewriting it for different reasons.. what a life
-
Not sure what's better on Friday:
Fix the bugs and push it to prod so manager will be happy.
Or sit there like a dumb fuck and wait for Monday before touching the code2 -
When a friend told you that they have a problem and needs a Computer Science student's help ..
.. and it's about a broken flash drive.
I can't even fix my broken C code let alone fix a freaking flash drive.1 -
Maintaining shitty code is a lot like playing whack a mole. Fix one thing, something else breaks. I wish they'd just let me replace this garbage already. Could've been done by now.2
-
When your code misbehaves in production and you need all the ducks in the world to fix the problem😂😓
(Marshmallow doing some serious debugging!)
1 -
do you guys also dream about code or is that just my brain? i swear to god, if i see something awful at work i dream of a way to fix it7
-
That one line of code that you know the logic of it and you know what is causing the error, but you can’t fix it!3
-
When your co-worker asks you to implement a fix for a problem in his code..
Reading yourself into his code, then you see him having fixed the same problem several lines above in another method. -
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
-
Who here listens to Coldplay."fix you" when you having bugs in your code and it seems you will not have a break through...6
-
Do the hard stuff first. Then everything else looks easy. Make a mess of the code, then fix it and make it efficient.4
-
I'm too embarrassed to show my team leaders code to other developers..
unreadable, no tests, parameters hardcoded..
But managers want to "help him grow"..
When do you decide you can't fix a lemon?4 -
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 -
This is a group sin.
We'd get the code checked and then run it straight to live. No test environments no real back up in place or process for releasing.
Just run code in if it broke run fix 1 through 3 until you got it right. That was two years ago. -
I thought my project would break on an edge case and I would have to spend 2-3 hours rewriting some code to fix it. Turns out I had already thought about that edge case when implementing that functionality (which was like 6 months ago), so nothing breaks and I don't have to fix anything. What a pleasant surprise!3
-
Writing code for software that was deprecated since 2015 it's a nightmare. More when the unit tests take way more time than the actual fix or feature. Just kill it with fire
-
coding all day long and then realising that you haven't commented anything...
after all, deciding not to comment your code because you are lazy and sure that you will know what you did in every single line of code when you were writing it... and then 2-3 month later blaming yourself for not commenting when you have to fix bugs or rewrite the code! damn! -
Best: complain about the security issues we had, later got the green light to fix them
Worst: at an intern my boss asked me to create some shady code... and I did it ... 😅 -
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 -
think I've hit that stage of my life where things break faster than I can fix them
from my body, to my code, to even my hardware9 -
Sitting on a hot chair in this hot weather working on a hot laptop to fix some ..... not very hot code.1
-
Nothing like trying to fix a product breaking bug in someone else's code that just ran off on vacation for a week. 😒1
-
Wrote some code, not realizing code has TOCTOU race condition until a healthy 4 hours later, and the fix was to move two lines of code upward. I hate me, myself and I.
P/S: What happened to PrivateGER, devTea and linuxxx?3 -
Just reed a comment in the fucking shitty codebase im working on :
/* temporary fix */
I’m fucking done guys !
2 -
I can't find a website I used years ago... maybe someone here remembers its name.
It was a place with daily code challenges, real time code battles, you had to fix bugs, syntax errors, you could choose different programming languages, and receive points based on the number of chars used to fix the issue, etc.
I hope it still exsits, it was really fun.
Thanks in advance!5 -
Arg, Visual Studio 2015, stop trying to fix my comment indentation!
It's a comment and. It is NOT part of the code. Leave my formatting alone!!!3 -
So my day's going pretty well, successfully managed to create a pull request for broken code that breaks more code and run into errors trying to fix it, then spill tea all over my desk/self spazzing trying to fix one child problem like 3 levels deep
Pretty sure I'm the office dunce at this point1 -
When the new guy changes the format of the code and fucks it up and you have to go back and fix it... slowly raises gun to head
-
Intellisense that would fix all my typos! 😜
I want it to be that good that I can just squirt on my keyboard and it still recognizes sensible code! -
That moment when you have issue reports from clients about someone else half complete rushed code that got through yet someone else review... I'm not gonna fix that myself...
-
I was asked to fix a bug delaying the app's email notification. When I opened the notification code file, I saw this comment previous developer wrote, it goes like
-----*This code works 70% of the time, if I try to change anything, the whole profile breaks. Please do not touch this code!. It does not worth the try*-----
Now I don't know what to do😂😂 -
When you get to the stage of just praying that your code will magically fix itself .........
Yeah hmmmmm -
When your coworker is so slow that your boss wants you to fix the coworker's bugs. Even though said coworker has nothing better to do, wrote the code and probably knows exactly where the issue is.
-
New piece of code which should work perfectly and solve your problem but it is not working just because you forgot to remove an old piece of code you were trying to fix the same problem! Fuck my life!1
-
> trying to make project using old version of specialized toolchain, exposes toolchain issue
> fix toolchain issue
> fix small typo issue in code
> linking spews ALL the errors at me and fails
-
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 just spent like an hour trying to fix some piece of code and guess what was the problem? a fucking TYPO! That was so frustrating LMAO (laughing but crying inside) T-T1
-
This code is so horrible I'm too scared to even fix bugs.
No I did not write this code originally.1 -
This code is huge ! THAT MEANS IT HAS HUGE BUGS !
FIX AND PATCH !
FIX AND PATCH YOUR BUGS !
Basically the reason I want to work on a big codebase one day is to be able to scream that
Winks if you get the reference (just so you know, I didn't read it fully)2 -
I’ve had to fix code that was “working just fine” until someone decided to “make a small change.” Programming is like a never-ending game of whack-a-mole 🐭. But hey, at least we have our clever jokes and endless supply of energy drinks 🥤 to keep us going. 😂3
-
Lay out exactly how you want a jr dev to fix his code, only to have him ignore all of it except that a certain library will be used in the fix.
-
When you're having to add BS/hackey conditionals to your code because the other dev is too damn lazy to fix their code.
-
TFW you get to work and your colleague is like : "Hey boyo you got bugS to fix on that code we pushed into production"
As I was just having a better outlook on my life -
I have been helping out a teammate with a code fix but never wants to try my code solutions, instead he always complaints about it, even if they work and comply with the conventions. (I am his dev lead)2
-
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. 💀👻
-
When you add console.log above your buggy code, but after 15 changes you forget to update the real code and you spend 15 minutes scratching your head because you can't fathom why your last change didn't fix the problem...
-
Junior Colleague: can you help me fix this small issue in my code? I believe it's located in this file...
Me: *spends half an hour deleting console.log, inline comments and blank lines*7 -
When you hit the deploy key, on crap code written by someone else... not caring about Operating..and you realize: OMG iam the poor DevOps guy, who has to fix it.
-
Stall.
The problem you were trying to fix, when said stuck position became apparent, will probably no longer exist in a couple of days. Hence no stuck to become unstuck from.
Delete code causing stuck position. -
Jeej first project. Read: 101 FE bugs to fix. In code i've never seen before. With bare minimum support. Though day. First steps with Gulp are set. yay1
-
Sweet merciful crab. Solved. Now I must never ever touch the code again because I barely understand what I did to fix it...1
-
don't you just love it when you have to fix a system that consists on unnecessary junk code, horrible/lack of indentation, no documentation and the clients says "I don't know what happened fix it and I'll post you good"
I mean, I live for this shit man! -
VS Code terminal is so bad... it is basically the worst part of VS Code; the devs can never fix it
The terminal in VS Code breaks for me all the time; it is so easy to break it; all it takes is change the size of the terminal window and bam, it is broken
The devs should either fix their shitty terminal or remove it entirely because it confuses people; I literally see wrong output from my program because of their terminal1 -
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
-
/*
Quick fix for issue#666 : Generic evil
no code changes required
ignore run time errors
and it'll eventually run just fine.
*/
DROP TABLE religion;7 -
When something is still broken after I fix it
When fixing one bug creates two more bugs
When I am too lazy to do anything at all
When I have to fix bugs in code I did not write
Whether the sun is shining or not,
whether it is hot outside or cold,
I always feel the same...1 -
To put online a self-sufficient SaaS which I don't need to debug, fix or update myself, as I'll have some code monkeys do the work for me.
-
When I get one with constructive feedback. It's rated since I'm usually the one that tells people their code sucks.... After it causes a production issue.
Yes no one does a proper code review on my direct team.... Just the stuff a linter would tell you to fix.... -
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. -
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
-
Radeon graphics driver crashed again.
I hope one day they will actually fix it but the light of my hope grows dimmer every day.
Hire some talent?
Rewrite their code in Rust?
Do some static code analysis?
Better modularity?
Some code reviews? Proofreading?
I am at a loss of words. The crashes need to stop.8 -
Today (Thursday) I have an interview and exam today, but won't be able to attend because somebody broke the production code and we need to fix THOSE Bugs ASAP.
Top Tags
Weekly Rant
View