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
-
So, someone submitted a 'bug' to Mozilla.
As some of you may know, in the next year, the new mass surveillance law in the Netherlands is going into effect.
Another fun fact is that the dutch security agencies/government have their own CA (Certificate Authority) for SSL/TLS certificates.
The new law says that the AIVD (dutch NSA/GCHQ equivilant) is allowed to hack into systems through obtained certificates and also that they're allowed to INTERCEPT TRAFFIC THROUGH OBTAINED PRIVATE SSL/TLS KEYS.
So someone actually had the fucking balls to submit a fucking issue to Mozilla saying that the Dutch State certs shouldn't be accepted anymore when the new mass surveillance law gets into place.
This person deservers a fucking medal if you ask me.68 -
I'm happy the announce the official devRant bug/feature suggestion tracker, now on GitHub!
It just went live, and you can find it here: https://github.com/devRant/devRant
Going forward, please use that issue tracker for all bug reports and feature suggestions. We decided to move bugs/features reports to GitHub because we've had a lot of people tell us they'd prefer that method since it makes tracking issues easier, and we also think it will improve searchability and maintainability of current bugs and feature suggestions.
Since we're starting from scratch with it, if there's a bug/feature that you're interested in submitting, and it's not already there, then please go ahead and add it! Even if it's been suggested before in a rant, we want to get them in the GitHub issue tracker, so please add it there too.
Feel free to let me know if you have any questions, and we hope this new method makes it easier to see what bugs we're working on fixing and makes it easier to see and discuss possible new features!46 -
Spends hours implementing a really cool new feature.
Feature gets deployed.
Client flags the new feature as a bug :'(
FML10 -
A friend asked me to test a program he made
So i downloaded it, and i noticed that i crash when you try to minimize the window
After i tell him about the bug, he send me a new version, and said "I fixed it, it was pretty easy"
He just removed the minimize button
"to remove a bug, remove the feature"4 -
Introducing avatar pets & a new way to unlock avatar items! Pets include cats, dogs, birds and tigers. We know getting all those ++'s can take some time, so while all avatar items are just as reachable for free by earning ++'s from rants and comments, we now allow items to be purchased in-app based on the difference in ++'s you have to the ++ unlock value of the item. (To purchase, you'll need the latest app version)
Paying for avatar items helps us keep the devRant servers up and running and also is extra motivation to add more fun avatar items. If you have any questions or find a bug, please let me or @dfox know. Happy ranting!
38 -
1 - Programmer produces code he believes is bug-free.
2 - Product is tested. 20 bugs are found.
3- Programmer fixes 10 of the bugs and explains to the testing department that the other 10 aren’t really bugs.
4 - Testing department finds that five of the fixes didn’t work and discovers 15 new bugs.
5 - Due to marketing pressure and an extremely premature product announcement based on overly-optimistic programming schedule, the product is released.
6 - Users find 137 new bugs.
7 - Newly-assembled programming team fixes almost all of the 137 bugs, but introduce 456 new ones.
8 - Entire testing department gets fired.
9 - Company is bought in a hostile takeover by competitor using profits from their latest release, which had 783 bugs.
10 - New CEO is brought in by board of directors. He raises the programming team's salary to redo the program from scratch.
11 - Programmer produces code he believes is bug-free.
12 - fml9 -
!rant
New job (first CS job).
Day 1: Install Ubuntu
Day 2: Dev said "it was so cute when he asked if he could uninstall windows." Also, first pair programming with engineer of 12 years. First commit (he did all the work, I just tried keeping up."
Day 3: "Here, try this bug " nearly get there. Have to leave early. Team event (Group VR experience, was wicked fun with drinks afterwards. Turns out boss man is a total bad ass. Swam with sharks and giant Wales)
Day 4: Fix bug. Notice odd behaviour. Fix that too. (All on my own). Code review: "This, that but works and is good." Get asked if I want to go to customer to do A, B and C. Tell Boss I only know B. He said "Tell me what you need for A and C."
I'm so God damn happy.8 -
You might know by now that India demonetized old higher value notes and brought in new one. The new ones easily tear off easily and generally feel cheaper and less reliable than pervious ones.
One interesting thing people discovered is that rubbing it with cloth makes the ink transfer to the cloth. Sign of crap printing. Here's government response:
The new currency notes have a security feature called 'intaglio printing'. A genuine currency note can be tested by rubbing it with a cloth; this creates a turbo-electric effect, transferring the ink colour onto the cloth
TL;DR: its not a bug, it's a feature7 -
First rant.
Managing an app in Canada, came back home to Thailand to visit my parents.
No deployments while you're gone, just bug fixes, boss said.
Landed at 3am, "hey I know we only support desktop but we got new customers only on iPad, make it responsive in a day and deploy." Wtf.
Haven't even seen my parents. In Starbucks.15 -
Reasons why I update a software to the latest version:
1% - I'm glad that they fixed the bug
4% - I want the new features
95% - To get rid of reminders that don't allow to tick a "don't remind me later" field.4 -
Dev manager: great news guys. We’ve built a new tool to do automated testing on apps. We’ve gotten rid of the old Appium solution we were using and built this new one.
Me: why not just use the inbuilt native stuff? Click to record works really well.
Manager: nah we thought it would be more flexible to build it ourself.
Me: ... ok ... moving on ... how does it work?
Manager: well this new .jar, you download it, pass in a config file, setup up your simulator and appium and the jar will do everything for you.
Me: ... wait you said you hate Appium? Now you’ve built a wrapper around it? And it doesn’t even set everything up, you’ve to do it all by hand?
Manager: oh we had too, would be too much effort to replace it. Don’t worry we can now write all our tests in .yaml config files instead of using Appium.
Me: so we’ve lost the ability of auto-complete and type ahead, everyone has to upskill on a new tool, it offers no new features over what’s available out of the box and we’ll have to deal with new bugs and maintenance and stuff our self ... because we need more flexibility?
Manager: oh don’t worry. The guy who built it is staying here. He’s going to deal with bug fixes and add features. He’s only one guy, but he’s really sharp, it’ll be great for us and the team.
Me: ... ... ...
*audible noise of soul breaking*
Me: ... ok thank you. I’ll look into this new tool3 -
At my old company one of my colleagues introduced async / await into our csharp code. He created interfaces and showed us a great structuring of his code. Sadly a few weeks later he left the company, because of personal reasons and a bug appeared in his written service. Our senior developer took the issue and complained for like 1 week. That you can't find anything, that interfaces are useless, that async / await is slow and sucks and that we should stop trying to bring new structures into the code base and do things the old way. In the end he deleted all the great things that my colleague introduced and wrote bad and smelly code.9
-
#6
My client tells me there's a new bug with to-www-redirects. He yells they don't work properly anymore and tries to blame me. But fact is I know, they are well configured in the Nginx conf and therefore work like a charm.
I told him I fixed it and charged an hour. Motherfucker.
😓🔨 -
Every week is the same. Wake up, new jira ticket. “Build us a pink house”.
*i build a house*
Next day, “URGENT BUG REPORT!!! CRITICAL ISSUE IMPORTANT IMPORTANT IMPORTANT”, click on ticket, “bug report: the house doesn’t have sprinklers”
They didn’t ask for sprinklers. This is not a bug. *i add sprinklers*
Next day, “URGENT BUG REPORT!!! CRITICAL ISSUE IMPORTANT IMPORTANT IMPORTANT ASAP ASAP ASAP”, click on ticket, “bug report: the house is pink.”
HOW IS THAT A BUG TWO DAYS AGO IT WAS LITERALLY A REQUIREMENT
Meanwhile management makes triple my salary6 -
When a system-breaking bug ends up fixing a different bug and actually produces a new feature we didnt intend but actually love
5 -
Everything in application is aligned to right
🤡 Can you alight text in that form to the left
Me: Why? All forms have text aligned to the right.
🤡: It looks better
*Add !important*
A couple weeks later, a new BUG is assigned to me by the 🤡
"This form has text aligned to the left, while all other forms have text aligned to to right"10 -
My day in a nutshell:
Fixed the app.
Broke the app.
Fixed the app.
Broke the app.
Reverted all changes from repo.
Fixed app.
Found new bug.
Ugh....1 -
That moment your javascript has a bug but its a cool one so you decide to leave it and call it a "new feature"
2 -
Our product owner's equivalent of "It's not a bug, it's a feature" seems to be "It's not a new requirement, it's a clarification."
:-/2 -
Walked into the office in the afternoon, everyone was kinda panicking
Asked what was going on, well, the ticket system is not working anymore, can't put in any new tickets.
So I started to look for the issue as well, checked the system and... The last tickets' IDs were at ~32k. Ha. Looked into the source code and, sure enough, they used a data type with an upper limit of... 32k. So when trying to get a new ticket ID it just crashed and burned.
Quickly changed the data type and stopped the office panic in around half an hour.
Memorable not because of how tough the bug was, but because of the impact and the simplicity of the fix3 -
Today @ 4pm:
New dev: I need help with this issue, i've been stuck on it all day.
Me: ok let's look ...... ok, and did you try google this?
New dev: ... no
Me: ... why?
New dev: well this is clearly my issue, why would I google it? I only google for things I don't know
Me: ... ok ... we'll do you know what this bug is then?
New dev: haha ok, fair point, I'll give that a try. Thanks for the tip.
Seriously, should I be worried? I feel worried13 -
Me visiting home for easter:
Me: tries to find some good assets for adventurejam
Me: fixes a bug on the prodserver
Me: redesigns a gui of an app
Me: applies for a bunch of new jobs
Mom: "you are always computer-ing, do something productive"3 -
Project Manager: Hey Gid, we need to start migrating project-A to the new Server.
Me: Okay, I will inform Dev-Q.
Project Manager: Please do and treat as top priority!
Me: Hey Dev-Q, we need to migrate project-A to the new Server and we need to get it done asap.
Dev-Q: But I'm currently working on some critical bug XYZ which PM wants fixed before COB.
Me: I dunno maybe you want to speak with him.
Dev-Q: I was told to...
Project Manager: Yes! we need that done right away.
Dev-Q: What about the critical...
Project Manager: No! treat this as top priority the client just called.
Dev-Q: Okay.
Me: Any update yet?
Dev-Q: Yep but it seems like the database is quite large and the migration may take a while.
Me: Okay take your time.
Dev-Q: {hours later} Pheww done! All files and database migrated successfully.
Project Manager: Good good. So the critical bug XYZ was also completed and migrated to the new server right?
Dev-Q:
5 -
Taking "fixing a bug in your head once you walk away from the machine" to a new level.
Fixed a bug, checked it in. Happy.
Go to a meeting 5 minutes later. 10 minutes into the meeting have the sudden realisation that the bug fix was wrong and while it would fix the issue it would break something else.
Anxiously sit there for 50 more minutes not really paying attention because all I can think about is that sucker being auto deployed to our Dev server.
Managed to fix it and get it committed without anyone noticing but FML.2 -
A small bug is found.
Chad dev:
😎 *Exists*
> Writes a simple ad hoc solution in a few lines
> Self documenting code with constant run time
> No external dependencies needed
> Fixes the bug, easy to test and does not introduce any new issues
That guy nobody likes (AKA. regex simp coder):
🤡 'This can be "simplified" into oNE LiNe'
> Writes a long regex expression that has to line wrap the editor window several times
> Writes an essay in the comments to explain it's apparent brilliance to the peasant reader
> Exponential run time (bwahahah), excessive memory requirements
> Needs to import additional frameworks, requires more testing that will delay release schedule
> Also fixes bug but the software now needs 2x ram to run and is 3x slower
> Really puts the "simp" in simplified, but not the way you would expect26 -
Not really a bug, but once I tried to learn building function ajax per table asynchronously instead of calling all of them at once. Spend like couple of hours of trial of error. It wasn’t needed at the time, but suddenly I need to fetch something separately because of a new feature. Just write a couple and line it’s done
-
The overhead on my JS projects is killing me. Today, I went to implement a simple feature on a project I haven't touched in a few weeks. I wasted 80% of my time on mindless setup crap.
- "Ooh, a simple new feature to implement. Let's get crackin'!"
- update 1st party lib
- ....hmm, better update node modules
- and Typescript typings while I'm at it
- "ugh yeah," revert one node module to outdated version because of that one weird proxy bug
- remove dead tsd references
- fix TS "errors" generated by new typings
- fix bug in 1st party lib
- clean up some files because the linter is nagging me
- pee
- change 6 lines of code <-- the work
- commit!3 -
I bypassed the Windows Store bug (error 0x8024000E) releasing it as a new app (not as an update).
Now you can find it on the Windows Store as "devRant unofficial UWP".
Changelog (v1.2.0.0):
- Stories
- PC & Holographic support
I worked hard to bring the best devRant experience possible to Windows 10, I hope you enjoy it! :)
https://microsoft.com/store/apps/...
13 -
End of second week at a new job. Found what I thought was a bug and wanting to impress I fixed it. The dev reviewing my code had just started a week before me so he also had no idea what was going on. It went live Friday afternoon.
Come back Monday morning and turns out I completely broke everything and nobody could use the site all weekend. I thought I was done for sure. Was shitting myself all day waiting for the call.
TURNS OUT NOBODY EVEN NOTICED4 -
When you don't have new feature to add to the app but need to keep updates.
"General bug fixes and performance improvements."3 -
Finally finished the blog post and (nearly) the last bugs (few remaining, still gotta think about how to solve them) are fixed.
The new blog post is online! I've taken a look at the Telegram messaging app and basically burned it into the ground. (Provided sources as well)
Next to that, a new domain name! As this blog is about online security AND privacy, I decided to change the domain name. The new one:
https://much-security-such-privacy.info/...
Dark theme can be enabled but will only work on one domain, you have to enable it on the other one as well to get a dark theme there. It stores the value in a cookie so it will remain when you reload the page and don't remove the cookies.
The RSS feed generator has a bug right now which makes that the page doesn't get updated, will work on that one tomorrow.
Thanks!
Last but not least, you can email me suggestions and so on at linuxxx@much-security.nl :)34 -
Just watched sam and niko youtube channel’s latest video about a bug/feature in windows when you do this:
1. Create a new folder
2. Put a file or two or more inside it
3. Select all those files
4. Right click and send to compressed (zip)
5. Press ctrl+z
6. That folder and its contents disappears to another dimension
🤯
Here is the video link btw https://youtu.be/YY5zfbDlSMs1 -
I HATE when a request for a change or a new feature comes like a bug feedback, as if it's your fault
"I clicked this, but this behavior that we didn't agree on didn't happen!! Fix it!"
😡4 -
Bugfix I am most proud of?
The ones where I dont just fix a bug, but refactor an old (possibly shitty) feature thanks to new knowledge, making the next person's job easier in the process :)3 -
Was feeling like a boss in new office after fixing a major bug.
Yes, the bug was fixed. Only half of the program doesn't work anymore.1 -
Apple flips the bird to devs again...
So I go to release a new version of my app (critical updates and bug fixes from mgmt) and I had just updated my phone. Yeah, that was a fucking mistake.
“This version of Xcode is not compatible with the new version of iOS.”
Ok... update Xcode...
“The new version of Xcode is not compatible with your version of OSX”
WTF?! This version isn’t that old? Fine... update OSX. 5 hours later...
“Hey, just wanted to let you know that we decided to break every one of your web development tool setting and basically nothing works on your computer now, oh yeah, and we’re Apple so FUCK YOU.”8 -
git commit -m "fixed bug where div wasn't resizing with window size change. Next I'll work on new bug which makes it so the pages won't load at all"
3 -
So, a few years ago I was working at a small state government department. After we has suffered a major development infrastructure outage (another story), I was so outspoken about what a shitty job the infrastructure vendor was doing, the IT Director put me in charge of managing the environment and the vendor, even though I was actually a software architect.
Anyway, a year later, we get a new project manager, and she decides that she needs to bring in a new team of contract developers because she doesn't trust us incumbents.
They develop a new application, but won't use our test team, insisting that their "BA" can do the testing themselves.
Finally it goes into production.
And crashes on Day 1. And keeps crashing.
Its the infrastructure goes out the cry from her office, do something about it!
I check the logs, can find nothing wrong, just this application keeps crashing.
I and another dev ask for the source code so that we can see if we can help find their bug, but we are told in no uncertain terms that there is no bug, they don't need any help, and we must focus on fixing the hardware issue.
After a couple of days of this, she called a meeting, all the PMs, the whole of the other project team, and me and my mate. And she starts laying into us about how we are letting them all down.
We insist that they have a bug, they insist that they can't have a bug because "it's been tested".
This ends up in a shouting match when my mate lost his cool with her.
So, we went back to our desks, got the exe and the pdb files (yes, they had published debug info to production), and reverse engineered it back to C# source, and then started looking through it.
Around midnight, we spotted the bug.
We took it to them the next morning, and it was like "Oh". When we asked how they could have tested it, they said, ah, well, we didn't actually test that function as we didn't think it would be used much....
What happened after that?
Not a happy ending. Six months later the IT Director retires and she gets shoed in as the new IT Director and then starts a bullying campaign against the two of us until we quit.5 -
Interesting bug hunt!
Got called in because a co-team had a strange bug and couldn't make sense of it. After a compiler update, things had stopped working.
They had already hunted down the bug to something equivalent to the screenshot and put a breakpoint on the if-statement. The memory window showed the memory content, and it was indeed 42. However, the debugger would still jump over do_stuff(), both in single step and when setting a breakpoint on the function call. Very unusual, but the rest worked.
Looking closer, I noticed that the pointer's content was an odd number, but was supposed to be of type uint32_t *. So I dug out the controller's manual and looked up the instruction set what it would do with a 32 bit load from an unaligned address: the most braindead thing possible, it would just ignore the lowest two address bits. So the actual load happened from a different address, that's why the comparison failed.
I think the debugger fetched the memory content bytewise because that would work for any kind of data structure with only one code path, that's how it bypassed the alignment issue. Nice pitfall!
Investigating further why the pointer was off, it turned out that it pointed into an underlying array of type char. The offset into the array was correctly divisible by 4, but the beginning had no alignment, and a char array doesn't need one. I checked the mapfiles and indeed, the old compiler had put the array to a 4 byte boundary and the new one didn't.
Sure enough, after giving the array a 4 byte alignment directive, the code worked as intended.
8 -
When you work for hours to solve a bug, and finally you fixed it, only to have 2 new ones show up to replace it:
3 -
My new favourite response to a bug ticket:
"But do you not remember we tested the implementation and it worked?"
... yes ... then it broke under other circumstances.
... must be terrorists or something2 -
"Most coders think debugging software is about fixing a mistake, but that's bullshit. Debugging's actually all about finding the bug, about understanding why the bug was there to begin with, about knowing that its existence was no accident. It came to you to deliver a message, like an unconscious bubble floating to the surface, popping with a revelation you've secretly known all along. A bug is never just a mistake. It represents something bigger. An error of thinking. That makes you who you are. When a bug finally makes itself known, it can be exhilarating, like you just unlocked something. Because, after all, a bug's only purpose, it's only reason for existence is to be a mistake that needs fixing, to help you right a wrong. And what feels better than that? The bug forces the software to adapt, evolve into something new because of it. Work around it or work through it. No matter what, it changes. It becomes something new. The next version. The inevitable upgrade." - Elliot, Mr. Robot6
-
Today it was decided that we would hide a bug by making a new feature that only hides the bug
I don't like it, but it needs to be done for actual reasons5 -
One of our customers calls everytime when he thinks he found a new bug. Then he literally yells "I found a new bow" since he thinks "bug" is a german word, so emphasizes it like that. In german "bug" means "bow of a ship".1
-
Devs: We fixed a bug, so watch out for some changes.
Management: The new values are too bad, you need to change it back.
Devs: But ... it was a bug?
Management: Rollback ... now!
I swear, the moment shareholders are involved, management is just about who has the best lie.1 -
Do you ever have those weeks where you have to fix a bug, then uncover another bug then another then another. Then you realise some functionality is completely missing. You write tests to cover your bug fixes and new functionality. Then you realise tests are broken with your fixes and you have no idea why. Then you get so frustrated you start making silly mistakes. Then your debugger starts playing up.... Yeah that's been my week.5
-
soo.. yeah.. I've just solved an annoying bug using only chatgpt.
My first commit in this new project. And it's based on chatgpt.
Literally just saved me from days of reading through kafka docs, auth mechanisms and other stuff. And no, the google did not provide me with a proper answer/hints. The only hint was "the configuration might be wrong". Well alright, but I was NOT using any configuration in the first place...
Fun times ahead :) I might even consider the pro version if it keeps delivering like that.16 -
i kinda feel embarrassed all the time. i feel like it's never enough, i don't know enough, there's so much i don't know. i do enjoy my work and sometimes there are moments where i'm proud of what i've done, or these "i'm a fucking genious" moments when i solve a bug or a certain problem or when something finally works. but if i have to do something new, i tend to panic a bit, as long as i do not yet have a concrete solution in mind.
my perception contrasts with the feedback people give me, but even when i'm happy about the positive feedback, i tend to think to myself, "they're wrong, it's not that great"..4 -
Tldr; my "this is not bug, its a feature" moment actually turned my bug into a feature.
Today we were presenting a project which has imposible deadline. I am developing this small project alone (which is probably good). I implemented core features first but I know project still have bugs and a lot of tech debts. Another friend started to presenting our demo and a wild bug appeared as expected. He was adding rows to a table. To add a new you gotta open new modal by clicking + button and fill the form. One of the fields had a bug. When you add row by clicking Ok button, the value of the field stayed there after you open modal again. So its basically a state problem in React. I forgot to clear previous state of modal. When they see that and my friend said "oh we got a bug there". Then I enabled my mic and said "thats not a bug, thats a feature. I didn't want to enter that field again and again when I adding multiple rows and made it persistent." and you know what? They liked the idea! They requested to add that bug to two more fields. I was just joking and my "this is not bug, its a feature" moment actually turned my bug into a feature. Instead of fixing it, I'm creating more of this bug. LOL!5 -
I've been hunting for a new job for several months because my current company isn't growing my skills any further. There have been many setbacks, a few rejections, and that awful lingering imposter syndrome. So I finally dug myself out of my self pity and began learning things that my current company doesn't implement – JS frameworks, UX practices, etc. Today I had an interview that felt more like a conversation and collaboration than getting grilled about terminology and bug fixes. No matter what the result, I've been inspired to learn again 😌13
-
I been seeing spam on devrant lately. It is usually a new account which only have 1 rant (a spam)
Maybe devrant should include some kind of "Are you a developer captcha" which make you fix a bug before creating an account.17 -
When you think you've either found a bug in Python, or you're going insane, so just to double check, you make two mutually exclusive assertions that could never both be true, and yet, your tests still pass.
I think it's time to find a new job.
9 -
Our new hired (promoted intern) just installed Ubuntu on his new machine.
Now we are the only ones using Linux at work.
He was having trouble with a flickering bug on kernel 4.4.0 and I just told him to apt upgrade that it would solve it..
And he was like: oh.. Can you update the kernel?
That's gonna be a long month...hope he learns this faster than git7 -
Two of them, both are not very extrem.
Positive one first:
Meetings were usually not dead serious (unless there was a problem), everyone just joked around a little, made their actual points and got back to work.
Now the other one:
A client's QA staff commented "this bug is still occuring" on 5 tickets, without checking if they ever deployed the new release candidate.
They didn't deploy the new RC, so of course, the bugs couldn't have been fixed on their side.2 -
My most satisfying bug fix?
I found a core concurrency issue in this gnarly homegrown ORM and reported it to the lead devs, who (very defensively, having written the damn thing) argued that it would never pop up in a prod environment and I was stupid for even bringing it up. Theoretically, this bug could cause pretty much every foreign key to be assigned to the wrong parent, but only if multiple instances of the application were open/running at once. They were so certain it would never happen on live that they explicitly instructed me not to fix it. After all, this bug had been active for many years on a previous project and nobody complained.
Problem was, that previous project was something that only a single user had open most of the time (think: a manager). The new project was something that would be used by multiple people at the same time (think: all the employees). Once we released this new-project-with-old-orm, it didn't take long at all for our customers to start complaining.
After that, they let me fix the bug. :) -
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 -
There. I fixed the bug. Tested every way possible 10 times and it won’t break. I’m awesome.
Tells a tester I have a phone with the new app-version installed for testing on my desk when he has time.
He just... came to my room. I gave him the phone. He looks at it, does SOMETHING and just ”Ya man, I broke it”.... whaaaat O.o2 -
I hate when a software update changelog looks like this:
The latest update is now available, update your software to get the most out of it.
I want a fucking changelog before updating my things. Like: fixed a bug, new button with cool new feature. Just something. I have to know. Can't just install something blindly that could ruin my software, especially when it's not reversible..1 -
You know what really grinds my gears? When new employees start shouting out suggestions of what feature we should do.. and how stupid this/that thing now.. or how slow that page is.. or how there's a bug somewhere.
WHAT WOULD'VE WE DONE WITHOUT YOUR OPINION?! thank you so much!!!
+10 points if their job has nothing to do with product or development
SHUT. THE. FUCK. UP
please!!!15 -
Teaching new devs, hired straight from India.
This is today.
Bug1: We have four lists, each item in these lists has a variable called "Charge". This var is a double and we need to convert it to currency.
Dev creates fifth list called "All lists" and converted it's charge to currency then questioned why it didn't work.
I explained, his solution? Convert each list into currency.
I explained that's wrong and told him what he needed to do. He did List1:Charge into currency, but left his other conversion in place just in case.
I walked him through fixing it which took 10 times as long as necessary, only to find out he randomly converted four booleans into currency for no reason.
Bug2: we take integer, convert to string and concat "Months" on the end.
Doesn't work for him, tells me he doesn't know why.
I told him that he's not outputting the variable that we did it to, he is instead outputting a custom variable he made and didn't do anything to.
Bug 3: followup to #2, he fixed it as I instructed, but then added months as static text to the output so now it reads "Months months".
Bug 4: to make his code cleaner, he presses enter in the text box. Unfortunately he did that IN A STRING so his output is full of random /r/n
How do you guys deal with coworkers like this? He isn't new, this is supposed to be an experienced developer. Im only in my 2nd year23 -
I’m so fucking sick and tired of !devs telling me how simple a feature should be to implement.
Like motherfucker the most complicated thing you’ve ever done with a computer is attempt (and fail) at working with tables in Microsoft Word and you’re trying to tell me how long a new feature/K8s architecture/noSQL aggregation should take to implement?
A monitor cable wiggling loose paralyses you for hours but I’m supposed to bow down to your understanding of what is causing a bug?6 -
Normal person : 365 + 1 = 366
Developer dealing with julian dates : 365 + 1 = 1(New year)
Business person : 365 + 1 = 001 (because they like symmetry in their file names with dates)
We found this BUG, now we are celebrating our new year by changing code in each of script to format string accordingly.
2 -
The new version of the (unofficial) client (now UWP and with "Stories") for Windows 10 is here... but I can't release it due to a Microsoft Store bug... 😢
Hope to see a Microsoft fix soon, because I can't wait to share it with you! 😝
4 -
See another of this git commit message :
"Fixed bugs and added new feature"
Fixed what bug?! Added new feature what?!4 -
How the fuck does someone releases a new version of a package without testing one of the core features of that package?
Spent fucking hours, hitting my head on the wall, only to realize that the latest build they have released has a bug. This is not acceptable :@2 -
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 -
There was a bug in "Change email" module. When the functionality is called, it sends 2 emails:
1. to a current email w/ a link to 'reject email change'
2. to a new email w/ a link to 'confirm email change'
The flaw was in how these links worked (the clockwork behind them). If one link is clicked, another one is NOT deactivated in the bkend :)
Now the task for you is to figure out why this is wrong :)4 -
Client writes a bug report: This and that doesn't work.
Me: This functionality never was implemented. Please open a feature request.
Client: But this is a bug. Without this feature, the service won't work as we expect.
Me: But this wasn't in the requirements for release. So you have to contact the PM for a feature request.
Client: THIS IS A BUG! FIX IT!
Me: GO FUCK YOURSELF! THIS IS A NEW FEATURE AND YOU HAVE TO PAY FOR IT!
Unfortunately, I never sent the mail. But I kept it in the drafts. Maybe someday...1 -
Made an Android app a while ago. I needed some pet project so I decided to go with Java for Android. First time, no experience at all.
So everything went ok, I had a little help from a colleague, structuring code, and pushing to the store. Work done app was doing ok.
A year later I came back to this project. I needed to fix a bug - date time and daylight savings crap. 😥
Spent a week on it. Ready to push a new version to the store, with some extra features! Build apk. All good.
Wait. I need to sign the APK? Wtf. I had to format my hard drive. How do I recover my fucking certificate?
*Google's for a while*
No fucking way. I can't restore the certificate. Or get the keystore back. The solution is to create a new app with a brand new package name?
Thanks for nothing, I'm done with Android development.9 -
Discovered pro tip of my life :
Never trust your code
Achievements unlocked :
Successfully running C++ GPU accelerated offscreen rendering engine with texture loading code having faulty validation bug over a year on production for more than 1.5M daily Android active users without any issues.
History : Recently I was writing a new rendering engineering that uses our GPU pipeline engine.. and our prototype android app benchmark test always fails with black rendering frame detection assertion.
Practice:
Spend more than a month to debug a GPU pipeline system based on directed acyclic graph based rendering algorithm.
New abilities added :
Able to debug OpenGL ES code on Android using print statement placed in source code using binary search.
But why?
I was aware of the issue over a month and just ignored it thinking it's a driver bug in my android device.. but when the api was used by one of Android dev, he reported the same issue. In the same day at night 2:59AM ....
Satan came to me and told me that " ok listen man, here is what I am gonna do with you today, your new code will be going production in a week, and the renderer will give you just one black frame after random time, and after today 3AM, your code will not show GL Errors if you debug or trace. Buhahahaha ahhaha haahha..... Puffff"
And he was gone..
Thanks satan for not killing me.. I will not trust stable production code anymore enevn though every line is documented and peer reviewed. -
It seems that the bug with the Add-ons on Firefox still remains unsolved (at least with firefox-esr on Debian, the "new" version seems not to have been released yet).
It has been an uncomfortable weekend on the Internet, but not enough to make me break my relation with Mozilla. Each time I miss my extensions, I think of those poor devs drinking coffee and fixing bugs during the weekend, instead of relaxing and do other things.
Why do I see so many annoyed people writing bad comments on Mozilla's blog? I mean, Firefox is open source, maybe we should be a little more patient and empathic with them :)
(source of the image: http://www.foxkeh.com/)
8 -
Fucking facebook researcher that make underfitted neural nets and fuck Mark that it's a marketing genius, the only idiot that can make news from a failure. The CEO of Tesla knows it and said Mark is not an AI expert. Bug not feature, it's only a poorly trained and poorly designed neural network having a bad representation of concepts, not a new language and not the fucking apocalypse. Google faced and solved the same issue when start ed using neural nets for zero-shot translations without using english as a translation bridge.
-
Backend Dev: Sir, I think we have a problem with our code. The function does have a lot of bugs in production that we can't maintain it.
Manager: Okay Front-end. You get a new Ticket. Prevent this bug by today
Front-end: Dafuck
Sometimes, I feel sorry for my colleague.1 -
That moment when code reuse makes you reuse reused code and you actually reuse a BUG.
You decide to go for code reusing when your boss asks: "Can you add an edit popup besides that 'add customer' popup button?". You do some little tweaks to the "new customer" code and it allows that to save over an existing entry, cool.
However, after a lot of time spent on reviewing the resulting PR, turns out there was a dormant bug on the code you reused, and it woke up with its new use.
That code was a bad copy-pasta from another, bigger form, which included a whole bunch of optional fields. As it was only used to save new entries, those now missing fields were simply being saved as empty. But as you reused that to save existing entries, you were now cleaning up all those optional fields without noticing.1 -
I changed "Bug" in TFS to "Monstrous Hideous Defect". That'll get the mindset right. The word bug is so common that nobody cares anymore. New Monstrous Hideous Defect? Holy crap, better fix that right away! 😃
-
Nothing interesting. Just 11 GB ram using and increases steadily. After restart app the bug was again. Okaaay, I thought. I reboot my PC, but bug was adamant. Well, then I update phpStorm and everything became fine. Ok, JetBrains, good idea to say user about new release version and make update:) Seriously, it works fine. I think every company should adopt this idea:)
8 -
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
-
Apple paid bounty hunter 18k instead of 250k by silently tweaking their help page, so it seems like the bug is less severe.
Dear apple, I defended you from baseless and opinionated attacks just like I defend every company that is bashed for no reason, but this is some straight up bouba shit. I will still be fair when it comes to your products, still never silencing bugs and downsides and praising what deserves to be praised, but I will always mention this incident when someone asks me about _working_ at apple. That kind of ethics bs can't be silenced just because I enjoy your new arm chip.
https://thezerohack.com/apple-vulne...12 -
I know I'm writing the correct integration tests when each one I add uncovers a new bug.
Still, it would be nice if just one of them passed first time.1 -
Beware of scope creep. If it's a bug, fix it for free. If it's a new feature or changed from the original signed off scope, charge for it.1
-
Why do I feel like developers at Zoom don't have a life: They release a list of over hundreds of new updates and bug fixes almost everyday. As much as I give them credits I also still feel sorry for them.
4 -
PM : Develop this new feature. Client needs it tomorrow. And be sure it works perfectly well.
Dev : haha how can it work without bug if it's developed in a day ?
Poor dev got transferred to support department :(
4 -
that feeling when you start looking at code after dinner, correct a bug or two, start implementing new features, tweak the code a little bit, you are really focus in your coding... then look out the window and realize the sun is about to come up. it's great 🤓
-
Story time.
I worked on a project recently where the HTML was written just _perfectly_. Div elements were exactly indented as the blocks on the browser window.
CSS classes were self explanatory and altering them didn't introduce any new kind of bug on the browser window.
Introducing a new div block with CSS classes fit perfectly in the window along with responsiveness on different screens.
JS was also written in a self explanatory way.
It was such an Italian Chef's kiss grade of work that I just sat back and admired the glorious work for 10 mins. Totally deserved it.8 -
Im getting annoyed by the new layout of google. Hovering the sidebar will make a scrollbar appear but the main part of the site's scrollbar will disapear. This results in most content moving from their original place. Let's make a Stlyish script to fix this problem I thought. Guess what now somethings stay where they should be, but the things that were first on the right place have moved. Also this will make the header shorter. I'm getting more and more amazed how shitty some frontend devs are at google.
To fix one bug they, instead of solving the bug, tried to counter the result of the bug.
I do like the z-index of the sidemenu though (it's 2005, the year youtube was created)12 -
Just before the holidays started I was given a task by my manager, $M.
$M: "Kyntak, while I'm away I want you to look into this new way of starting $important_service"
$me: "Okay $M, is there a bug for this that explains what is needed?"
$M: "Yes, you should be able to find it"
Goes looking, finds someone else working on something connected but not the same, finds the code change that makes this available... It doesn't explain how to use it, when the async events fire or (well, to a junior engineer like me) really anything.
Message the other (very experienced) eng.
$me: "Hey I've been asked to make $important_service use the new starting API, can you tell me about?"
$eng: "Yup, here's a bug for that and I'm happy to answer any questions you have" *goes offline*
I read the bug. It doesn't mention the original problem I was trying to solve, it doesn't even mention $important_service. There's no design doc mentioned. The bug has a higher priority assigned than any of my other work. It has an expected completion date only days after I get back from holidays (which $M told me to take).
I try to contact $M and $eng. They've already left for holidays.
"Hmm"
Implements as much of the fairly inevitable boilerplate that I can infer from the bugs and surrounding code.
"Hmm"
So, I'm into my second week of holiday and am starting to think about the potential shit storm I may return to.
I hope the bug's priority was wrong.4 -
Is it just me or devrant has a bug of showing false notification badge?
It's stuck on this number even though I don't have any new notifications
5 -
The moment, when you're coding a new feature on friday, your code somehow behaves weird in firefox... dev console shows unexpected behaviour and you're starting to think YOU ARE GOING CRAZY...
And then.. you find a fricking fucking Bug from over 12 YEARS AGO which STATUS IS "NEW"!
"Yes, the problem still persist with 2.0.0.11"
"This is indeed still an issue in version 3.6.3"
"Yes, it still exists in FF 4."
"Bug still present in Firefox 8."
"This ticket is almost 10 years old. Switch to Chrome."
CONGRATS FUCKING MOZILLA! THANK YOU! <3 <3
https://bugzilla.mozilla.org/show_b...2 -
Google, will you ever manage to fix YouTube so it actually doesn't fucking break every day?
This "feature" where the page doesn't reload when I click reload is neat until I want to, you know, reload to see new content. Or reload because you failed to load a single video thumbnail. But no, you managed to combine the shit of both worlds and give me a loading progress bar and then don't change anything.
Also YouTube is the prime example why you don't try to reinvent text input fields. I can't remember a single instance in the last 5 years where the comment fields didn't have at least one weird bug.
Why do tech companies build the shittiest websites?10 -
Just...Macbooks
(sigh)
The entire day wasted having to install a new OS to install a new Xcode to export an app, only to find the xcode was installed under a different user (who has long since gone from the company) to then have to look up what to do, to then just sit...........and....................wait.............for Xcode to download again.
And I know when I try to export my app (which had zero problems being exported to Android) I'm going to hit an entire day tomorrow of bug fixing for ios sh...stuff16 -
I've been working for the last 5 years on some large legacy code used in production, more than 100K LOC, poor comments (when existing) often outdated, huge parts of code that can no longer be reached, over-engineered class hierarchy, functions of thousands lines, huge parts of deprecated code that cannot be removed because "someone might still be using it". Statistically, every small change caused 3 new issues somewhere else and every bug fix or new feature required 10 times the time that would be necessary with a decent codebase. But after five years in hell I can finally say that... Oh wait, nothing changed, the code is still legacy and nobody is going to do anything about that.1
-
When someone creates a new bug and leaves without fixing it.
And the next day you can see everyone around his desk with unfriendly faces waiting for a fix. -
As much fun it is to code and create new features for users. Take a break from the computer and spend time with real people.
A few years ago I would stay at work to get tasks done. While everyone in the office would go home I would stay and finish some task. After doing that for a few months my wife started to yell at me.
It made me realize that no matter how important a new feature, a bug or optimizing code is family and the relationships you have are more important.4 -
You know what really grinds my gears more than anything else? Not having anything to work on at work.
That might sound like the most german thing to say but bear with me for a second.
Even though i am almost one year into my job as a junior dev, i consider myself and i probably am very new to the coding world. And even if i weren't new i would still have to continuously learn and improve. And every time i just sit in front of my working station, with nothing to do, i'd rather figure out an incredibly tedious bug, learn lisp or deal with a shitty framework.
Most of the time i don't know what to do. I improve my workflow with some bash-scripts and aliases, i read into the details of certain tools but at the end of it, i can't really get into something deeper and get value out of it because actual work might just be around the corner...3 -
@dfox in case you havent already discovered it i have found a bug with notifications in the iOS app.
Steps to reproduce:
1. open notifications
2. tap one of them as many times as you can really fast
3. It generates a new view controller for every time you tapped it.
obviously having to tap furiously is a bit obnoxious but i originally noticed it when the app was running slow and i tapped the notification a second time. It created 2 new view controllers instead of one so i had to actually go back twice to get back to the notifications screen.6 -
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 -
I'm getting to the point where every time I encounter a new bug to fix I die a little inside. So tired of stuff not working and as soon as I get one thing fixed another blows up. Unresolved problems and open loops keep me awake all night. I sometimes want to switch careers but what else is there for me after more than 2 decades of this? I guess I could flip burgers and mow lawns. The burger flippers make about what I made in my last job and the guy who mows my lawn makes twice that much.4
-
My project had a pretty decent state until I decided to add more features. New features had new requirements which in turn added more code along with a bug which nearly destroyed my will to live.
Went into 'fuck it' mode and reverted aaallll the way back to the decent state. Now I don't feel like sticking firecrackers to my laptop and lighting them up. 😌 -
Fun fact : Typing on a keyboard that's not plugged into your laptop will not work. Honestly, I should have taken today off. My toddler woke up at 1am screaming bloody murder and didn't get back to bed until 2:30. There's a construction crew hammering up my 14 year old floors to replace it with new ones. My dog is anxious as fuck with all the noise, and truthfully, I'm just staring into my screen hoping the code will write itself. This code will become production deployment logic, so it damn well better be excellent and bug-free. Not a good day to pick up this task.3
-
I was working on a new feature for this legacy project.. Just minding my own buisness then all out of the blue I got an email from our client (before the email I exported the live database because I needed to reproduce a weird bug) saying the sync stopped working
<backstory>
The database needs to sync every 15 minutes because it has a master-master relationship with a 3rd party database..
</backstory>
So I was like shiiit! Did I do that!? So I checked the logs, nothing... I called the 3rd part to check if they have problems, nothing.. Then I checked the network logs... Again all fine... 30 nervous minutes later, I got a new mail... Saying it finally synced... Still have no clue what happened or if it ever was a problem... God damn clients man... -
I'm fucking tired of putting my efforts into bug fixes.
5 years of web. I never had a client that likes to keep it's crappy slow piece of shit product on the market in the exact same way it is.
If they didn't sell it to state employees (and good luck for them if they do not use it) their product would be dead.
That's the only way they get money: bids. And the minimum a state pays is 15 MILLION.
And they don't have 90K to pay another dev to help creating a new product.
Their CEO fucking REJECTS anything that's not a bug fix. Once he said to our PM:
"It's pretty and more fast, but wasn't this way that made me rich"
I'm thinking I'm getting another client, seriously. Everyday the same thing breaks and they already know the fucking answer:
WE NEED TO FUCKING REFACT
CREATE A NEW FUCKING PROJECT
This shit is making crazy. I can't sleep. I can't eat and I'm always fucking tired, no matter what I do.
I need to stop working for Brazilians.
I'll try US, Canada or somewhere in Europe.8 -
!rant
Neighbours asked me to help them setting up their new printer.
Bug: Installation of the driver fails.
Fix: The printer has to be turned on during installation.
I earned 20 bucks for this single press of only one button.
First-Level-Support in the neighbourhood: Annoying but pays like hell.3 -
I am bored !!! No feature request and No bug was reported from last 2 days... Nothing to resolve today.. I am thinking should I create new bug and release it as feature??5
-
qa: so yesterday we found some bug, not really related to you but <boss> told me to put it on you
me: yeah, when he doesn't, this dick didn't work since I came
*later this day at ~15:00*
boss: so I'm going home, you **must** deal with this bug today, your algo doesn't work.
me: it did 2 days ago didn't it? did you even check the bug?
boss: yeah
me: did you check for regression or just said to put it on me?
boss: nope
me: did you check the changes of the new guy?
boss: nope
me : so why the fuck blame my code?!
*17:10 I'm going home no regression, new guys code deadlocks, not a single fuck thrown* -
Why do clients wait for 17:55 before asking you to fix that nuclear reaction bug or that new "little insignificant feature i can't live without" ? Seriously, what the hell is your daily job ? Because i really want to switch to it.3
-
I finally made my first production-level bugfix at my new job! 😄 After weeks of training and then being assigned a live bug, I resolved it quickly & elegantly, which helps prove my worth to the team.
Man, it's so gratifying to be making contributions that are going to affect real devices that actual people are using. It seems being a dev with a sense of purpose is nearly as important as enjoying what you do. ☺️ -
Holly crap..... Just fixed a 7 months old bug in a system i worked on and had to leave it for 7 months coz i just wasn't seeing what i did wrong and today..... everything simply unraveled
It's a flask app and i got stuck on updating a column in the database and also it created duplicate configs on one of the configuration functionality
Figured out what was causing duplicates
A different function was creating new configs instead of updating...bypassing duplicate checking in the config function2 -
I hate legacy code.
Introduced some new changes to our application and voila! A bug in the legacy system surfaces. It was just hiding in there, waiting to ruin my weekend.2 -
!rant
Does anyone else derive great pleasure from creating quality of life/small utility programs?
So I'm learning python in between projects at work (plan on slowly moving new projects to it) and damn, my coding buddy and I have found a package/import for almost anything we can imagine. Heck, we canned ourselves laughing when we started googling random things and still found python packages that do it. I plan to use the language to automate a ton of things when I get a new PC.
Aside from that, I recently in 2 days (1 day building, 1 day bug fixing) made a tiny utility that shaves a good 5 minutes off a certain task for my colleagues at work, and in bulk use will save even more time. It's a textbox and a button only but it felt so nice to make something useful like that so quickly.5 -
Trying to learn C and thought a easy file copy was a good start. The program read the size of the file, reserved that size in memory, can copied data there and then to the new file. For some reason I never thought that the file might be bigger then available memory... Took a couple of BSOD to find that "bug".3
-
boss said: "we need create new version of our software. copypaste old version in new branch. so we will have dozens of versions and all of them online and working."
my question: "what if old bug will appear in all off 100500 branches? we will need fix all the versions of bug in different copies we have modified!"
boss said:"c'mon when we will get this problem then we will think about it. all the devs in world working on many versions. its easy."
your opinion?2 -
Going through the conversation for xxxxth time with my business partner, why we will not launch a new product on top of pre-made PHP script / plugin.
Just got our company into TDD, and automated QA via CI server & code checks etc, PLEASE stop trying to drag us back into the land of spaghetti code & bug legions in production. That's all thxbye. -
That moment when agile means "I will sneak in new feature requirements in with your bug tickets even though our sprint is supposed to be only stabilization". Thanks PM Lord.
-
Wouldn't call it a software bug but related:
Was developing an order system to expand in the UK. We have been developing it for the last 2 years and always had a one nasty bug in the system... Whatever we do, it still appears... Tried debugging to find the source, tried covering with tests - nothing helped it was still there. We even rewrote the whole system 3 times and it still was there!
One day, we have been given a stupid request from our manager - take a black background and make it even more blacker... That was it and I went to the CEO with letter where I stated that we should remove the manager... As I'm the Senior there, he did ask me why and eventually removed the manager...
Oh my guys, I've never felt so good after removing a bug! Since then - our application went live, we had our first customers and we were happily rolling new updates. And the best part - there was no BUG! Everything we did just had undocumented features or missing links but we haven't really had a single bug that was not caught by our automated tests!
---
Moral of the story:
Not only software can have bugs. People also can be "bugs" while bugging you about every single details they think is not working correctly. -
We should all share our first reported bug for 2018
Let's start this tag :) "2k18 bug is"
Happy new year everyone !!3 -
This Safari Bug is sooo bad, really hard to find it. (It initializes new variables with the element where id and variable name is the same, why?)
10 -
Well... I can think of several bugs that I found on a previous project, but one of the worst (if not the worst, because the damage scope) it's one bug that only appears for a couple of days at the end of every month.
What happens is the following: this bug occurs in a submodule designed (heh) to control the monthly production according the client requirements (client says "I want 1000 thoot picks", that submodule calculates the daily production requirements in order to full fill the order).
Ideally, that programming need to be done once a week (for the current month), because the quantities are updated by client on the same schedule, and one of the edge cases is that when the current date is >= 16th of the month, the user can start programming the production of the following month.
So, according to this specific case, there's an unidentified, elusive, and nasty bug that only shows up on the two last days of every month, when it doesn't allow to modify/create anything for the following month. I mean, normally, whenever you try to edit/create new data, the application shows either an estimated of the quantities to produce, or the previous saved data. But on those specific days it doesn't show any information at all, disregarding of there's something saved or not.
The worst thing is that such process involves both a very overcomplicated stored procedure, and an overcomplicated functionality on the client side (did I mentioned that it dynamically generates a pseudo-spreadsheet with the procedure dataset? Cell by cell), that absolutely no one really fully understands, and the dude that made those artifacts is no longer available (and by now, I'm not so sure that he even remember what he done there).
One of the worst thing is that at this point, it's easier to handle with that error rather to redesign all of that (not because technical limitations, but for bureaucratic and management issues).
The another worst thing (the most important none) is that this specific bug can create a HUGE mess as it prevents the programming of the production to be done the next day (you know, people tends to procrastinate and start doing things at the very end of the day/week/month)... And considering that the company could lose a huge amount of money by every minute without production, you can guess the damage scope of this single bug.
Anyway, this bug has existed since, I don't know, 2015 (Q4?) and we have tried so many things trying to solve it, but that spaghettis refuse to be understood (specially the stored procedure, as it has dynamically generated queries). During my tenure (that ended last year) I spent a good amount of time (considering what I mentioned on the last rant, about the toxic environment) trying to solve that, just giving up after the first couple of weeks.
Anyway... I'm guessing that this particular bug will survive another 4-ish years, or even outlive the current full development team... But, who knows ¯\_(ツ)_/¯ ? -
Hi everyone I'm new there =)
Basically i'm just here for the stickers.
But this look like a really fun place to be as a dev, so i'm maybe going to stay a while ;)
anyway have a great day, you can resolve this bug !5 -
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. -
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 -
Get a ticket for a low priority bug, reported internally. Fix the issue mentioned in the bug.
Moves to QA environment, the original bug reporter tests and *passes* the ticket.
Moves to Staging environment, same exact individual then *fails* the testing. Cites totally new/unrelated changes that need to be made.
Apparently our the workflow is -
Code->QA->Staging->Requirements
Makes sense! :)1 -
Bug report:
iOS 10 (latest) + iPhone 6
Can't scroll past initially loaded rants on algo screen
Also, love the new tag picker...14 -
Demo for client goes bad when we encounter a bug adding a new entry into the back end. Entry shows up in the admin but not the front side.
<thoughtbubble> "I can't believe this, we just tested it! How can this be? How? How?" </thoughtbubble>
Perhaps, the cache? Nope.
<thoughtbubble> "You gotta be fucking kidding me!" </thoughtbubble>
Perhaps the front side is pointing to dev? Nope.
<thoughtbubble> "Oh shit... make something up quick. Make it sound good." </thoughtbubble>
Tells client we'll have to look into it. (real smooth)
Looked into it and it turns out the bug was actually a feature. Apparently when you assign an "end date" to a date in the past... by design, it won't show.
However, was it bad UI? That's a different argument.4 -
So we have this really annoying bug in our system that customers keep complaining about. I've explained in detail, multiple times, why the part they think is a bug is not a bug and the workaround they keep asking me to apply doesn't make sense, won't fix the issue, and won't even stick (the system will notice that the record they want me to delete has been removed and it will repopulate itself, by design).
I've told them what we need to do as an actual workaround (change a field on the record) and what we need to do to properly fix the bug (change the default value on the record and give proper controls to change this value through the UI). We've had this conversation at least three times now over a period of several months. There is a user story in the backlog to apply the actual fix, but it just keeps getting deprioritized because these people don't care about bug fixes, only new features, new projects, new new new, shiny shiny new.
Today another developer received yet another report of this bug, and offered the suggested workaround of deleting the record. The nontechnical manager pings everyone to let them know that the correct workaround is to delete the record and to thank the other developer for his amazing detective work. I ping the developer in a private channel to let him know why this workaround doesn't work, and he brushes it off, saying that it's not an issue in this case because nobody will ever try to access the record (which is what would trigger it being regenerated).
A couple hours later, we get a report from support that one of the deleted records has been regenerated, and people are complaining about it.
🙄🙄🙄🙄🙄🙄🙄🙄🙄🙄🙄3 -
I always love to stare the application that I develop... First I start with admiring it... then the things that could have been done to enhance the feature.. then the bugs that could only be seen by me.. then all these results in new update of the application and this cycle continues 😂
-
Does anyone know if android 8.0.0 had a Bluetooth bug at all?
My pebble would just not stay connected to my phone (they are both brand new at that point) and when they did randomly connect it was for literally a second.
Now with 8.1 it hasn't disconnected once... I'm so confused!37 -
Begin working on new project
Don't know how to implement a feature
A billion solutions online, understand one of them
Spend hours implementing and google-bug-fixing
Get it working
Incompatible with everything else I want to do
Mfw.jpg
$ git reset --hard HEAD~ -
Product manager: When building new features, we find we have bugs that reappear in other parts of the app where the bug was solved before. We have to find a solution to this issue.
Dev: These are called regressions, they happen all the time in software development.
Product manager: ...
Dev: Fuck outta here! Its friday!3 -
Last Scrum Meeting, set up our new Container Server and installed Sentry (Bug Reporting Tool) on it. I was pretty proud, since it was one of my first DevOps thingies I had to work on. (I may end up as a DevOps Engineer after my Internship) In the scrum meeting, the colleagues just start saying everything with a French accent and just laugh about their french jokes while I'm in the middle of showing them sentry.. they were literally unstoppable... 😡 And weren't paying any attention to my presentation.
-
I spent most of a day a few weeks ago tracking down and fixing a NaN bug in a framework I use. I hacked it into my local copy of the framework's code.
Today I have the same bug, and after several hours of searching I finally realize I'd updated to a new version of said framework and so had overwritten my fix....
FML3 -
Around three months ago in a meeting regarding a new end2end test for a product :
PO: We have a full feature stop, only bug fixes are coming until we can unify all products.
Me : So I can use any selectors without worrying the whole thing breaks with the next update?
PO: Sure.
Last Thursday :
PO: Yeah, we gonna overhaul the entire UI with the next release to get better UX.
Why would any sane person reinvent an entire product thats already scheduled for discontinuation in 2018? And how is it possible that a few months ago nobody knew anything about it? Are they using fucking tatot cards for management decisions?1 -
Samsung has a bug in their galaxy software that essentially makes you unable to store anything that's not in the root folder on an additional sd card. After 2 years, they still have the bug. Additionally some phones will shit themselves if you try to format an sd card with it
How the fuck can they just leave significant bugs. The whole just get a new phone every other year mentality/industry style is both wasteful and seems to contribute to garbage software7 -
most memorable bug I fixed
Line 1:
- throw new Error(‘test’)
+ // throw new Error(‘test’)
yes, this was committed code in production4 -
I released an Android lib on JCenter.
So far so good. What I didn't realize was that I had a terrible bug related to a content provider.
Since I was using the ContentProvider to make my CursorLoader work, if someone installed an app with my lib, you couldn't install another one with it because it would conflict the providers.
I had to quickly find a solution and dispatch a new release. -
This is so nice..💙😄
<Heading>
Synopsis of Gita (religious book of Hindus)
<Stanza 1>
Code is an illusion
Today you are coding
Tomorrow someone else would do it
Thereafter someone else
<Stanza 2>
What did you learn
That is helping you in this Project
What are you learning
That will help you in your next Project
<Stanza 3>
Bug is the truth of life
It is today, and will remain forever
You think you have debugged the Bug
You are wrong
<Stanza 4>
It is continuous
In various new forms
It pops up
Recognise it Parth (Son of Hindu God)
<Stanza 5>
That's why go on making Codes
Don't think about the Bug
They will come to you
On their own1 -
Our Other it team asked me to create a new repository instead of a new branch in my project just cuz they thought branching would be more time consuming than maintaining a separate repo for emergency bug fixes.
-
Second week sick I see how my life slowed down and how meaningless everything around is, everyone is rushing about some bullshit, name it new amazing job opportunity, black Friday great deal, super duper product idea or some most important bug on production that we need to fix asap.
All that can’t wait a week when I’m healthy?
Seriously, people lost their minds in today’s world to some bullshit.
I’m to old and to depressed to care about such idiotic things. Living my life as I want and on my own peace, don’t care everyone is running, I’m slowly walking and I like it.
It’s better to walk straight than run around like an idiot.1 -
Do you have those little success moments while coding? Like the feeling of avoiding a new bug because of a test failing 😍2
-
The Hydra regrows three heads for every head chopped off. Just like fixing bugs. For every fixed bug three new pop up.
-
This week was one of those weeks were it feels like it's never ending
Monday, delayed trains and the legacy project's new update went live
Tuesday, not a lot of work so I did some self study (best day of the week)
Wednesday, again train delay, and some funny little sh*t ripped the valve from my bike... I mean sure if you let the air out, haha little fun but completely removing the valve? That's just f'n low...
Thursday, the legacy project had a weird bug that I can't reproduce but has to be fixed before the end of this week...
Friday... To be continued... I hope it will be a quiet quick and easy day... 😟3 -
Been working on a new project for the last couple of weeks. New client with a big name, probably lots of money for the company I work for, plus a nice bonus for myself.
But our technical referent....... Goddammit. PhD in computer science, and he probably. approved our project outline. 3 days in development, the basic features of the applications are there for him to see (yay. Agile.), and guess what? We need to change the user roles hierarchy we had agreed on. Oh, and that shouldn't be treated as extra development, it's obviously a bug! Also, these features he never talked about and never have been in the project? That's also a bug! That thing I couldn't start working on before yesterday because I was still waiting the specs from him? It should've been ready a week ago, it's a bug that it's not there! Also, he notes how he could've developes it within 40 minutes and offered to sens us the code to implement directly in our application, or he may even do so himself.... Ah, I forgot to say, he has no idea on what language we are developing the app. He said he didn't care many times so far.
But the best part? Yesterday he signales an outstanding bug: some data has been changed without anyone interacting. It was a bug! And it was costing them moneeeeey (on a dev server)! Ok, let's dig in, it may really be a bug this time, I did update the code and... Wait, what? Someone actually did update a new file? ...Oh my Anubis. HE did replace the file a few minutes before and tried to make it look like a bug! ..May as well double check. So, 15 minutes later I answer to his e-mail, saying that 4 files have been compromised by a user account with admin privileges (not mentioning I knee it was him)... And 3 minutes later he answered me. It was a message full of anger, saying (oh Lord) it was a bug! If a user can upload a new file, it's the application's fault for not blocking him (except, users ARE supposed to upload files, and admins have been requestes to be able to circumvent any kind of restriction)! Then he added how lucky I was, becausw "the issue resolved itself and the data was back, and we shouldn't waste any more yime.on thos". Let's check the logs again.... It'a true! HE UPLOADED THE ORIGINAL FILES BACK! He... He has no idea that logs do exist? A fucking PhD in computer science? He still believes no one knows it was him....... But... Why did he do that? It couldn't have been a mistake. Was he trying to troll me? Or... Or is he really that dense?
I was laughing my ass of there. But there's more! He actually phones my boss (who knew what had happened) to insult me! And to threaten not dwell on that issue anymore because "it's making them lose money". We were both speechless....
There's no way he's a PhD. Yet it's a legit piece of paper the one he has. Funny thing is, he actually manages to launch a couple of sort-of-nationally-popular webservices, and takes every opportunity to remember us how he built them from scratch and so he know what he's saying... But digging through google, you can easily find how he actually outsurced the development to Chinese companies while he "watched over their work" until he bought the code
Wait... Big ego, a decent amount of money... I'm starting to guess how he got his PhD. I also get why he's a "freelance consultant" and none of the place he worked for ever hired him again (couldn't even cover his own tracks)....
But I can't get his definition of "bug".
If it doesn't work as intended, it's a bug (ok)
If something he never communicated is not implemented, it's a bug (what.)
If development has been slowed because he failed to provide specs, it's a bug (uh?)
If he changes his own mind and wants to change a process, it's a bug it doesn't already work that way (ffs.)
If he doesn't understand or like something, it's a bug (i hopw he dies by sonic diarrhoea)
I'm just glad my boss isn't falling for him... If anything, we have enough info to accuse him of sabotage and delaying my work....
Ah, right. He also didn't get how to publish our application we needes access to the server he wantes us to deploy it on. Also, he doesn't understand why we have acces to the app's database and admin users created on the webapp don't. These are bugs (seriously his own words). Outstanding ones.
Just..... Ffs.
Also, sorry for the typos.5 -
I started programming on a new POS machine and I noticed that sometimes it reboots randomly. The boss and the assistance said that it's a well known bug and happened also in all old machines. Ah.... Ok.
And that shit costs a lot and it's stupid as fuck. Really? How the fuck is it possible? Sometimes I think that if I put a cardreader and a printer in a 50$ android phone I would save a lot of time6 -
Everytime I face a new bug, my innerself tries to convince me that I can never find a solution to this.
But my gut feelings know that sooner or later I've always found a solution.
Thanks to all the devs sharing their problems in the internet. -
Inspired by a programming is a constant/continuous thing. Every small and big achievements, from squishing a bug, finding a workaround, pressing the "Build" button and the programme runs. Each time the brain feels expanded like when a baby discovers new things, a tiny creature in a gigantic Universe of endless possibilities.
-
Me and new guy are working on something. We're both in different countries.
New guy just graduated a couple of months ago. Thinks he's better than us, egoistic, refuses to accept his mistake. Cannot work well in a team and arrogant. Basically a package.
I fucking spent 3 hrs trying to look for a bug in my code, which doesn't exist in the first place. Because he's a lazy fuck and refuses to even accept that he might've made a bug (evident from the fact that his first reaction was to blame me and second reaction was to verify his code)
And he doesn't have the decency to admit that he made a mistake.
What's even more sad is that I've to babysit him cuz he's incompetent.
It's fucking obnoxious.2 -
I was kinda proud, when I released a new test version of my android app, since I had a couple of new features and bug fixes. As soon as I told a friend of mine about it he found a error that has never occured before in the method. This only happens in the release build. Why does it happen? BECAUSE SOME DAMM VIEWS WANT TO BE INITIALIZED AFTER DAMM THE APP HAS BEEN PAUSED/MINIMIZED1
-
Omg I have to check 2350 svn commits.
We have 2 seperated frontends, one for maintaining old UI and one for new UI which is going to production in one month. So now I have to check if any CR/bug was implemented/fixed only on old UI. Frontend2 was created last year on july. Fuck my life2 -
I cant keep this inside anymore I have to rant!
I have a colleague that is an horrendous loose bug-cannon. Every peer-review is like a fight for the products life.
Now I understand - everyone makes bugs me included and it is a huge relief when someone finds them during peer-review. But these aren't the simple kind of bugs. The ones easily made when writing large pieces of code quickly. Typing = instead of == or a misshandling of a terminating character causing weird behaviour. These kinds of bugs rarely pass by a peer-review or are quickly found when a bug report is recieved from testers.
No the bugs my colleague makes are the bugs that completly destroy the logic flow of a whole module. The things that worst case cause crashes. Or are complete disasters trying to figure out what causes them if they are discovered first when the product reaches production!
Ironically he is amazing a peer reviewing other peoples code.
But do you know what the worst thing of all is! Most of the bugs he causes are because he has to "tidy up" and "refactor" every piece of code he touches. The actual bugfix might be a one liner but in the same commit he can still manage to conjure up 3 new bugs. He's like a bug wizard!
*frustrated Aruughhhh noises*9 -
Most interesting bug (recently at least)... In JavaScript, you can create a date with new Date(dateString).
...if it starts with the year or is ISO format, it will take the user's local timezone into account. if you did something like new Date('6-Jun-16') it doesn't care about time zones... so depending on how we passed a date via the api, we'd get a different actual date.4 -
I have a demo meeting tmr but the web app written by the junior dev is in crap state. Forget about new features and bug fixes, I probably won't even be able to correct and clear all the spaghetti codes. So instead of working on it, I am trying to encourage myself by creating quotes images.
-
It's been 1 week since I started my first Job. Currently I am given task to do bug fixes on WordPress. In 1 week time I am already under extreme pressure. Today is Friday and I need to look at 3 different projects. Plus on top of this I am new to WordPress. I sometimes go home and continue the work to meet the strict deadline. God this is hard!!3
-
bug comment in the tracker, from the new junior dev, during her first week:
"probably fixed by [other dev]".
Among the unhelpful comments, this was a special gem. really special. a What the Fuck did you mean by that special. Was it fixed or not? who fixed it? [other dev]? someone else?
it was better not to have any comment at all.
later that junior became a really good dev... -
for one split second I thought I had discovered a way to manage multiple states with one reducer function in react,
turns out it was a bug in my code,
I had already gone to brag about it on my react group chat, until I went back to my code and as I was cleaning up and closing brackets and all that stuff, my new feature stopped working.
I need to find that bug3 -
Sometimes I think that my computer is possessed.
The story goes like this (typical): adding a new feature creates a bug with something that worked perfectly until now. I find and solve the bug in a few minutes. Now the spooky part: with that sort of bug, even the code that worked up to now shouldn't have worked. But it did. Does someone knows a good Ghostbusters service?1 -
I absolutely treasure the bug reports we get from users. Nothing helps bring the product closer to perfection than the informed critique of end-users.
Recently, however, this one dude is filing a new fucking report every time he encounters the same fucking bug. "X happens for operation Y on file A"
"X happens for operation Y on file B"
.
.
.
"X happens for operation Y on file Z"
Jumping Jesus Christ, man, I'm pretty sure we can identify a pattern after the first two!
I don't expect him to know about the work we do to reproduce a problem after one report but fucking hell, have some faith that we'll get the picture after two or three.
These are fully detailed bug reports too, so it's not like he's just being a troll. -
Honest question:
I did a project and delivered it, but my boss did 4 commits after that. Without giving me any feedback.
They were small things: using a different library (just one line), and removing one debug line that caused a bug.
Should I ask him for feedback or just tell him "Hey I saw your commits, I'll make sure to use the new library and never let any debug line in"?7 -
After an important meeting where you actually get to give feedback and share some of your ideas for new features or bug fixes, one of the managers sends a follow-up email to the team telling you to get features done, like they were his suggestions.
Manager “I'd like you to work on.... “
Me "Right, that's what I wanted to work on... "6 -
I'd been with the company for maybe two weeks, pushed some changes and updates to a client's site on a Friday afternoon as instructed by my boss, checked everything over and it's all fine.
Come Monday morning and this client is seriously miffed, not all of the changes had applied and the site was a mess all weekend. Turns out a bug with the caching plugin meant what we were getting in the office was different to outside.
Meetings were held and a new QA procedure was put in place. -
Wtf is happening to tech security... Last 4 months
All WiFi is now crackable. .. in short amount of time
Windows . . Annihilated with this new bug might not be fixable... and work back on all of them
iPhones cracked ...
Linux dirty cow ...
Android been suffering.
And everyone knows Mac's security is joke ...
Finger prints ... Made pointless on everything.
Literally all going to shit .. 😐
And I know how to do all this... It's all out in the open not even hard to find8 -
Looking for bug bountry online and trying to find sqli bug.
I tried using sqlmap but no success.
Is it about WAF they're using or sqlmap is not complete ?
(I set the level and risk to highest possible)
Thanks
@ExGetMessage6 -
Got our snazzy new HP Elitebooks from IT. Nice lil laptops.
Guess how many apps they installed for us off the list of "Applications Devs Need" that was submitted with the original request that they asked us to provide.
Goddamn 0. 0 Apps installed. ”Instead here is admin access, install what you want.”
Being a PC guy I don't mind setting up a new environment but things like Office365 and Adobe CC could of been installed for me, I don't have the licence info offhand so now I gotta bug IT again and why ask for a list if your not going to install any of them?? Ugh. I don't have time to sit here while Adobe installs the whole suite....
/rant
What's the first thing you install on your new PC? I find I grab ConEMU first.6 -
Hey guys, I need some junior advice. I work at a small startup in a team with 2 other backend developers.
The "new" guy studied at a university for a few years. He writes beautiful code. I try to learn from it and use his short hands a lot. I came from highschool and don't have a degree in it (yet).
I recently wrote a piece of code which handles some timeslot logic. I was really proud of it.
New guy needs to fix a bug and add a few things. He completely refactors my code and makes it more structured and partly better. The logic stayed the same.
It sort of bothers me that he touches my (precious) code. How do you guys handle these things?21 -
Curiosity killed the cat.. or was it Opportunity?! 🤔
You get to learn new stuff daily.
Not one assignment is the same, and if it's similar, you can hijack the old code, improve it & turn in the better version of it.. or don't improve..totally how you feel that day..if you're not a crappy developer no improvement should still also be ok..
I love mostly adjustable schedule, so there's no biggie of I have a day or two of coders block & can't produce much of value..I can switch tasks & do some simple ones on those days..or just refactor.. all's good..
I love solving puzzles, every bug is a new puzzle I can play with..
So basically, I love being a dev, because it's like being back in school, but only with the subjects you like! -
The bug I never fixed isn't a bug in code I wrote, but rather an OS problem I've given up on fixing.
I dual-boot Windows and Linux on my desktop PC. Every time Windows updates, it switches from grub to the Windows bootloader, making it impossible to boot into Linux. I've fixed it three times (each time requiring a different fix, from disabling fast startup to reinstalling Grub from a live USB), then gave up. My desktop PC is now a Windows machine. I'm upgrading some parts soon (including replacing my boot drive with an NVMe SSD) so I decided when I do that, I'm just going to reinstall Linux on the new drive and see how long I can last without installing Windows at all.3 -
A customer asks for a change request or a bug fix and it results in creating a ticket for that.
It's the process and how it works in most places but after you finish with the task and fix the same customer who provided you with the requirements will request that you share the steps on how to test the fix or the feature.
I'm not speaking about the data preparation or required configuration. I mean a step-by-step instruction on how the tester/QA will test it.
It's driving me mad!! So a way to counterplay this stupid requests, I provide the happy path and what to expect. And in case, they stumbled on a bug later in production, I can easily say "It was approved by your testing team and that's a new requirement ;)"2 -
> [PM from a totally different project / team comments on already-closed 10-line PR] How about we [add a totally new feature involving several engineer-weeks to patch over a fixable bug in another part of the system] instead?
> [me] we can talk about that, but it's nontrivial and we should scope any work relating to it to be sure we're doing the right thing
> [him] [starts private email chain] this should be simple. Why isn't this as simple as that other change?
> [me] [explains why]
> [him] I think it should be simple. We'll talk about it offline tomorrow and maybe you can do it next week.13 -
InitiativeQ is a new currency built by ex-PayPal guys and they're currently giving it away free...Unlike the cryptos you've lost a bunch of money on! If you play the lotto or buy cryptos, you should def. get on board with this. All you need to provide is name and email and they promise not to sell your email address or bug you with spam emails.
By invite only: https://lnkd.in/ei5HBhZ27 -
To fix a bug I added a few log messages to trace what gets executed and in what order (very new to the project). Fixed the bug, pushed PR and the only comment was to remove the log files. 🤦♂️🤦♂️
Please tell me this is normal or should I start looking for a new place that hires "only the best" 😭10 -
Finally fixed that bug after hours of debugging, and a bit of crying/screaming… and now I have a brand-new error message to cry about. Progress I guess?1
-
Most interesting bug caused - created printer driver for vietnamese diacritical marks for old matrix printer without VN support by switching to graphics mode and plotting the dots and dashes. Print speed reduced about 200x and printer shook itself to pieces by rotating the cylinder back and forth. Oh well... Ended up buying two new laser printers instead.
1 -
When IT is like : hey our new grafana is at this place "some URL"
I submit a bug ticket: "I can't see metrics about this server that has been running for a while"
Their comment on the ticket : the URL to the old grafana -
I have made a lot of small changes in my app like minor bug fixes, Animation, optimizations, better database management, new options, overall interface improvements, ... to give the application a better overall appearance. Then I decide to show it to my Client.
"From what I can tell, you haven't done much since last time"1 -
When you get brought into a new dev job and the lead tester says "oh good, the junior bug boy is here"... Not sure if he thinks I'll be squashing them or making them...
-
> Finally write some wicked code that fixes a weird race condition bug we’ve had for two weeks now
> xCode breaks for absolutely no reason on a build so we can’t release a new version
🤦♀️1 -
I'm so frustrated right now.
I put a lot of effort in a (voluntary) web project where its main component is based on a html table. Everything tested in dev (Chrome, FF), demo deployed and now I open it in Safari (macOS) just to discover that the rendering is broken. A Google search revealed some people with similar problems and many unanswered StackOverflow questions. It's unfixable.
Why Apple? Even MS got its sh** together.
It's unpaid work... I just wanted to something good.3 -
Google made sure that devs understand Layout Editor has lots of bug fixes in AS 3.4,
I'm now at 3.4.1 and that thing still crashes (stops responding to changes unless I do them in XML) when I just add a damn new control in an empty window!
I hope they get it right anytime soon.
So my situation right now:
XCode shit when writing code but has some robust Layout Editor
Android Studio: Amazing when writing code but shit when using Layout Editor
Guess one can't get the best in at least one of them :\3 -
My new feature has a bug in it, but not in Internet Explorer..
Huh? This is new! I know this the other way around! -
testing feature: that is not what the specs say this how this is suppose to work. so, I write a bug report.
conversation with developer goes as follows
developer: this is not a bug. sends the bug report back.
me: the specs say it is a bug. I resubmit the bug.
developer: sends it back saying that it has been changed in the new specs.
me: how do I get the new specs?
developer: it is on the server, go ask your boss on where ecaxtally on the server they are. then, he closes the bug report.1 -
Everytime I applied long leave, my client and PM will plan for important feature, but they say start the sprint and for other new people i have to give KT, and they will take care. I know how that will screw up the system. So at the time it's nightmare late night at office, in office time KT, no weekends, stand-up for 1hr(every time QA will ask, what we get after this sprint). Stupid clients changing the requirements after stand-up.
Everytime code base screwed and need to refactoring. So as much as possible core functionality I'll complete and only bug fixing for newbie. I hate those days. -
Confession: a very important feature of the website I'm developping wasn't working for a certain time. The boss wasn't aware because he doesn't go on the site, and I only found out last week because I needed to implement a new feature that used the previous one. Problem: the bug was only on production, not on local (and of course we don't have test server).
I took advantage of the absence of my boss today to clear the situation by making all of my tests on prod. I hope no customer tried to pass a command today, but it's finally repaired. I am both proud and shameful.3 -
Customer calls
Talking about some new feature he haven't totally thought about. so i tell him to think about it.
Talking about a bug, but can't reproduce it.
Talking about another enormous new feature but halt it after hearing the initial estimation.
Total time waster = 1.5 hours for every day.
DON'T LET CUSTOMERS WASTE YOUR DEVELOPMENT TIME.
instead of talking - use project tracking software (i.e. JIRA) -
Yesterday‘s Windows 11 update brought back an old bug which I haven’t seen since Windows 8 or so.
The EN keyboard layout is added in the task bar UI but it‘s not actually there when you try to remove it in the settings.
Fucking hell! Why even make new versions of Windows if it‘s all the same pile of shit?
That‘s not the only old bug that persists across multiple major Windows versions!3 -
Starts search and replace.
Trys to replace a type in the whole Project.
Syntax Check: lol no, apparently everything is broken now, good job
(literally my whole project was marked red)
Reverts changes
(project still marked red)
Syntax Check: lol what? Your code already looked like shit before, won't let you compile this.
It was a bug which breaks the syntax check after big replace requests. Had to start a new project and copy my code step for step, so it didn't break again. However I've forgotten to replace the type before I copy...
Another story regarding this shit:
Renames Variable
IDE: oh, let me help you by replacing all old var names with the new one
Agrees
IDE: oh shoot, didn't know it could break things
Wants to revert
IDE: did you think I would go through this mess again?! Do it yourself!3 -
Bug in the Webapp
(maybe its already been reported before...)
If you load the new top feeds
https://www.devrant.io/feed/top/day
https://devrant.io/feed/top/...
https://devrant.io/feed/top/...
https://www.devrant.io/feed/top/all
the button "more rants" opens
https://www.devrant.io/feed/top/2
This URL doesnt work. Its reloads page 1 of the "all" feed
https://www.devrant.io/feed/top/all
The links
https://devrant.io/feed/top/...
https://devrant.io/feed/top/...
https://devrant.io/feed/top/...
https://devrant.io/feed/top/...
don't work ("page not found")4 -
Bug report
Using a physical keyboard seems to prevent me from being able to complete a post. I can open both a comment and new rant, type the contents but am not able to post. The button doesn't do anything.
Switching off the keyboard seems to cause strange behaviour (deleted this rant the first time I was trying)
My setup:
Moto z play android 7.0
SwiftKey keyboard app
Logitec K810 Bluetooth keyboard3 -
Never fixed? lol.
Maybe I took hell of a time, maybe I've ignored it for long but at least I've always fixed bug which I came across and will fix if I come across any new (as there might be many hidden :P ).
As I mostly work on eCom and integrations, it's way too risky keeping bug.
Cheers!! -
Wanted to try a new alerting based on a new Prometheus metric we added. To trigger an alert we killed the dev stage db of the service. Alert didn't get triggered. The reason was that the metrics endpoint suddenly needs exactly 60s for a response if the db is killed and prometheus timeout is 20s.
And to top it off, this behavior happens for each service we developed (that has a db) .
Well at least the new alerting already helped find a bug.2 -
Hey look at these awesome features we offer in the new version!
*carefully upgrades servers*
*app runs smoothly for few hours*
(Docker container exited with code 137) x 100
OutOfHeapMemory errror
Another dev: "I can't see the data flowing through the pipeline"
Boss: "Hmm, why did we upgrade again?"
*checks jira issue for the software*
Bug Report #125 fixed in the next version.
Aha!
Fuck this shit!1 -
Back in the early noughties I had an interview for the new job. A couple days before the interview I've visited that company's website. There was search input. Of cause I've entered some hacky things into it. And after several attempts I hacked it. The site was down in an infinite loop.
Two days later I told interviewer about the bug and what I did to reproduce it. He was surprised and checked the website. It was still down the same way.
I was totally ashamed. I was supposed to report that problem somehow.
BTW I got the job:) -
I joined this company last month and all of a sudden I'm assigned to fix the most important fucking annoying bug that no one in the dev could reproduce.
Im beating my qss going behind people asking questions. Because iits my second month and I'm still fucking new.6 -
Sad because I was performing an extensive code integration of a release from an external source and then an employee from another building integrated another release before me
Now I need to request a new release with the bug fixes and it will take various days, maybe weeks (and if another release is integrated before, the cycle restarts).
I might be able to integrate by the end of the next year. Who knows. -
Not sure if someone reported this or not ..
But after I post my rant, and try to write new one .. I find my previous rant already there with the tags.
It might be a bug in the autosave2 -
Me: I'm gonna work on my personal project on my lunch hour!
*spends whole hour investigating one brand-new bug and fixing it*
Me: :/1 -
I love it when I manage to fix one bug and then 9 new appear, like a Hydra. Mythology at its finest.3
-
I feel like i am being forced to own a shitty module in our codebase.
It was developed by previous owners and they made a frankenstien monster out of it: Its one part of codebase that is very huge, does not follow the code standards, is making complex kinds of api calls and using very niche components. It gets bugs once in a while BUT IT WORKS.
It fuckin works and is one of the important steps before customer purchases a company product, so kinda part of revenue generation flow.
But this module was never a part of our codebase which we would usually touch. it was owned by another team, they would add enhancements , new features to it and fix the bugs .
When i joined the team, i was once asked to help those guys as a "resource" because they wanted to get something shipped and were low on bandwidth. So i just worked on one of the screens, added a small bugifx and voila, task is done and am back to other part of the app.
But now out of random, they decided to pass on the ownership to ur team, gave a small KT which didn't really explained a lot of actual codebase, but rather the business functionality of it(and that too poorly). And my TL is saying that i should own it because "I worked on that module before"
I don't know how to deal with this frankenstien monster. Earlier a bug came and i was out of my wits to understand why this bug came. their logging is weird and not explaining a lot, their backend devs help provide aws logs but those aren't very helpful either .
the best i could do was declare that their technical approach is wrong and we should modify it, but that idea was quickly squashed.
ITs quite possible that company isn't going to change this module or add any new features further. but everytime a bug would come, i would be getitngfrustrated looking at their frankenstien monster5 -
https://stilldrinking.org/programmi...
/\ This is why all programmers should go on strike for a month and collectively collaborate to code a new, clean, bug free internet where nobody but you can control your data.
Also. It should only be added to by people who know how to code in order to maintain this clean code.
We can call it "internet level 2" or "internet 2.0"4 -
I use Microsoft Word like once a month. Every time I open Word there is an update to all of the Office Apps. And the update take like half an hour to complete.
I usually like updates and install them, because I hope that the new version maybe patches a bug or makes the software more efficient, but unspecified updates that often is frustrating.
1 -
3 or 4 weeks ago me and management had a talk about new features in our product...
So we implemented the new features and then we released the app...
Today I got a really long bug report that summarizes into the following sentence -> BUG: Everything works exactly as we talked 4 weeks ago.... And apparently that is bad 😣
Like c'mon dudes if now it is a bug then why the fuck I needed to code that feature?! Time totally wasted for nothing! 😤
Fix My Lighthouse!1 -
When you're trying to fix a bug in your project and realize the problem is a bug in the platform your project is built on.... FML
---
Searches mailing lists for the problem
-- Hours later --
Finds that bug might be fixed in the new unreleased build.
--
Installs release candidate of new build.
--
Still broken.... *Facepalm*
Now to try an old build and see if that works...2 -
Just spent 4 hours on a bug with Postgres in Node. Turns out when you create a new client, and then end it, You need to create a NEW client (I guess because the old one is bad??).
Thanks for the shitty error messages Postgres. I want 4 hours of my life back.1 -
Today we picked an old (6 months old) iOS project back to add some features. We clone repo and run `pod install` to pull the dependencies.
There seems to be a bug with FBSDKCoreKit (facebook SDK) and the only solution is to delete the Podfile.lock
if we do this, it will pull the new version of every dependency, and the public API of each dependency is broken. Meaning we have to spend about 18 hours+ just to make this shit compile.
Fuck this shit!! -
I've a whole new respect for ElasticSearch. It's codebase is so insanely complex, that I'm seriously contemplating tracing out the flow on a big ass chart. Any suggestions on how you people work and debug so many asynchronous flows?
I have been working on a bug, for almost 6 days (to be read as 3 consecutive weekends), and the best I've done is, conceptually isolate where it's happening. I'm an open source noob, but I feel I've learnt a whole lot during sifting through ES' codebase. :)2 -
I miss bug hunting... Baking new features is far less fun than debugging all sorts of weird issues across all the layers of the setup. Devops has its charm, but still I find myself looking for problems more often than tinkering with devtools.
I wish there was a "debugger" role in my company.7 -
Ok, So I am just fed up with these project delivery dates. These are the most irritating aspect of any project.
My current project is already delayed 3 times, because of the optimistic biases of the team lead.
Developers were forced to work over weekends. The QA cycle is taking more time than the dev cycle itself, and it's very irritating waking up with a new bug in the JIRA notifications.
Everytime we reach the delivery dates, there will be multiple bug items on each and everyone's plate that you just can't release the product.
I want to know if anyone feels the same ? How does your management takes care of these delivery dates ?1 -
Probably a bug @dfox
I've been providing my feedbacks through the Feedback menu. However, I'm writing this issue in here just to know if I'm alone.
-------
Issue
-------
Platform: iOS
When I clear the notifications and refresh the timeline for new rants, the notification badge shows a number. But there is no unread notification when I go to Notify. This has been occurring multiple times now.9 -
Got a weird bug today...
A new feature I just implemented works but outputs nothing.
So I start printing its inputs early in the code, fine no problem here. Then I print out the supposed results a little bit later, fine too. But now the full program work perfectly.
I find out that if I remove one of those two prints then suddenly my function start outputing empty arrays! WTF?
I think I find a quantum bug, you can observe the bug or the internal values but not both!5 -
Man, at the rate I'm going, I'll have to put a bug I found back in April on my new years resolution list...
Sad thing is, as we all know, new years resolutions never work out... So maybe this bug will never be solved :S -
Don't you love the neverending sprint?
You know the one that just inherits all the tickets from the last one? Each sprint packs on new cool features but along the way bug tickets come in for code you haven't even touched or wrote and you deal with them because they are blockers.
before you know it, sprint is over and ok to the next one. I'm pretty sure that is how this is supposed to work right?1 -
Bugs: These are not bed bugs. For programmer they are a nightmare, to customer we introduce them as a new feature and say, “My software has no bug. It just develops random features.”
-
Wordpress.com are idiots. I have free site there. And now I want to edit my posts and I clicn on my site in top left and it does not do anything. And its not a first time. Wtf. Fucking idiots. Even if they made a bug, for millions of users they should fix. Now what , millions of users cannot edit their sites? idiots. And I see no way otherwise to edit my posts or add new.
Or I click write when loaded my site, and it fukcing opens white page. What a fuck.3 -
Working on fixing a problem and broke something else! HOW? 😩😭😭
...and I still have not fixed the new problem
🤦🏽♂️4 -
When your boss asks what you're working on and you say "Fixing a bug that causes new subscriptions to be prorated to line up with old ones." and he says "Terrible. Needs immediate fix."
"I know! That's what I'm doing!!"1 -
Hello, my first time here. I got to know this website/app from my PM because I need to vent it somewhere other than him according to my PM.
So, here goes my first rant. The date is today (Monday). The rant subject is our new tester. Some context on the guy. He started in our office 8 weeks ago and his title is senior tester with some years in testing. Me and my team with the exception of our PM are new hires and for me, this is my first job after graduation.
After a grueling month of pushing for new modules and bug fixes from our monthly UAT from the client (yes, this will be a future rant one day), about 2/3 of the team is on vacation paired with a long weekend. So, a very few ppl in the team including me and my PM came for today.
I usually came quite early, around 8 am as I commute with public transportation. As soon as I have my breakfast and just getting ready to open my dev laptop, he came to me with a bug. This is like under an hour I came to office. I'm ok with anything related to the project as today was deployment day to test server for our monthly UAT. So, I check the bug and it wasn't my module but the PIC is not there and I familiar with the code thus I fixing the module.
Then, not even 15 mins later, while fixing this module, he came to me with another bug. I'm still the only one who in office that can fix it thus have to do it too. Finished the both bugs, pushed and je retested it. Fortunately, my PM and another colleague came. But, for some reason, he only comes to me for the bug fixes.
The annoying thing for me is that he comes to me every time he found an obstacle, bug or glitch. At this rate, by hourly. Thus, this cycle of impromptu going around fixing-on-the-go for the project begins, for me. Then, my PM asks him abt our past issue log given by the client UAT. Another annoying part is he never checks the clients feedback to see if the result can be produced again. The time he checks it is when ppl ask abt it and test it 1 by 1. Then he came to me again with why x person marked it as done. Like hell I know why they marked it done, you the one who need to check with them. Thus, I called/messaged the PIC for x modules abt the issue and then they explain it. I have to explain it again to him abt it and then he makes the summary report for the feedback. This goes until lunch.
I thought the bug fixes is over and I can deploy it after lunch. I thought wrong and I kinda regret coming back early from lunch which I thought I can rest for a while with the debacle over morning. Nope, straight he comes to me after I sit down for 10 mins and until almost work hour is done, he came to me with small bugs and issues like previously, hourly. By then I think I crushed like ~10 bugs/issues and I'm knackered. I complained to the PM many times and the PM also said to him many times but he still does it again and again. Even the PM also ranted to me abt his behavior. The attitude of not compiling an issue log for the day and not testing the system to verify what the client feedbacks are valid or not is grinding my gears more and more. Not hating the guy even though his personality is quite unique but this is totally grinding ppl's gears atm. As of now, it's midnight and I finally deployed the system to the testing server. This totally drains my mental health and it's just Monday. May god have mercy on me.
Owh, the other colleague that come today? He was doing pretty much the same thing but he was resolving a major issue which is why the tester came to me.2 -
Working. Finding a bug. Quick-fix. New bug. New bug. New bug. Spending 1 hour looking for Quick easy solution. Getting distracted with a more complicated solution. Spending 1 hour researching. Back to problem, one more hour bruteforcing the problem. Finding it was just about a configuration problem. Fix in 5 minutes. Repeat everyday.1
-
Every new day a new Intellij idea BUG ....
Don‘t believe they actually charge you money for this crapware ... how can anyone be happy with that??3 -
So many occasions to choose from! Probably the most pissed I've been is when I'd been assigned to work on (and completed fixes for) the same bug as another developer twice in the same week after already having spent 4 days working on a new enhancement that's requirements changed literally an hour after I'd saved the code!
-
I've been asked to release a project which has been written by someone else, then rewritten by another developer, and both have left the company.
I can't release it yet because there is an inconsistent bug throwing some values out.
We've got it running side by side with an older legacy system which it's going to replace. Before the 2nd developer left they added some logging to our live system to record both values so that they could be monitored to make sure there was no inconsistency.
There are some inconsistencies... however, when I run the same data through the new system and the legacy system in a test environment they both come out correct.
FML
I've considered quitting...2 -
Hey all,
Where does devrant for Android store downloaded images? And yes I allowed saving and storage access.
Android data folder is empty. Bug?
It did work before i switched to Android 8. My new phone is also android 8, and it also does not work.
Greetings17 -
-Recently started a new job so I’m new to the infrastructure-
Spent the vast majority of the day trying to SSH into one of my company servers to sort some random bug out on the website & the connection kept being rejected despite the day before it working when passing the .pem key into the SSH along with the ip & my username, nothing new there.
Anyway, everyone’s mad busy so I don’t wanna bother anyone to ask why, so I check confluence, no documentation for SSHING into our scheduler or the code the server I need to access. Never-mind.
Spend another couple hours trying debug it on my own, no luck. Never-mind.
Finally seize my opportunity and ask for help; ‘Oh the server IP changes daily so you need to run a task through our scheduler that you need to SSH into to return the list of IPS and that dynamically changes so that’s how you get the IP’
Oh ok. Why is there no documentation for that again? I mean. Thats generally some pretty important information you’d pass onto your starters.
At least I can say I won’t be making that same mistake again.5 -
Friday morning's meeting:
CTO: Ok guys, deadline is next Friday so today we close the last big issues and next week no more new features, only bug fixing.
Monday morning's meeting:
Business: So here is the new mock-up for the search feature (basically they changed the whole behavior).
😐1 -
I've wasted hour to fix bug in my program.
Basically there was problem with auto updates system (two exe files - one is program itself, and another is update Manager which replaces old exe with new one).
I've managed to make bug which causes to infinite update loop...
The problem was instead of calling program "helmet_updater.txt", it was calling "helmets_updater.txt"... -
When you’re working under high pressure, a coworker writes you that you have a bug in the new feature which is blocking him and you start swearing about what an idiot you are...
And you then realize that this is the team chat with SM, PO etc., and not the private chat.. -
How the hell do I plan and put in place new procedures for testing and THEN updating software on our department server 😫 (a 7zip bug got us good recently lol)
why couldn't this be a procedure before I started working here. I don't know how to create a procedure document. What if I forget to write a step
Fuck I just wanna go back to my code not a word document3 -
Deleted a cloned directory for a project which I had made several bug fixes and updates on. I just noticed I couldn’t find the updated files folder when I want to clone for a new project. Sadly this means I must have deleted the directory thinking it was a duplicate of the initial project.
I have no backup and for some dumb reason I forgot to create a repo for the newly cloned directory. I have cleared my recycle bin multiple times prior to now.
I use mac and I need help! -
Chromium dev tools and Lighthouse audits sound like a Chrome features marketing campaign, once you proceed beyond basic optimizations and bug fixes, like
use our new image formats, stop shipping old JavaScript to new browsers, provide a source map, use web font preload but only if you use it exactly matching the best case scenario, rewrite your manifest file which used to work just fine etc.
actively encourage people to exclude up to 5% of global website audience?!
"This means that 95% of global web traffic comes from browsers that support the most widely used JavaScript language features from the past 10 years"
https://web.dev/publish-modern-java... -
Asking for a friend....
New job, fairly new to web development, very new to JS. I am failing miserable at my job can’t complete tickets which are mostly bug fixers created by testers. So I am debugging code that I didn’t write on a tech stack I do not know (ampersand, q, radio, lodash, react, etc)
Do I try to learn the language better?
or
Focus on learning debugging with dev tools and getting better at using the webstorm IDE.7 -
I think you already know by now, but I have to say it. The update of the discord app is utter shit, brought only downgrades to me and they still refuse to fix bug that have been prevalent on their platform for years to force their shiny, new, untested bullshit down your throat
-
When I was working on the bug list and our testers kept repeatedly assigning me new bugs and "do-overs" I don't think I've ever been so angry
-
What do you think about the new Youtube layout?
New Youtube, new bugs.
I reported a bug when it was opt-in and guess what, it's still here: in subscription feed's listed view, scrolling is laggy after loading more items with stepless scrolling (e.g. Chrome w/ touchpad). So many unnecessary animations.
It's just really frustrating when you try to info large company about a bug and they do nothing. The previous ones are also still there...
I guess it's time to reboot my Youtube Data API client project, which I started just for this reason.3 -
When you have a customer that is a pain and you have to do a new contract since months but they are no replying but at same time there is a bug in a plugin they are using.
They are not updating their plugins in production but only after a test in staging.
In production there aren't write permission from web server side, so only they have access.
And the plugin has a 0-day. -
A young new dev was working on his first ticket, about a bug during parsing of an uploaded excel file. Our issue was that if the file contained an empty line, all remaining rows were ignored. So the task included extending our tests to cover this case. After 2 weeks (!), his merge request comes in. His idea (without ever asking for help) was to parse the whole file (in some cases huge) in the production code a second time, just to count the rows (!!) and save the count in a public static int field, which was verified in his new test.2
-
Does anyone know if there actually is a way to make URL alias? Like:
I wanna go to https://maps.google.com
But instead I only wanna type : maps.google
Just like that new thing of Google "sheets.new"
Or are there any Google Developers that may see this and are gonna implement this 😉
And I know: But why don't just type .com behind it? Well.. If there is one thing that I've learned as developer it's that every second you spend to long on one thing.. You actually waste because at the end you could've wrote a whole project! Or fixed a bug or something like that. You know what I mean17 -
I was new to Android development back then. One of the project requirements was to implement a feature, that will prevent the users from turning off the phone. Even if the users tries to turn off, the phone shouldn't turn off (specially when the phone battery is sealed). So, I tried a method and it works! But later the users reported that the feature doesn't work! I mean, I can clearly see that the feature works in all the phones I have ever tested. But later I realized that the feature worked in Debug APK but not in Release APK. I mean, seriously? It's not even some kind of pro-guard issues that happens with GSON+Parcelable. So, I did it again using a new method. Again, it works in Debug but not in Release. After trying and failing multiple times, finally I found a solution! May be this bug alone took me almost a week to fix it!2
Top Tags
Weekly Rant
View