24
Comments (9)
sorted by:
You're viewing a single comment thread. View all comments, or full comment thread.
0
Wyopepe 0 points ago +1 / -1

Bugs and glitches are a living part of software.

I’ve worked with very large enterprise codebases and you cannot escape it.

It’s simply a problem of imperfect people using abstractions to solve business problems.

That being said, this isn’t a hard problem to build software for. Auditing should be there as well as logs recording the software and user actions, by whom, etc. QA should have ferreted out most issues, especially at this level.

It’s hard to speculate, because maybe the codebase is garbage, and there is little insight into the actions of the software itself. Without it being open source, we are just guessing how this could happen.

2
deleted 2 points ago +2 / -0
1
deleted 1 point ago +1 / -0
1
Wyopepe 1 point ago +1 / -0

Any system that has any significant amount of code or complexity will contain bugs or defects.

Without seeing the code base itself, we can’t really speculate as to what took place.

I’ve seen code where there are no unit tests, integration tests, etc. rarely is there 100% coverage.

All I am saying is, at the end of the day a bug cannot be ruled out, and it very well could be a feature. Without the code, we are just guessing.

I will say, that with all the other coincidences, I can see your viewpoint and it has merit.

1
deleted 1 point ago +1 / -0
1
deleted 1 point ago +1 / -0
1
Wyopepe 1 point ago +1 / -0

The code is the source of truth.

It doesn’t lie.

That’s my main point.

In general I agree with you. This isn’t a difficult problem to code for and in a perfect world, these issues would be accounted for. Depends on the codebase and the vendor who wrote it.

1
deleted 1 point ago +1 / -0