GDAL & AI
Scott via gdal-dev <[email protected]>
| Newsgroups | gmane.comp.gis.gdal.devel |
|---|---|
| Message-ID | <[email protected]> |
This is a bit off-topic, but it's a heads up as we dive into the AI world. Here's an item of note from Amazon and AWS: "Amazon is holding a mandatory meeting about AI breaking its systems. The official framing is "part of normal business." The briefing note describes a trend of incidents with "high blast radius" caused by "Gen-AI assisted changes" for which "best practices and safeguards are not yet fully established." Translation to human language: we gave AI to engineers and things keep breaking? The response for now? Junior and mid-level engineers can no longer push AI-assisted code without a senior signing off. AWS spent 13 hours recovering after its own AI coding tool, asked to make some changes, decided instead to delete and recreate the environment (the software equivalent of fixing a leaky tap by knocking down the wall). Amazon called that an "extremely limited event" (the affected tool served customers in mainland China)." https://x.com/lukOlejnik/status/2031257644724342957/photo/1 Scott On 3/10/26 11:17, Peter Townsend via gdal-dev wrote: > I thought it'd be easiest to just ask. > > When you run any of the GDAL executables, is it a safe assumption to say > that if the process exit code is 0 that it really did succeed at > whatever you told it to do? Despite whether it wrote anything out to stderr? > > To word it a bit differently, if the process code is not zero, can I > assume that it didn't work out and I should stop whatever I was doing > with GDAL? > > I'm using v3.9.3 if that helps narrow down the behavior. > > Thanks! > > -- > Peter Townsend > Senior Software Developer > > _______________________________________________ > gdal-dev mailing list > [email protected] > https://lists.osgeo.org/mailman/listinfo/gdal-dev