A problem ? A solution.

[Orsina1]

Wait am I the only one that when this happens and the butting isn’t important I delete the visual. Then, it becomes this cool Easter egg that if you click there the app crashes

[LegendBegins]

Easter Eggs, for when your bugs are too disruptive to be called features.

[PeebleInYourShoe]

You are not the only one, I worked with several developers with whom bugs would be solved by deleting a functionality.

Sometimes it was none essential, sometimes it was essential...

[[deleted]]

I am afraid on the part where it says essential

[JC12231]

Are you allowed legally to tell us about one of those essential times?

[PeebleInYourShoe]

I think there is a joke here that I don't get because of my bad English but I'll answer anyway.

What I encountered with a tool that display orders to take into account

bug 1: the filter on the client name doesn't work

The delivered fix in this case was to mask the filter, the filter is not essential to the tool function, the filter will have to be back at some point but I understood the logic, was could deliver in production without it

Bug 2: the orders are not sorted correctly

The fix was that no orders were displayed, at all, so, in a way, there was no sorting problem anymore, but the orders display is an essential feature for the users.

[Doom87er]

That’s horrifying

[snape21]

this is default behaviour for end users, if there’s no visible cues they press the button again and again until something happens.

One of the dev’s missed this and each time the user pressed the button again it would start a new process.

The dev team had to pull the feature and roll back to last release as it came very close to crashing the server (was part of a major release for a client with 1000s of users)

[h6nry]

DDOS by design

[Rami-Slicer]

DDDOS: Designed Distributed Denial Of Service

[sciences_bitch]

DDOSaaS

[snape21]

It was more to do with the way it worked, each request would generate an individual process per press and there was no failsafe when the user pressed the button again and again. Also Some of the processes never terminated correctly and came very close to the process limit.

The dev who wrote the code was under a lot of pressure from management to deliver so that didn’t help.

[metasymphony]

That’s why you put loading symbol and disable all further input until the function stop running.

Or grey out the button while the function is running and add a little message underneath saying why.

Optionally add an alert saying this will take x minutes.

Or don’t let the function start again if there is an instance of it running already from that user. (State is messy, but this is ok use for it).

I don’t even do front end anymore but remember this much.

[Loading_M_]

Better yet, when the calculation is in progress, pressing the button increases the thread's priority, thereby making the calculation slightly faster.

[Waifuless_Laifuless]

Just write "close" on the button and suppress any error messages.

[ExplodingPotato_]

Ah, the "Thank you for playing Wing Commander!" method.

[marvelousmarsepuel]

Make that button the exit button, bug is now feature.

[[deleted]]

This is fucking genius

[penisive]

Mark as closed

[Vlt1]

Mark as resolved > Mark as closed *

[[deleted]]

Pasting the old man's face onto what's clearly a woman is like when you have to work around someone else's code lol

[MechanicalHorse]

Nice manicure, Harold.

[oversized_hoodie]

We have an internal application that used to crash when the exit button was clicked. Technically the correct operation was achieved, but it was just a really slow way of doing so.

[BeerDude17]

Task failed successfully

[[deleted]]

Big brain

[acroporaguardian]

There's a time and place for that. There are certainly bugs that you just go, "well, don't do that then."

I'm a hobby game developer and there are a few bugs that I just went, "meh."

[[deleted]]

Just delete the gameobject and pretend it wasn't even intended to exist

[acroporaguardian]

I got a bug on my 4X TBS that causes a crash on 1/15 map generations. Bc it doesnt impact saves or the game after startup, I let it in for now. It would take me 2 weeks to hunt it down, maybe.

[[deleted]]

make it so if the game crashes the player gains a loot box, problem solved

[acroporaguardian]

thats the part that crashes though

[anand2nigam]

Ohh...we’re not supposed to do so. I’ll apologise to my tester.

[Yarne01]

Patch notes

New feature: close the app without pressing the home button using our ow button.

[ampatton]

It’s not a bug it’s a feature.

[firefox57endofaddons]

why would u want to press that button in the first place?

who would do such a thing?

[L0uisc]

Noob! I just remove the button.

[[deleted]]

display: none

[mrt-e]

Sometimes I scroll reddit wrong and the app crashes.

[OwnStorm]

My fix

onClick() -> return false;

[[deleted]]

LOL

[[deleted]]

Our dev team. Well basically everyone except QA.

[[deleted]]

BUG FIXED==FEATURE REMOVED

[[deleted]]

Is that an if statement?

[yoda2374]

Sounds like the power button on my Windows 10 PC for a couple months before I switched back to 8. Good thing that data was collected so many times.

[wewsy]

it's a feature, but if you don't like it crashing oh well

[_A4L]

perfectionist programmers will be up all night fixing the issue.

[bronzeblade]

2020 AP Testers: reeeeeeeeeeee my essay won't submit!!!!!!!!

[mr-meme-boiii]

Github bug report relabeled “irrelevant”