GBAtemp.net - The Independent Video Game Community

Jiehfeng
Jiehfeng
Before I used to look at devs and think, "why can't they just check everything while they build?". But now I know the work is just so much that you really don't have the energy or care to do so and it's totally natural and understandable.
  • Like
Reactions: VinsCool and Sono
Jiehfeng
Jiehfeng
Bug fested games make more sense to me now, the scale of AAA games have grown exponentially, that scale just makes the developer not bother with cross checking previous work and whether they're affected by additional updates. There's just too much to cover.

The blame most likely lies in the testers, their understanding and effectiveness, and the communication with the devs.
  • Like
Reactions: VinsCool and Sono
Veho
Veho
1667831563763.png
  • Haha
  • Love
  • Like
Reactions: VinsCool, Sono, rvtr and 1 other person
Veho
Veho
No but seriously, bugs are not simply a matter of the code "not working". You run your functions when you write and build them, you don't just write them and believe they will work.
Bugs are a matter of that one single (but repeatable) border case that you didn't think of because it's extremely rare and extremely insane.
  • Like
Reactions: VinsCool and Sono
Veho
Veho
And checking your code is fine and good, but when there is more than one person working on a project? You won't be checking everyone's code. It's impossible. You define input/output parameters and if the server doesn't explode when your function calls their function, it's declared "working."
  • Like
Reactions: VinsCool and Sono
Jiehfeng
Jiehfeng
Yes that's correct, but I was more on the lines of scale. Even if you have tested everything properly while building, when things get big and everything is still connected, when you update something already existing it can change something somewhere else entirely and you wouldn't know about it until a tester comes in and checks the whole application.
  • Like
Reactions: VinsCool and Sono
Jiehfeng
Jiehfeng
As for functions working with a range on inputs, that doesn't cover all the types of bugs. The function may not break but the bug may very well be logic based elsewhere instead.
  • Like
Reactions: VinsCool and Sono
Sono
Sono
Not counting my code (because my bugs usually only consists of spelling mistakes), the biggest types of bug sources I find are either stupid logic types (most of the times it's either inverted, and/or an off-by-one bug), or people tend to use an obscure helper function with an obscure edge-case from some completely different class, and when that helper function gets "fixed", it magically breaks everything.
  • Like
Reactions: VinsCool and Jiehfeng
VinsCool
VinsCool
Ever since I've learned how to code with the minimum amount of skills needed to really understand what I am doing, I can totally relate.
I almost always find my own bugs entirely by accident, otherwise I wouldn't even know they existed until I did something unrelated and broke the entire program!
  • Like
Reactions: Jiehfeng and Sono
VinsCool
VinsCool
So yes, testers are absolutely important.
I also take time for test runs, which was invaluable for my projects.
If I did my functions and/or routines with the assumption they would always work, oh boy would I get a nice surprise at the time of testing it out! lol
  • Like
  • Haha
Reactions: Jiehfeng and Sono
VinsCool
VinsCool
I've also come to the realisation sometime a bug is here, and you know it's happening with a specific setup, but couldn't bother patching it just yet simply because you know it should not happen in the first place if you didn't actually try to trigger it, lol
  • Like
Reactions: Jiehfeng
General chit-chat
Help Users
    Bunjolio @ Bunjolio: +2