: I'm pretty sure the issue isn't that they disabled him instead of leaving him in, it's that they disabled him instead of hotfixing the bug or something. It seems like a pretty incompetent solution as a developer, this really shoudn't be happening unless they're incapable of figuring out how to fix the bug which is another thing that really shouldn't be happening. Riot is basically announcing "yeah we have no idea how to fix this one, sorry"
This is an absurdly naive way to think. I don't know where people got this idea that bugs and defects can be fixed instantly. Hell, if you do not have _exact_ instructions on how to replicate a bug, a development team may never be able to reproduce the bug in question. A sizable code base with multiple developers writing code over many iterations of a product will have quirks. Developers are given a task, and as long as the code passes new tests, regressions tests, code review and user testing, then the code is considered valid. Even with these safeguards, developers can sometimes write code in such a way that causes unintended interactions that happen under very specific conditions. The code then needs to be refactored to fix the issue, pass the above review/tests and deployed. It sounds simple, but code is not magic. You don't always just look a few lines of code, think, "Oh there's the problem,", change a few lines and call it a day. That can happen for some bugs, but it's not always so easy. I understand that Riot's code base is far from perfect. We've heard the same tired excuse of not being able to implement a feature due to how something was written. However, development is not wizardry. Code bases with thousands of lines of code can have an absurd amount of dependencies and coupling.This can make finding the source of a defect like finding a needling in a haystack.


Level 31 (NA)
Lifetime Upvotes
Create a Discussion