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
-
Meeting with asshole partner company CEO at restaurant.
Me: "I'm a bit worried about the bugs in your API. There are some ways to retrieve privacy sensitive info from public endpoints"
CEO: "Well, we're a rapidly growing startup!"
Me: "Uh... so?"
CEO: "So... Move Fast and Break Things! Priority is to improve our API further, and we'll fix bugs as they show up"
Me: "Maybe you should stop trying to emulate Zuckerberg in your management style. You know that even Facebook themselves admitted that their slogan was a retarded mistake"
Waiter shows up at table. CEO orders some overly expensive fish salad.
CEO: "Well, they have done something right... they're worth billions"
Waiter asks me: "And you sir, have you made your choice?"
Me: "Do you serve popcorn?"
CEO: "Popcorn for lunch?"
Me: "No, for your congressional hearing"16 -
I once changed all my error messages to say “Processed successfully” because I had a demo yet the software was very buggy.
I bought myself time to fix the bugs later.
#demoHack7 -
Dev: Ok issue fixed, you just need to log out and back in again on your end to receive the fix
User: It’s still not working
Dev: Did you log out and in again?
User: No why would I want to do that?
Dev: It’ll reset your locally saved login information which is causing the issue
User: I thought you said the issue was fixed?
Dev: On our end yes, we just need you to reset your end in order to receive the fixed version
User: Look I have been dealing with this issue for 6 months. Fixing bugs are your responsibility. I have too much to do, you have to get this fixed. *click*.
Dev: Yeah you submitted the bug ticket yesterday night though
Email from users manager later that day: <User> is saying you are refusing to fix this bug. This is unacceptable. Fix it or else I will escalate this. Also there are other bugs we noticed today too, fixing them is absolutely critical!
Dev: …
Dev: What other bugs did you notice?
*no response for 2 weeks and then:
User: Hey you can close this ticket, the issue seems to have resolved itself.
Dev: ….muppet.17 -
Mom : why were you late?
Me : Got lot of bugs in office.
Mom : Is everyone alright? Did you kill them?
Me : No mom we fix them.
Mom : I thought we kill them.
How humane are you guys.9 -
Watching my coworkers fix bugs is like watching people untie knots by pulling hard on both ends, in the hope that the rope breaks.1
-
When a system-breaking bug ends up fixing a different bug and actually produces a new feature we didnt intend but actually love
5 -
Just who the fuck from apple thought its a good idea to make the FUCKING SCROLL BAR overlap, the FUCKING PROPERTY ARROWS, everytime i accidentaly hover over it? I cant change shit! I have to wait few seconds every time i accidentaly hover over the scrollbar so i can be able to FUCKING CHANGE the value!
Dear Apple Inc,
Fix your shit! We're paying 100$ a year for what? More bugs and toruture? I didnt sign up for this bullshit! Give us back some real quality products, or just buy the company Jetbrains and let them build the IDE for you instead.
12 -
This is the kind of comments that helps you to smile while you're getting a headache trying to fix your bugs :D
2 -
Client gave another agency access to their site while in contract with us and lied about it. Now they want me to go in and fix the bugs they caused. I reinstall the backup from the last time I completed edits and things were approved and working. Client is mad that pages are missing and ads are going to 404 pages.
Me: "Didn't you say that there haven't been any changes in the two weeks since I completed your last edits?"
Client: "Well yeah."
Me: "Then there shouldn't be anything missing."4 -
My boss is still forcing us to support IE11. Recently, we started having even more bugs with one of our vendors on IE. We filed bug reports with the vendor to fix it, and they came back with "no. Why would we fix anything for IE11? Not even Microsoft is fixing anything for IE11." Boss's answer: well, let's make a separate component for IE11. Probably using flash and/or silverlight. We asked about redirecting IE traffic to Edge, he said that's "the nuclear option." So, doing the thing that Microsoft suggests, that involves not much work at all is "the nuclear option"; ignoring industry standards and recommendations, introducing well known security vulnerabilities, losing money, and trying to circumvent the vendor that serves out our major product, however, is totally reasonable. Our IE traffic is less than 3% of our users at this point.24
-
Once browsing through Google play store under what's new area of an app i found this:
*Removed bugs
*Added bugs to fix later6 -
Answer from 3rd party software company: "we can't fix these bugs because it requires development on our side".. hehe, yeah, no shit 😂4
-
How the fuck does these testers find these bugs
there are like
- go to this
- click on this
- type the first 57 digits of pi
- sacrifice your first born to the devil
-> there the table is misaligned by 13 pixels, fix that14 -
When your boss says "good job, you have developed something big in such a small time" (~2 weeks) but you haven't showed him the bugs and shit (gonna fix it btw)
3 -
They made a full fucking application in MICROSOFT EXCEL!!!!!!!
who the fuck makes an app in Excel? Though it's used internally, it has over 100 users and Everytime there's an update a new file is sent to all of them by mail. They use different excel files as DBs and tables as sheets. It's even got a fucking UI with check boxes and drop-downs and shit
Now guess what my task is?
Understand that entire application from the Excel files and make a webapp to cater to those requirements.
Fuck documentation, there are bugs in the Excel file and I need to fix the bugs in my app
Some good soul please tell me how must one start analyzing an Excel sheet to understand the logic behind it. Or a tool that magically converts "excel applications" to webapps25 -
So today is Monday. A bug report comes asking to be fix. I feels weird reading the report. Then I check the codes.
SOMEONE MESSING WITH MY CODES!!!
The other developer codes a very un-dynamic function that gives birth to bugs. Know what? He replaced my original codes with his faulty codes. 😑 😐
3 -
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
-
In my current work, I have two systems to work on (let's name em Systems A and B). Both basically do the same thing; both allow users to book facilities available to them.
System A is already in production. My job is to fix any bugs that come up on said system. System B is an improved version that they wanted me to develop. This would follow a different framework etc. I am already halfway through this system.
Now, here's the fucked up part. The code for system A is a massive clusterfuck. It has unused commented code dated back to ancient times where men had the brain of an ape.
And don't get me started on the fucking logic. One part of the code was to retrieve and display the timeslots available for a chosen facility. The code to do that alone takes up 500++ fucking lines, filled with ajax commands, html manipulation and commented, unused codes..AND THAT'S JUST THE FRONTEND!
The fucking backend was not a problem of smelly code anymore. Nope. It was like a programmer had code diarrhea and shat his backend code all over the project. If I had a pin board, I would have made a crazy wall just to understand what some fucknut was trying to achieve.
Anyway, my supervisor told me to fix some bugs on System A. Knowing how the code was, I told her that I could refactor the code. Since I've already achieved that function on System B, with a shorter and cleaner code, I could just copy that and use on System A. But nope. She SPECIFICALLY told me to just "do whatever to fix the bugs. I don't want to waste time on System A." Okay. Makes sense to me. Whatever. I didn't wanna fuck my head up looking through that mess of a cesspool. So, I came up with a few hacks, not thinking of clean code and fixed whatever bugs there was. I then just pushed to the repo (after testing of course).
This bloody morning, supervisor came in and gave me more bugs to fix. When I thought she was done, she said "Hey. I saw the fix you made to the system. The bugs are fixed but the retrieval of the timeslots is now pretty slow. Could you see what is the problem?"
Slow.. She said that it was slow. And asked if I could fix it. I already told her what the problem was and she did not want me to waste time on it. But she wants me to fix it. WHAT THE FUCK IS WRONG IN HER BLOODY HEAD! I SWEAR TO GOD... UGHHHHH I swear I was already waterboarding her in my head. YOU WANT FAST?? How bout fucking allowing me to refactor the code?? Fucking shit head. I think I should take up yoga.1 -
Merge request
Title: Fix bugs
178 files, +615, -743
And it had passed review by not one, but two (allegedly) intelligent people.
HOW. THE. FUCK?!
Luckily I am overtaking that domain and won't allow such bullshit. Mainly because I will be the author of the commits.17 -
PM asked us to skip the unit test and just deliver untested application to SIT environment due too tight timeline. But when there are defects raised by tested, PM asked why got bugs and asked us to fix them immediately while we have to develop other new features at the same time.5
-
When you are given a task or bugs to fix and your boss will tell you everytime that, "this is so easy this will be done in just 3 seconds".
WTF! Then don't hire devs and do it yourself! And start fixing all the damn bugs in just 3 seconds yourself! There are 28800 seconds in whole fucking 8 hours, I guess if we divided it by 3 you can finish a task or fix a bug at approximately 9600! (Applause) Now we are silently calling him "The 3 seconds man'.4 -
If I died, I would have one regret.
I once worked in a code base whose messiness would make an oil spill in the fucking pacific ocean look like spilled milk on the floor in comparison.
Naturally, it had bugs. Oh BOY did it have bugs. Most of them were taken care of well enough. Or about as well as anyone insane enough to work in that code could.
There was just this one bug, which I still (un)fondly call "my bug of 2 years". It. Just. Didn't. Make. Sense.
It was written in JavaScript. Naturally. Which by itself, is the metaphorical programming language equivalent of a pile of horse manure. But this bug. It was the guano icing on top of the horse manure cake which is JavaScript.
I LITERALLY spent 2 years trying to find a solution. I woke up at night, thinking of explanations. I had dreams about fixing the damn thing. And I never did.
On the day I left the job, I had to pass it on to a friend (who hasn't solved the fucker yet either).
I hated that bug with all my heart. But..
Now that I think back, all the books I read, all the docs that I scoured, every non working fix I coded and every failed efforts I made on it, eventually made me a better programmer.
So cherish your bugs and issues. Sometimes, they come, not to hurt you, but to help you grow (unless you use JS, those bugs just wanna fuck you).3 -
So I've written the c part for deploying the NN to the drone. Now I have to wait for the guys who are actually the creators of this platform to fix a tiny bug in the quantization process. Then I can test my code and see the 100000 bugs that I have.
https://github.com/FullMetalNicky/...
4 -
Old boss story. This guy was nice but a terrible boss. Also relevant, he has a background in IT so should know better.
Him: So when you wanna check a password is correct you just unhash it in the database?
Me: *facepalm*
Me: Hey we should be doing unit and integration testing at a minimum to lower bugs.
Him: We don't need those, we're not a bank. If a problem comes up we just fix it and push to production.
(A while later)
Him(in email): Why do we keep getting bugs reported. Don't you devs test your code.
I was mildly annoyed at that one.
Him: We're always over budget on projects, how can we fix this.
Me: What if we increase our quotes.(technically there are other ways as well but not really possible at that time)
Him: We can't do that, clients won't want to pay.
Me: *finishing off my handover as I'm leaving for a new job*
Him: Wow you do a lot of work2 -
Boss: do you remember the other team? we need to fix one of their bugs
Me: amm, okey np
Boss: do it when you have time, but don’t forget to finish your things first.. and we need that fix by the end of the day.
Me: //what a beautiful monday <3 -
Out of all the bugs, the most annoying are the ones that come out and make me say "WTF?!?!? WHY THE FUCK HAS IT BEEN WORKING FOR THE LAST 2 YEARS??!!?!!??? THERE"S NO WAY IT COULD HAVE!"
When the bug surfaces, you investigate and see that it indeed IS a bug and there's no way it would ever work w/o a fix. But then SOMEHOW it's been working just fine for years....
It's like server elves went on strike and said "no more, it's enough covering that bug - it's time you fix it, lazy-ass idiot!"11 -
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 -
Hey all - I made a big update to in app "x replied to a rant you commented on" in app notif to try to fix some bugs/scaling issue.
Please let me know if you notice any weirdness/notif issues. Thanks.5 -
I wish my clients would stop reporting "bugs" in my app that are legitimate results calculated from crap feed to it by their upstream systems.
Just because my app is easy to use it's the first place that they find out that their ecosystem is fundamentally broken.
GIGO, people.1 -
Two friends and I are about to publish a side project in two weeks (for an open Beta) it feels good but I am kind of nervous...
Today I found new bugs and I don't know yet if we have the time to fix them all...
Do you have any tips / experience you could share with me?13 -
It's my 2nd week into my new job. I asked people what they think they are doing.
The summary:
Senior dev: we fix bugs
Junior dev: we write code
Intern: we create the future
It depends how you look at it. They are all called software engineer or developer.9 -
"Why does my app have so many bugs!?"
"Why does literally nothing work!?"
"How come you cant fix these problems soon enough?"
...
Me: "remember how you didnt account for testing in the budget or development plan?"
"No"
Me: "thats why."2 -
Happens every day:
"could you please fix those bugs ASAP? Testers are waiting for it"
*resolve the issue and inform the requester*
(two weeks later)
"Thanks, I'll inform the testers they can begin their tests"
Ugh, how ASAP makes everything seem so urgent and important
-
boss: we should map all the possible ways to do things in the system so we can test them and make sure we fix the bugs.
Me: yeah, well, that is exactly what automated tests are for, every time we find a non-mapped way that breaks this we make a test out of it and fix, this ways we end up mapping the majority of ways.
Boss: yeah,yeah ... Let's sit down latter and map everything on a document.
I bet my ass we are never gonna have tests as a part of our workflow.3 -
It's my first 'rant' so be kind :P
When I started my studies a already knew some very basic programming stuff. I went to the exercises with another dude I met. We always joked about the tasks we had to do and did other things while the others tried to fix bugs in their code. After the semester ended he asked me whether I want to work part time at his mother's office. I went to the interview which was weird because I have never been to one before but got the job straight away. I'm in my fourth year of working there because the team is awesome.5 -
I spent the last 3 months trying to hire new developers for my team. I found someone experienced who is great and a graduate, who is, well, a graduate.
For some reason he thinks he knows everything about our framework he has never used and seems to think he knows how everything works in our codebase which he has never seen.
That’s fine. I’ve had my share of cocky developers.
But what confuses me is that when I ask him what critical bugs are left, he reels off two significant ones. I ask what it will take to fix it. Of course he says he knows how to fix it. So I say great. Then fix it and let’s move on to a more fun part of our project.
Suddenly he didn’t know where he problem was and so I told him he had to investigate and come back with something concrete.
It’s just frustrating managing this developer who is deceitful.10 -
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 -
Happened at work a few months ago (I'm new to devRant, that's why I post this now):
"I have bugs!" - "Then fix them..." - "No, come here and have a look, I have bugs!"
He literally had a bunch of very small insects inside of his monitor, don't ask me how they got there.1 -
Twitch Developer Rig sucked hard and was cropping my extension down to 300px high no matter if it was “panel” which should be this high or everything else.
So I posted to their forum and they committed a fix MINUTES later.
That’s how you deal with bugs. -
Noticing a bug once or twice but not being able to reproduce it after that gives me anxiety. This job is detrimental to one's mental and physical health. Serious question. How to unfuck yourself?4
-
On the twelfth day of Christmas
programming gave to me:
Twelve bugs in public branch
Eleven errors to fix
Ten freaking warnings
Nine Windows Updates
Eight blue screens of deaths
Seven minutes of compiling
Six servers down
Five Android Studio crashes
Four angry stackoverflow devs
Three kernel panics
Two burned graphics cards
and a one broken-dick piece of shit JavaScript framework4 -
LPT: NEVER accept a freelance job without looking at the project's source first
Client: I have a project made by a company that is now abandoning it, I want you to fix some bugs
Me: Okay, can you:
1) Give me a build to test the current state of the game
2) Tell me what the bugs are
3) Show me the source
4) Tell me your budget
Client: *sends a list of 10 bugs* Here's the APK and to give you the project I'll need you to sign an NDA
Me: Sure...
*tests build*
*sees at least 20 bugs*
*still downloading source*
*bugs look quite easy to fix should be done under an hour*
Me: Okay, so, I can fix each bug for $10 and I can do 2 today
Client: Okay can you fix 8 bugs today for $40??
*sigh*
Me: No I cannot.
Client: okay then 2 today for $20 is fine, I want a refund if you can't fix them today
*sigh*
Me: Look dude, this isn't the first time I am doing this, aight? I'll fix the bugs today you can pay me after check they are done, savvy?
Client: okay
*source is downloaded*
*literal apes wrote the scripts, commented out code EVERYWHERE
Debug logs after every line printing every frame causing FPS drops, empty objects in the scene
multiple unused UI objects
everything is spaghetti*
*give up, after 2 hours of hell*
*tfw averted an order cancellation by not taking the order and telling client that they can pay me after I am done*
Attached is an image of a level object pool
It's an array with each element representing a level.
The numbers and "Final" are ids for objects in an object pool
The whole string is .Split(',') into an array (RIP MEMORY BTW) and then a loop goes through each element in the split array and instantiates the object from an object pool
5 -
Too many clients watch one or two development videos on Youtube to then 'school' me on how to fix bugs... if you're such an awesome dev, why hire me? :)
2 -
When your company buys a third party solution and you spend all your time emailing them about bugs in their system.
Seriously, I even sent you the exact line of the bug in your JavaScript with a suggested solution, and deployed a new stack with your latest (broken) fix so you can test out that solution. Then you email back saying it is fixed but it is clearly still broken. If I email you a fixed version of your file will you deploy it? OMG!1 -
corporate emails and what they mean
- “changes to our privacy policy” — we raised capital, time for you to leave! good times are over.
- “changes to our pricing” — we are basically acquired, leave now.
- “blah blah community help blah blah” — fuck you, we can't even be bothered to fix bugs in our product.
- “blah blah 30% off blah blah” — yup, the unsubscribe button was broken last time you clicked it. -
People on devRant: "it took me 1/2/3 hours to fix that bug, omg, what a time waste!!"
Me: *wrestles some bugs for 1/2/3 DAYS*
I'm confused, how is fixing a bug within hours a ranting material...?11 -
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 -
Merry Christmas as well to all the people who have to program, monitor servers, fix bugs and all the other stuffs!
-
Google: buys Android
Makes tons of $ from Ads
Meanwhile 7 year old bugs
Are still not fixed
A bug reported in 2012: recently created files are not visible when using MTP protocol.
Guess what? I still have this bug on my 2017 phone, like many other people.
Probably has something to do with file cache.
Because obviously 7 years is not enough to fix a stupid bug. Especially when Google is busy implementing all the other features nobody asked for except marketing department4 -
To everyone who wanted the JS library to do the blur like in one of my other rants, I want you to know that it's close to be finished. I just have some blur position bugs.
I think tomorrow I will finally fix that bug and publish the library on Github.
The linked rant: https://devrant.io/rants/888497/...
I will maybe do another post when the project will be on Github. 😉2 -
So i have been working with a so called python expert my manager on a project.
He has 3 years of more experience in python than me.
The best thing is he shows up everyday with random post from stackoverflow to fix our bugs everyday.
And if the code is in python2 he says that only difference is just put () around print and it will work
🤦♂️
He earns thrice as much i do3 -
Maybe not worst, but most frustrating. One of the systems I helped maintain at my first job had a few different bugs that caused bad data in the database. The "solution" to the problem was to write SQL queries to directly fix the production data. This would take one member of our team (it rotated weekly) about an hour every day to fix because there were literally dozens of these errors.
All the devs knew that we could identify the root cause and fix it in, probably, 3-4 days tops. Management would never approve the time because it would take longer to fix the root cause than it took to fix the data.
I worked at that company for 7 years. The bug was there when I came on, and it was there when I left.2 -
Changing between projects multiple times a day is as annoying as a homeless chasing you while begging for heroin money.
Today was one of these days I had to fix bugs for 3 different projects with completely different devStacks. The productivity dropped to a new low. Being a fullstack dev is awesome, but please let me do one thing at a time, so I can stay focused!
Dear boss, just fuck off with your managing skills or there will be ultraviolence soon!6 -
When I arrived at my new job last year they were working on developing a large site using a live server with all the devs ftp-ing every change in the build process to test it. 😵
It was not uncommon to hear 'is anybody in the style sheet?' being shouted across the office!
Needless to say, I had to fix many bugs multiple times when my fixes were overwritten!7 -
My senior developer says he wont fix any bugs that are reported by any user in the company, because bugs will appear anyway.
I think he needs to change job2 -
The ability to understand every codebase immediately to the point where I:
* don't need to rely on the documentation
* know exactly where bugs are
* know how a change (bug fix, new feature, etc.) affects other areas of the project recursively
Obviously because it's a waste of time hunting that occur when modifying a codebase, no matter how carefully one writes tests or tests their code, something could always sneak in because it's not always apparent how a change ripples through your codebase.
It's tiresome and especially annoying when working with core modules1 -
Fuck this completely abysmal CMS!!!!
Not even god damn Einstein would be smart enough to understand this stinky pile of legacy code!
No, it's not enough to write an HTML template in PHP with less than 500 lines of code, noooooo, every god damn template HAS TO BE AT LEAST 3000 FUCKING LINES OF CODE WITH RANDOM INCLUDES EVERYWHERE!!!
Every fucking thing I fix spawns at least 2 new bugs! I FUCKING CAN'T!!!
I swear, if I meet these fucking worms of developers... someone will eat fresh turds mixed with puke from a highway toilet!17 -
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 -
An iOS app which was basically a wrapper for a giant jQuery eForm.
~5000 lines of custom JS and it broke ALL THE DAMN TIME. A team of us worked on it for about a year and all we ever did was fix bugs. But the bug count never went down. The bugs just got replaced with more bugs.
Thankfully its not live anymore.
After the global thermonuclear war, all that will remain is cockroaches and jQuery. -
Any Stardew Valley fans?
I've made a little something.
https://nitwhiz.xyz/projects/...
I know there are some bugs (such as the Chef's bundle missing completely), going to fix 'em soon.4 -
Really?
Far far away in a small startup, one developer was brave enough to try to fix the beautiful iOS application (hmm, nothing fancy just a broken, patched and served behind a wrapper).
To do so our hero needs, of course, a testing iOS device.
So the guy went searching for the testing device and asked around, then he returned to his desk shocked when I asked him what happened the guy told me literally:
- "Can you believe it? The boss gave the testing device to his fiancée"
and now guys you know why bugs in startup application take a while to fix :/1 -
Saw the following meme text on fb group.
"It took me 30 minutes to write the code. And 2 hours to fix the bugs."
But I thought it is not quite complete without this ending.
"And a single minute for client to totally dismiss everything." -
Developer of said repo notices the influx of activity, but then just updates the readme by saying there are bugs, not fixing.
Bro I just gave you a PR. Take the fucking PR and that will fix the bugs. -
So a follow up to my last Mathematica rant:
I have a JSON file made up of arrays of arrays of arrays with the outermost layer containing ~10,000 arrays.
So, my graphing works perfectly the first time for one of my graphs. I fix another unrelated graph, graph the whole file, and suddenly the first one stops working. The file read-in only reads in the array {2,13}. I double checked the contents of the file, they were as large as always.
Then, I proceed to look for bugs, find none, and decide to restart Mathematica. This doesn't help.
So I go back, find no bugs, and eventually am so fed up that I just restart Mathematica again, no changes.
Suddenly, the array reads in fine. Waiting for the graphs to come out but I think they'll be fine.
WTF Mathematica? Why must I restart TWICE to make bugs caused by your application go away?7 -
So I’m working on a project right and I don’t run it after writing 104 lines of untested code and it doesn’t work.
Which is expected but then I do some stuff and fix that, I get a new error which is great cause I’m getting closer.
Cut to tonight. I’m trying to hunt and kill this bug. And after doing nothing but copying the code to another text file so I can upload that copy and get help.
I decide to run it with a little just print statement in it to make sure it’s definitely broken and I’m not asking online for no reason.
And.. it works.. WHAT???
I uncomment the rest of the function and get rid of the print statement and scream because ITS WORKING!!
I MEAN IT HAS BUGS BUT THEYRE BUGS I CAN FIX AND FOCUS ON AFTER I FREAK OUT ABOUT IT WORKING AFTER ME CHANGING FUCKING NOTHING.8 -
Why is Drupal so hard to learn?!!!!!!
It feels like you are learning an entirely new language. Yes it makes hard things simple, at the same time making simple things hard to accomplish.
And also modules are buggy, you would fix bugs instead of doing your tasks.
I want to learn Drupal but I guess it is not friendly for beginners like me.12 -
Today was supposed to be the day we hook up the test suite and i fix the immediate bugs.
Today is the day none of the testers are at the office.2 -
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 -
I'd rather take a swim in a moist human massgrave than fix any more bugs of this cancer-inducing "selfmade" CMS developped by a "company" that shall not be named.
Sadly I am not aware of any such pit in the neighborhood, thus more bugfixing it is... yay ⚰️5 -
You guys work from home because of coronavirus?
Me on the other hand, have to work on weekend on my desk to finish an urgent project, it’s for the ministry of education (who closed all schools and launched an online courses) to monitor the effectiveness of the new platform and fix some bugs on it.1 -
*client comes to us "please take care of our app, it's ugly and the previous devs made it all buggy, especially the Android version"
*we write code, analyze bugs, fix them, QA them
*we deliver a preview
*client only looks at the iOS app, doesn't give a flying fuck to the Android app1 -
Today while trying to fix a bug, an actual bug came flying through the window and sat on my laptop. When I tried to make it flee, it went inside my laptop through the vent.
I guess now I have two bugs to deal with.1 -
I'm pretty sure my clients would fail the marshmallow test 9/10 times if not 10/10 times. We have a certain time period of the day set aside for me to look into new reported bugs but besides that I'm supposed to work on regular tasks. Of course, they ask me five hours after that time period is done, whether I can look into a new (non-urgent) bug. At the cost of the new thing they want to launch in 2 weeks. 🤔 I would love it if we actually had time to fix every single bug in the codebase but what typically happens is I get about 15 bug reports (most duplicates) and I'm expected to fix all of them in a span of 2 hours.1
-
Got a 1 day of alone time :) 8 hours WFH ant then the (almost) whole evening was MINE. Guess how it went :)
Coding until 2am and falling asleep on my keyboard, waking up on a cold lappy at 5am bcz its battery died and its aluminium frame was freaking freezing.
I know right? That was an awesome evening! I've managed to catch and fix some nasty bugs!6 -
Submitting a pull request seems a good way to end the week. That's what I love about (some) projects on GitHub; instead of just ranting about bugs or out-of-sync documentation, you can fix the problem and send a pull request upstream. :-)2
-
Was talking about how I implemented CI/CD in one of our projects as a starting point to others and how it worked by running tests and deploying to the server and one of my colleagues laughed about having to have tests at all, I explained and asked him what was he gonna do that morning, his answer:
"Well, I'm gonna test the system X and fix some bugs"
To what I replied:
"If you have automated tests you could have those tests automatic(?!) and they also help you finding bugs early"
Wtf do ppl have in mind that they prefer remediation over prevention and they end up wasting their time with shit that could be fully automated?2 -
Sometimes at the end of the day if a solution to a problem seems inefficient I just leave the task rather than writing buggy code. It gives me a day's time, away from the screen, to come up with much better and elegant solution which I eventually code up the next day.
After years of experience I have realised that its better to wait for a day and not write inefficient code rather than trying to fix a hell lot of bugs later.4 -
Left a php job because I was fed up with php and was promised I could work with different languages.
Start new job, 2 weeks of work with a different language. A few days away from completing the micro service and it's been decided it's going to be deleted and I've been told I'm now to fix bugs in php.
Actually given up on life. Dont want to go in. Want to work at KFC. Had enough of being a php fixer :'(
Feel like the job I was sold now doesn't exist.3 -
Back when I used be a junior fresh out of school, my senior used to say, when releasing a first version or a major version of any software, app or website always implement easy to fix bugs.
End users or clients, especially the ones that tasked you with the creation of it, will look for a bug until they find one, if it isn't one you will spent hours trying to figure it out, instead give them one.
You know how to fix it and the client is satisfied they found one.
To this day, i still do that, although mostly not even aware of it. Eg: I know that's a bug but i'll fix that when (not if, when) they complain about it.
I even find myself telling the juniors, i develop with, giving them similar if not the same advice.
And that is what experience means, skill is something they teach you in school.
Experience is what makes you a senior or a junior, not your level of skill or the amount of keywords on your Linked In profile.2 -
I've just realised something... I haven't ranted about work for a looooooong time.
It seems now all the monkeys have left the team and we've hired young people that actually knows how to get things done without blowing things up (though still need to work on documentation, bus factor still too high). So I'm no longer cleaning up their shit or the bugs they're too incompetent to analyze and fix...1 -
So after months of self study my company finally appoints me as a junior developer with a major client as the intermediate dev on the project resigned. My tech lead assures me that junior devs only fix bugs and do other minor changes. One week in and in our first sprint planning session the client decides to priorities a Major update to the app. Now I have 2 weeks to deliver what will either make or break my immediate career. And I have no idea how to implement any of the changes. Stack overflow you're my only hope (and many hrs of YouTube tutorials)3
-
CEO announced a bug bounty programme for devs to do stuff in their free time for additional cash.
Cash is decided by business people based on their idea of how complex the given problem is.
And it's not for bugs one could just find and fix. Only some fixes/features decided by them.
Like second shift.4 -
If I was independently rich I'd pay to work on software I use to fix bugs that it has.
Hello, Paradox Interactive, let me fix some of these roads for you.
Hello, Spotify, let me allow power users to make playlists be subsets of other playlists.
Hello, Github, let me create a tagging system to sort starred repositories.2 -
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
-
working on a crappy legacy site written by an invalid. The job was to replicate an existing site for a school with the original's permission. I fix a shit ton of bugs and update the original.
For the first time ever I got a phone call from the original's owner to complain that I had fixed their site -.-
leave things broken from now on!5 -
"Do not lose time improving the data pipelines from our ERP, it is about to be replaced!"
Then suddenly there is a week of bugs and stress because the non-improved data pipeline can't handle new situations.
"Just fix the bugs! It is all about to change anyway!"
Repeat. And repeat.
Fuck, I hate when managers think that there are such things as "temporary fixes" in ERPs. Or that companies can ever migrate to another ERP. Those things are forever, as Cheetos dust on your bowels. -
I really lost my faith in our profession.
A Software&Hardware solution that costs more several 10.000€ is broken after every update.
The Producer even achieves to break untouched features in new releases.
No communication at all. If you report Bugs, they are your fault. The whole system has absolutely no security at all.
It is unsecure by design.
And even if they hear your Bug report you have to pray that they will fix it.
Most if the time you have to wait the whole year for a new release tio get your bugfixes.
But there are also bugs that are untouched for years.
WHY? WE PAY YOU!
I want to cry4 -
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. -
Friend : Hey man lets watch world cup at 5.
Me: Sure why not, we will have a great time
Me: Leaves office early tho having bugs to fix
Me: starts watching the game at frds place slowly pulls up my pc
Frnd: Are you even watching the gamean, it was a goal now , did u see that , come on man
Me: ohh yeahhh goallll, goes back to vim
Game ends and he switches off the tv and stares at me for 20 mins,
Me: what hpnd man did the lights go off?4 -
example of my commenting on bugs to fix later
Before I found devrant:
//1-3-18
//when user goes to send mailing for first time
//we need to remove the message from admin
//which only displays on first time login, but
//may block the data we are looking for
// then return to parent
After DevRant:
//9-8-18
//when user goes to send mailing for first time
//there's a fucking stupid message that they
//have to read once which blocks the data we need
//so, goutte click that shit, then return to parent3 -
Our Excel file of critical bugs to fix before live went from 18 to 11 today. I was super happy... then I asked my colleague how he was getting on with his "Points from the designer" task.
It's another document which had 25 new points added to it this afternoon. -
My codes has mutate from a minor bug to a monstrous one.
It happened when I try to fix the minor bug. Looks like I add more bugs instead.4 -
The world's largest rubber duck is a couple hours from me at the moment, I plan to visit with all my major coding bugs and errors, hopefully his size and wonder will help me fix all the big issues my little one couldn't3
-
I think bugs are always my fault..
Still after so many years on this project I alwaaaaays go debug/recheck what I coded first before checking the old code and data...usually turns out it's something long before me that's still fucked up & buggy, but still.. I always think I managed to fuck up something.. :/ I need an egotrip/egoboost or sth.. but I doubt even this'd help.. I know my code is not pictureperfect, but still.. I never think it's good enough..and that it has bugs.. o.O I also have a bit sex daily so I dread to write/fix anything in js.. -
> do you feel sorry for freelancing contractors
> whose previous client abandoned them
> they ask you to help them fix some trivial bugs in the shitty code
> you believe you can change the world by going overboard by also improving the code quality, along with fixing the bugs
> initialize an empty file where you'll translate the shitty code into a more organized one
> start creating variables and generic functions which can be used in a modular and organized fashion
> meticulously document the first function you write
> realize this is not worth your time
> insert some glue code into the original code which fixes the trivial bugs
> glue code has hard coded values so it adds to the shittiness of the code
> submit the work
> get $$$ -
One of my coworker change the code from
```
void foo() {
if (condition)
{
}
else
{
}
}
```
to
```
condition ? ifTrue : ifFalse;
```
and add it to changelog
```
- fix bugs // yes with an "s"
- feature added
- some list of the bug fixed.
```
I refer back to the commit, only one Fucking commit and on changes. Bro, what the fuck?8 -
Project Manager logic (the best kind).
PM: Here are a list of the tickets we need to address next.
Architect: Hang on, didn't X raise a number of critical bugs yesterday? They were serious, we need to fix the critical bugs first.
PM: ... but he marked them all as critical
(so that means they aren't an issue? cool, i've been doing this wrong all my life)2 -
Well, that's one way of getting rid of bugs and creating other issues, since it never works out to have just random people fix never to be touched again systems
9 -
If you expect someone to help you with your errors/bugs, at least get some proper logs and explain what you tried that didn't work. Don't just spam them with pictures of errors or "something is wrong. Please fix".
I've seen people taking pics of their monitors. Half the code is eligible due to the glare -_-. At least take the effort of posting your code somewhere and sharing a link. GitHub would be the best go IMO3 -
Job security:
- Create bugs purposely
- Discover the bugs after a while (if you discover it too quickly it will look suspicious)
- Fix the bug1 -
Consultant: "I don't agree with that, it's got to be something else" when you point to a known fault with the function they are using in the framework.
Then you send them 10 articles from stackoverflow and the framework's own website.
Consultant: "Oh. Thank you."
Just let me fix the damned bugs and not have to justify every single fucking change I have to make to make the damned thing work the way it is fucking supposed to.
This is why we can't have nice things. -
So there is a mall here that idk how but has little currents pass through it's supporting rails. And every time you touch it, it gives you a little shock.
I have been waiting for about 3 months now expecting a patch fix when I realized that physical production bugs have no patch fixes. More than 3/4th of the population is unaware of a whole different level of bug fixing frustration. Damn1 -
When QA isn't smart and you spend way to much time talking and in meetings.... "Listen, we are only testing for new bugs related to this fix, if there is a pre-existing bug, document it and move on".
QA finds a pre-existing bug and stays fixated on it for 3 days....1 -
Not sure if yelling at someone for not listening counts as a fight.. 🤔 since he wasn't listening..ever!!
But yeah, my ex coworker was a champion in not listening and doing stoooopid shit, from not following orders, to cheking in all the files in solution to tfs (no changes + debugging shit etc) which made it a nightmare to find and fix his bugs.. I just gave up talking to him alltogether since he only wasted my time and didn't listen to any advice/order.. -
Me: Alright, new week, back from vacation fully rested and focused, lets get productive.
Apple(safari 10.3 update): Fuck you.
Basically the change log was:
*fixed critical security bug.
*added more bugs to fix later.
Well fuck you too safari... You disgust me.
The least the fucking imbeciles, or monkeys, behind safari can do is add a fucking css prefix. For fucks sake. -
Just got to test the app from the frontend team... Oh God why!!
5 minutes, found 5 bugs (c'mon testers!!)
Worst (and now it's a rant) why do designers insist on working with big screens and don't test it on a standard screen? You know? Those typical screens your users are using?
So, it looks great in a 24" screen but the focus is terrible in a 15.6" screen... No time to fix it... What should I tell the users? Works better at 85% zoom out? -_-
You just fucked up the main feature of the app! Congrats!!! The rest looks okay I guess3 -
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
-
Fuck inherited projects!
I was invited to work on a simple migration and integration project for a bank. Thinking it was simple and just a month long project, I accepted it.
... last August 2020.
Now, almost a year later, we have freakin gone nowhere with this project. The bank has had 5 project managers leave over the last 1.5 years that this project has been active.
And every fix I make brings in numerous other problems.
It’s so fucking insane.
No one knows who to blame.
I am currently in call with the bank with about 12 other people who are all watching me fix bugs that they find -.- -
Got a job as a fresher, had no idea what work I'll have to do.
Was given the task to fix some bugs that had creeped in due to update of some UI framework.
Having absolute no idea of front end, I started the task.
Have spent the entire last week looking through CSS, HTML, Javascript.
Have come to the decision of quitting the job.
Life is too short to be lived this way.7 -
I am surrounded by incompetent fucking idiots, from the team lead that does a half arsed job at coding and then wonders why nothing further down the chain works to whole component teams that seem to be lagging so far behind they don't even know what the current code base looks like.
And who's in the middle of it all running around fixing all the problems these fucktards create, why yes it's me.
I would leave to let it implode and see what they'd do but I already know, they'd leave it till I got back so I could fix it all for them.
Feel like going around with a rolled up news paper and whacking each of them on the back of the head while screaming "no, bad code monkey, bad, fix your own bugs"
I hate being the go to fix it guy sometimes.1 -
When your website is tested after months of efforts and then tons of bugs come up....
Gonna fix each of it..
Y am such a poor developer.. !!!! 😖😞2 -
Today was a bad dev day working on a shitty React project. Not that React in itself is bad, but it can be hell to work with when the code is a big pile a crap full of anti pattern code. I spent the day refactoring to try to fix a bug, but to no avail. It would take days if not weeks to put some order in this mess and to prevent such bugs.6
-
Had to fix all bugs of my colleague this night because our client was not happy.
Before he joined us he worked as a database admin and now he wants to learn web dev and coding. But he did so bad mistakes like endless loops or requesting api 5 times.
In so tired now, happy when its christmas -
Till now, hacktoberfest has been really bad more me.
Why so?
I got 4 PRs for my project, out which 3 were identical.
I reviewed them and commented to fix the bugs. The Unit Tests are failing and they don't bother to send out a correct PR. And they don't even bother to fix them and respond. They just want to make 4 PRs to get the free T-Shirt.
Just finish the PR and make it pushed to the mainline.2 -
Scenario after sending a build to QA:
(Monday)
Me: How's the build? did that app worked?
.
.
.
.
.
(here come's friday)
QA: The app didnt work on this part and there some bugs there, and please add this another module.
Me: okay ill fix that..when do you need it?
QA: today
Me: (just kill me)3 -
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 develop an Android app for my thesis
Rant: I am more eager to fix bugs/make my app better, than write my actual thesis on how the app works -
When front end developer start testing just before working hours are complete 😑 and you have to stay to fix bugs.6
-
wtf...
Ones of the best bugs I love the "most" are the ones where the fix is counter-intuitive, e.g. making smth seemingly incorrect to rectify the issue.
Like today, I crafter an SQL query to fetch some PG metrics. And postgres-exporter refused to accept it until I added an excessive comma [,] at the end of the SELECT block (right before FROM).
Like.. wtf...12 -
Fucking hatttteeee airports... I'm a developer not in fucking sales.
My boss let's me fix bugs at the client5 -
I work with a guy who is genius in his field, but doesn't have much ability outside of it, his view is we should all know what he knows and not bother him with bugs in his code we should fix the issues ourselves. Oh how the shoe was on the other foot when he needed help with a personal app.4
-
How are you supposed to fix bugs in your program where:
1. it has been investigated before and was not found how to reproduce it
2. it cannot be tested at all
3. never happens on the test environment
fml19 -
Dear app, if you say that your update is for bug fixes, you better fix all those bugs instead of releasing and releasing an update with the same bugs still there. Better look into the UI/UX issues too. Your app looks horrible! Last time I was involved in it, everything is looking so fine I haven't had a bad review for a long time. Hope you can read this. #ktnxbye1
-
Dev Goal : Fix the bugs you said you will solve in 2015, but are still open,
Because you know what fix to do,
And you are too lazy to do it.
And too busy, creating half baked, hacky fixes for new exciting problems.
:D -
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
-
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... -
Trying to sleep. Looking at devRant. See a f ew rants about bugs which reminds me of my bug. Get out of bed and now behind my computer trying to fix the bug. Hope it's a quick one so I can go back to sleep
-
Oracle, what's wrong with you? Why do you have in every minor release of glashfish after 4.1 weird bugs which cost several hours of debugging of the own software until discovering there's a glassfish bug occurring in typical situations but there is no fix in sight.
In 4.1.1 there was a bug in the admin panel which throws a exception if you tried to configure JMS and in 4.1.2 there is a bug which prevent finding and loading a necessary class for using jax-rs despite it's available.
I have do complete an assignemt until friday and such bugs are such a pain since i change so many thing just to find out that my first structure/config/etc. was correct. -
For the past 5 odd years my Bluetooth headphones wouldn't connect to my laptop properly and I had to issue a second Connect command while the first was pending to get it working. I even wrote a script to automate this: https://github.com/lbfalvy/...
Today Bluez finally released a patch for this. That's right, after many years, today the issue got fixed; Connect now returns an error if a call is already pending.
My headphones still don't work, but my workaround is now correctly recognized as invalid input.12 -
Me: //trying to fix bugs
IntelliJ: hey you have 2 typos
Me: Where? I can't see typos anywhere what the Hell
Me: //looks up and down my classes/interfaces. It's my name
Me:
Me: Well isn't that delightful -
Hate those bugs, where you stumble upon a fix but have no idea why it fixes it or what is causing the bug!2
-
the word bug has lost all meaning to me because all issues in the repo are labelled "bug"
That being said, the best bugs I fix are the ones where i can say its IEs fault and theres nothing i can do so i dont have to do anything because IE will never be updated -
Instead of actually fixing bugs, most of my latest PRs have been adding "debug features" that make me look productive but really just enable my total unwillingness to actually fix the bugs.1
-
I've come to accept the fact that when I first learn a new concept I'm not gonna know what the heck I'm doing with it until I code it for myself and break it and then fix it. Bugs help you learn.1
-
How to interpret when you receive bugs reported for your application?
Should I be happy that someone is using them or just be sad that I gotta fix them and how poorly I wrote the code.
Note: will obviously consider turning some of them into features. Though not all.2 -
I am going to rant about this here because there is nowhere else where I can "SCREAM".
My work process....
Working on a project that does not have mockups nor a plan. I am building as I go. Design, infrastructure, EVERYTHING. Because my boss is a "genius".
And the project goes like this....
1. Boss tells me to build something.
2. I tell him the functionalities and design.
3. Boss, "Figure out yourself and we will see how it goes".
4. Me, Builds something.
5. Boss does not like it and demands changes.
6. I make the changes.
7. Repeat.
1 year and a half for one project that is a simple e-commerce. Show the products, a search functionality, users sign in and can order and show their orders.
A simple page in which does not take time, but without a plan, without A FUCKING PLAN this project will go on forever.
I am losing my mind. I put on test and tell my boss to test it for bugs. He demands a meeting and tells me, "we need to add this".
OH FOR FUCKS SAKE. TEST THE SITE FOR BUGS YOU FUCKING USELESS THING. I WILL FIX THE BUGS AND THEN WE WILL TALK FOR NEW MODULES.
I am doing documentation, database infrastructure, front-end, back-end, testing (because my boss cannot do it. It took him 2 week to start testing for some things after asking him every fucking day "Did you test it", "Did you test it").
Maintaining out CRM for bugs and new modules and maintaining our company's website.4 -
I've been trying to sleep for a while now. Counting sheep isn't helping because now the sheep have a whiteboard and are writing down answers to fix my bugs :/
Edit: if you were wondering, there is 1 sheep as of right now -
> somehow decides to fix two bugs at 3 a.m, since they looked simple enough
> fixes bugs
> also causes a memory leak in the same JS script
> next morning the app compiled but kept crashing (duh)
> obviously cant remember what happened
> hangover doesnt let me think, i.e forgets to check the Local History in the IDE
> spends an extra 2 hours. -
I wish real world would have breakpoints and we could just go back to fix those bugs.
What is wrong with people... Trump, Munich, Ansbach, Nice, Brexit, Orlando... so many bugs to find...3 -
Who else is fed up of memes on Facebook like 'She was upset because I didn't talk to her. She didn't know that it was because I missed a semicolon in my code'
Really?? WTF compiler do you use dude? Because of such shitty memes, couple of my non-dev friends asked me how frequently I miss the semicolon in my code?! I said never because:
1. I am not a dumb coder to compile my programs with any syntax errors.
2. Even if I do, I fix it in a minute.
:| WTF really! These dumbheads don't make memes on bugs.3 -
You know what I hate? Git commit messages stating 'fixed tests' or 'fixed docs' or 'fixed integration problems'. You did not fix anything, fuckhead. You updated the code, introducing more bugs as usual. FIXED?! NO, UPDATED! That's what I hate.1
-
Xamarin is, hands down, the most annoying fucking thing I've worked with. Like more annoying than windows crashes and random fucks asking me to hack shit.
I am so tired and frustrated, after every work day. It's like I'm trading bug for bug.7 -
I cloned the most recent copy of my coworker's app so I can help fix bugs when we go live tomorrow. These are the methods in the users controller:
beforeFilter
isAuthorized
login
logout
dashboard
viewAllOrders
viewCheckedOutOrders
viewOrderDetail
addNote
checkOutOrder
rejectOrder
getUsersByOrderStatus
completeOrder
viewOrderHistory
search
admin_addUser
admin_editUser
admin_addClient
admin_editClient
admin_editOrder
admin_createNewOcof
admin_editOcof
admin_viewAllAvailableOrders
admin_viewAllClients
admin_viewAllCurrentOrders
admin_viewAllUsers
admin_viewCheckedOutOrders
admin_viewOrderHistory
delete
userUpload
admin_adminUpload5 -
Fuck Xamarin! Fuck Xamarin.Forms!
It's slow, it's full of bugs, it's missing basic functionality, it's rapid new updates breaking older frameworks, it's a shitty unstable IDE on both Mac and Windows, it's the need to frequently reopen files or restart the IDE to fix "intellisense" or the false compile errors, it's non working UI builder and previewer, it's connection issues with simulators, emulators and real devices, ...
Have I forgotten something? Probably yes.
Your dev customer for many years.1 -
So I have two bugs to fix, their severity don't make sense to me
One is classed Medium while it's just some changes in design and ergonomy
One is classed Low while it's a functionnality that is not working
Priorities ¯\_(ツ)_/¯3 -
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
-
Best feeling?
Just leaving the office with a well-working codebase. And no bugs to fix.... until tomorrow morning. -
Managing a small team - poorly.
I was in charge of testing a legacy calculations engine together with two scientists, for whom I set up a python and interop environment so they could test the engine easily.
The two were very excited at the thought of validating the calculations and in fact found many bugs.
I was very supportive, told them to fix the bugs and gave them a pet on the back.
All three of us were happy the legacy engine is shaping up, that's until my boss heard of it, and boy did he grill me hard for it.
Turns out our efforts were highly unappreciated by the client, whose only request was that we test the engine and report the bugs. Not to fix them. My goodwill cost the company a lot of money, since the client paid by the hour, and was now due a refund. Crap.
It took me a year to finally understood the moral of the story. Which is to always respect the client's wishes and convey maximum transparency to him. -
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 -
Tweet: Angular is slow.
Response:
vdom is worse than angular.
Then why not fix the stupid change detection strategy, broken form type/validations, late subscription bugs.
"Angular is for enterprise app".
This sentence means nothing.
Wtf angular community is so toxic
https://twitter.com/mgechev/status/...14 -
The best coworker I've had always wanted to fix everything! And most times he did. But sometimes his fixes created more bugs. Needless to say his name is Paul Ness so it made it even better hearing people say "PNesswhat did you do now!?" , that never got old. 😂
-
I'm currently working on updating our SAP Hybris code base (unreleased) to the latest hybris version ... god, there are so many bugs I could scream. SAP, how can you release such a saftware*, or wait the actual question is, SAP aren't you ashamed for that peace of shit you sell for 1M per licences!?!?!
Allegedly SAP has >100 people sitting there working on hybris. Every new version I wonder the same, when do the finally fix the bugs, improve performance, update the 10year old ant version, migrate to maven, remove the bloat ...
what they actually do is just add bugs and more bloat "§$%&/()=)(?/&%(&
* german "saft" means juice. A "saftladen" is a shitty company, "saftware" ... you get it right ;-)2 -
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 -
Today is one of those magnificent days for my code. One of those days where I stumble up on the weirdest bugs and pull a fix out of my hat barely looking at any doc. One of those days where I find out there is a very tricky flaw in our project design and yet I end up finding an elegant solution to circumvent future problems. One of those days where I find the informations I want even though the documentation is the worst I've ever seen.
I love that productive feeling. -
It not Christmas until you program a game you have be working on for the last few months. I've been gifted with two bugs today. Oh, what fun it is to fix bugs on a one horse powered laptop!2
-
Class normal people:
Def good day:
"Manager was out, had great lunch, got a. special someone's number, successfully avoided traffic, got in special someone's pants"
Def bad day:
"Stubbed toe this morning, rained all day, broke up w. special someone, sat in traffic for 2 hrs"
Class software dev:
Def good day:
"Wrote lots of working code, little to no bugs, checked in no-probs, ahead od schedule for ship, extra time for ping-pong!"
Def bad day:
"Somone fucked up the latest build, coffee machine's broken, ran out of adderall, manager on everyone's @$$ for a fix, 5 hrs later...no fix, no blames, no coffee, board meeting; fml" -
The best part about working on Someone else's UI bug fixes is that you get to look like a hero when you fix the bugs and make all their work look like a sham - asshole 101
-
Been ‘working’ on this game for the last 5 months now. I love making it but I haven’t gotten any where because there are too many bugs. Like, it’s all bugs.
I started the project when I started learning game development and with all the time I’ve put in it I don’t want to kill it.
Anyone else have a project that they are working on, where they don’t even make progress on it, they just fix bugs?2 -
Someone else updated a firmware and noticed that its worse than the older? The worst ia when you try to fix it and it broke another thing.
Too many bugs in a release (yes, a "verified" release)3 -
Trying to fix errors and bugs results in some weird behaviour
like I don't know how I went from making an app to cleaning the gutters on my roof but here I am -
Advice: always be thankful when you are the idiot because it is easier to change being stupid yourself than changing the other parties stupidity. Example: you can fix wrongly using a 3rd party SDK, but you can most likely not fix internal bugs in the SDK.
-
For future generations :
Bring back cocaine to coca cola.
Since 1904 Coca Cola no longer contains extract from cocaine leaves.
Drugs who made us.
If we live in matrix and we are simulated the general rule would be wipe bugs from the system so ex. if all of people were using cocaine cause they drink coca cola the wipe would be remove cocaine from the coca cola. That would fix the cocaine bug. Cause people in 1904 had almost no knowledge about how world looks like, they were using pigeons to deliver messages. If we bring back cocaine maybe we would also bring back those times, when everyone dropped cocaine in 1939 - 35 years old ourselves were fighting to death between each other cause of rehab.
I wonder how many of those non visual but only statistical bugs we have on this planet. Machine learning is just one of the tools we use to learn about them.1 -
Today I had to fix a bug and it took me about 2 hours to find out that it related to a bug in a component which doesn't belong to the bugs component. In development everything where fine. But after deployment the bug occured. Found out that when running Vue webpack projects in dev it handles errors different, kind of a global try catch block. After deployment the application breaks.
This teached me again that we should not ignore any red error line in console. -
The characters in Euphoria are living the life. Fuck, do drugs, get high, no feature to implement, no bugs to fix.5
-
#AskingForSuggestions
Suppose, you were given a project source code of an Android app, a pretty BIG sized app. You don't know anything about the code unless you read line by line. Now you were given a deadline to fix some bugs, but you don't know where to start or where to put breakpoints to debug. In that case, how would you do it? How would you debug the code?
Thanks13 -
Some idiot fixing bugs in production and overwriting files without updating his git repo when I pushed another bugfix live.
Boss to me: "it's your job to get the fix live!"
I FUCKING HATE MONDAYS!
screw performance i'm gonna run gulp.watch in production and just git reset it to last release when someone fiddles with files on the server :( -
Was given 2 bugs to solve and after 1 day and half someone remembers to tell me that what I'm trying to fix won't work cause the issue only happen in production an I won't be able to test it with the connection that I have...
-
!rant
Whoo!! Client's satisfied with recent launch of product!! Still has little bugs to fix here are there, but general feedback was positive, stating it's "much smoother" -
Boss: Ready for deployment?
Me: No, there's still a few bugs.
Boss: let me know when they are fixed!
(Goes back to desk, runs without any issues)
Me: It all finished.
Boss: Wow how did you fix it so fast.
Me: I have no idea. -
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! -
Please Santa, fix all my bugs for Christmas!
(i know it's a lot, i'm also happy if you help me with a half) -
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 -
Build pushed to production and is ready to be delivered to the client. May 1st today. Day off. Silently fix bugs and build.
-
Happy 1 of August to all Swiss lads on here. Let's celebrate by remembering the backlog of bugs some of us need to get fix by tomorrow.
-
The first company I worked for had a policy to not ship any release, service pack or hot fix as long as there were still open bugs with the severity "critical" or "blocker". They wanted to ship a service pack nonetheless, but without violating the rule and thus keeping their KPI unharmed. So the support guys got in touch with developers and asked them to lower the severity of certain "critical" bugs. They said we by all means need to write into the comments that the severity of those bugs has to be reset after the service pack was shipped, so that those important bugs would not be left behind.
- Support team violates the rules set up by themselves.
- Developers had the actual work of doing so (and the blame to catch).
- The Support team's KPI just remained unharmed.1 -
I don't get the bug "joke" that's flying around. If you have 99 bugs and fix one, why would you have more? Do you not have automated tests?4
-
After inputting all of the defect info into the bug tracking tool, QA writes a quick summary of their findings and goes home.
Love explaining to mgmt why developers could not fix bugs because they had no access to the bug tracking software.
1 day.... X number of bugs... 0 progress -
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.
-
I was writing in Haskell GHC - and after I got tired of fixing some tuple problem I had no idea about, I typed "fix bugs" and pressed enter....
-
I joined devRant just to rant about a devRant bug. The irony.
If a rant is a bit longer, it will overflow and cause various bugs. Usually, the comment button is basically getting out of sight, especially on rants with many comments.
I already saw this issue multiple times and it's driving me crazy every time.
devRant, please fix your CSS
8 -
This code is so horrible I'm too scared to even fix bugs.
No I did not write this code originally.1 -
I know it's taking me a quite some time to release the AltRant update but I am constantly finding more places to improve loading times and whatnot. The fix list is getting longer as I go...
Also, massive shoutout to @johnmelodyme for helping me with the SwiftRant library and finding those crazy bugs and weird typos and genreal improvements, his contributions are literal goldmine!5 -
When refactoring and reusing code, is it even ethical to change author?
I am on a project of creating reusable library from another project. Original code is perfectly written, easy to understand. I will just prune the code and fix minor bugs.
I have seen colleagues replacing the original author field in the same scenario with their names, feels wrong. Can I add non-standard maintainer field in doxygen format?14 -
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 -
On a past project, every sprint planning was the most unproductive meeting. We were expected to fix all open bugs each sprint, so there was literally nothing to plan. How do you prioritize when the goal is “do everything”? 😂
-
Programming insight #4
Even if code is repeating just twice it's still better to add it in a function/submodule and call the function/submodule twice.
In future, if a bug comes in that section it's quicker to fix it at one place than at two different ones thereby reducing the cases of missing unhandled bugs.
TLDR: The lesser the code is repeated the lesser are future bugs in code2 -
Anyone else's job expect you to fix bugs in your niche app that even the global giants don't give a shit about? Like, have you seen the weird shit that happens with YouTube and Hulu? Our app has neither the staff nor the budget of these big brands, if they haven't fixed it, we probably won't.2
-
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 hate surprises.
I join office after a short leave and the other guy is out with a completely new product I have no clue of. (surprise 1)
Next, he's on leave and now I'm asked to fix bugs.(surprise 2)
Just for the curious, I ended up successfully fixing them and adding 2 features. -
The thing about startups is that you have the opportunity to be involved in a lot of different things. I easily get bored with repetitively doing almost the same thing day in day out.
In my current company, I have been working on the same mobile app for close to two years. It’s the same basic thing, build UI, make API calls, and fix bugs. I am so bored that I’m fit to climb a wall. Anyways, I’ve started applying for backend positions.
But then startups are volatile and things are almost always unorganised.2 -
Me: hey, I noticed we are doing this weird stuff in 'platform A' can we file a story to fix this.
Dev: It must be legacy code or library implementation before my time. By the way it's the same in platform B.
Me: yeah, we will need to fix that too.
Dev: tell you what. For now let's keep our platforms uniform we will fix it when platform B is fixed.
Welcome everyone... to the new chicken egg problem. Where even bugs are needed to be uniform across platforms.1 -
Working for a little SharePoint-Company while studying.
Have to hunt bugs.
Found a major bug which kills one of our customers SharePoint-Site completely because of code pasta.
Told my supervisor about the bug and reported it.
"yeh. we will fix it now"
2h later they started to go live.
"Did you fix the bug?"
"No. Wanted to have the system live asap."
On my way home I got a call.
"We need you back here in the office"
"Why?"
"It crashed. Is not reachable anymore. Help fixing it"
fuck off
-
Well, I'm not saying I just spent a couple of hours trying to fix bugs in a basic ML tutorial, but...
I hate matrix arithmetic. -
Happy New year to all my fellow devs. I hope that this year brings you easy to fix bugs and no harsh deadlines
-
When all the employees in a company will be waiting for the time to go home, Developers are the only one, will be sitting and thinking when i can finish this feature(or fix these bugs) and go home.3
-
When my boss wants me to fix bugs on a very old project because they want to bring it back into production since "there was a project that already did what you propose".
-
I'm starting to grow fucking tired to fix bugs. I know this is a part of the development process, but shit, I've been doing this for two whole months now
-
My head of products idea of an urgent bug is a feature that he really wants in the app.
Guess who’s got 22 ‘bugs’ to fix by Friday 🙁2 -
Get out of class exhausted af, go to work for what feels like eternity to fix small CSS bugs, leave tired af from boredom, go home and *try* to be productive and learn more tech so I can may be not do CSS my entire life, pass out, drank, wake up exhausted af and repeat2
-
I guess i have to be thankful for not knowing whomever wrote this fucking piece of shit of a PHP app that i have to fix stupid bugs in a daily basis.
Cause if i did know the bastard.. i'm pretty sure i would fucking bash his useless head in with anything i had in my hands at the moment... FUCK!.
The level of ignorance and stupidity.. i can't even begin to comprehend.
The worst is that we can't even rewrite this fucking piece of buggy shit cause the bosses are so fucking proud of their deformed creation and wont pay us decently to even to that in the first place.2 -
I created two projects and they are now under testing. Now i am working on two other projects (& more to come). I'd be working on something but i get a lot of emails to do some changes or fix some bugs.
I feel i'm slow but it's only me working on those 4 projects, i can't stop something and work on something else!!
Should i work more at home? Or is it not my fault?
Nobody complained on my work, i'm giving good results although i feel i am losing control, but what if they think i'm a person who can't manage well? any advice???5 -
Not exactly related to the topic but the exact thing is chilling the fuck out .
I always was anxious and was completely paranoid about minor bugs in my application during prod deployments(that is when I didn't know about testing utils and so on) , till the point that I couldn't fix a minor bug in the CSS and I puked 5 times over.
It was rough times but then I got over it and it really helped me alot.
I know bugs are like really not the kind of things you'd want to see in any application but it will arise in every application :3 -
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
-
A piece of my soul dies when I see code like this:
Y = x ? false : true
I was already mad because the file that contained this line was written in a way that makes it really hard to fix any bugs or add feature that were supposed to be already implemented, then the sight of this just made me feel sad10 -
I know using Composition is a good way of reusing components. Works like a charm and sends data down the tree like a waterfall.
But in our codebase it's applied to bugs. Fix one, get two more, fix two get four more.
I want to cry :'(( -
Had to fix some bugs in some really old ASP code today. Need Front Page Server Extensions which doesn't work after XP. Spin up a VM, install XP, IIS, FPSE, then we need Visual Studio 2003 because the project won't migrate. Turns out - installing 'Visual Studio 2003' is a prerequisite for installing 'Prerequisites for Visual Studio 2003'. Cheers Microsoft 😯
-
Apparently I'm to try and fix bugs that are 1-2 years old. Some of which have had work done on them before, so may be in a different state. No reproduction scenarios either.
What the actual fuck? -
demotivated, opened some hacking/programming music on youtube to get me in the mood.
why hacking music? well whatever file you open you have tons of "smart hacks" to fix, as all bugs up to date since I'm here were just fixing brilliant h4xx0r ideas from developers that worked here before.
Maybe I should try to search for unhacking music instead!2 -
It's 3AM and here I am trying to fix the mess that I made last night when I was drunk and the deadline is 12PM (only 9 hours left).. You don't but if you do know how do I kill my boss so that I would look like a bug from a software made by our company killed him to take revenge of killing the bugs?1
-
Okay..
So, what do I have here?
A cross platform mobile app with NO unit tests.
😕
I have to write a big new feature from scratch. (Things can't go wrong, right?)
Started working on it, pointed out problems with the UI/UX designs. The design changed multiple times, still I thought I could finish it by the expected date. And, so I did.
The feature went through testing, and they found bugs. (Surprise...?)
It's already kinda scary to touch someone's code that has no unit tests and no comments. And I think, it's all the more difficult to not introduce bugs.
Also, had to work on the weekend to fix the bugs.
I had some good learnings here, but I'm not sure how I can prevent bugs without unit tests and proper feedback cycle. :/4 -
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 -
How do people feel about including bugs and how'd you fix them in a job app/email? I have a couple companies that are super interesting to me but their public facing sites have a few layout issues (for example, the footer is squished into one column on mobile). I can definitely see how it would come off as arrogant, especially if it's a cold contact.
Thoughts?5 -
Have you ever felt this way?
Taking a tour back in my developer life when I have little experience on my stack I spend days trying to fix bugs and finish tasks.
The funny thing is that I felt I was working much harder and earning less and I felt being used but that's not true because its hard to say that due to my little experience and besides those bugs won't show up if I had much experience, the bugs are very much avoidable and to crown it all an experience developer will fix it in little time, though I won't consider myself super experienced but at least I can say am better than those times and to me I have achieved some level of experience to look back at my misconceptions in the past. -
When you're sitting there coding on your computer, and you suddenly realized that while you were trying to fix the Integer.max number of bugs in your program. You simultaneously developed a second programthat is much better.
-
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