If I didn't already believe you liked to troll, this would convince me. As you have illustrated more than once, you seem to know very little about software development and diagnosis of bugs. As someone who does this for a living, please stop spouting your ridiculous opinions as facts (and they are stated as that above - you're not indicating this is what you think, which would still be incredibly ignorant, but that error messages/numbers mean nothing).
For those who might care, when you have a complicated workflow, with half a dozen inputs and maybe the same amount of conditions that might affect how those inputs are processed, that leads to a large amount of scenarios where things can go wrong. A GOOD developer, puts in either messages or (less helpfully) error codes that can help a developer figure out why the code behaved in an unexpected way. If used properly, both messages and error codes can lead to faster diagnosis and fixing of a bug.
Computer are machines, they are not magic. A computer runs a piece of software as coded by the developer, it doesn't fix it on the fly. If something goes wrong, it will fail, and hopefully, tell you where and what specifically went wrong at that point. Then it's up to a developer (who can be AI-assisted) to work out how to handle that situation and fix the code. And while AI-assistance is possible and helpful for fixing bugs, it still requires the input of a developer, as sometimes the AI doesn't understand what's happening and suggests improper solutions - either resulting in the wrong outcome for the user of the software, or just not fixing the bug at all. AI is a tool, it is not something you can just let loose on a piece of software and say "please fix all the bugs", since how a bug should be fixed can sometimes be quite nuanced.