Haven't seen yet how AI overlords would have solved the #crowdstrike issue.
:blobpeek:
Haven't seen yet how AI overlords would have solved the #crowdstrike issue.
:blobpeek:
@vascorsd Maybe they caused it. Not our overlords but our underlings. It's yet another source of complexity and the company has been bragging about it.
@vascorsd It looks like the "AI" missing might be a static code analysis tool in their build pipeline.
@hypolite Yes. I misread it the first time, overcharitably, and thought he was mocking the poster he was quoting ... but the poster was himself.
Wildeboer removed his post anyway, so the link between this thread and the racist thread has been severed.
@hypolite I don't know if the thread was about the correct stacktrace or not, but I saw from the bluescreens posted that the error was a segfault.
If your company's software segfaults in today's world, and you're using a legacy language where it's easy to get segfaults, that's a choice your company made. That was the point of the thread before the author subverted his own point and made it about conspiracy theory racism.
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.