Comment Re:Documentation (Score 1) 57
not to review techical documentation to identify design issues
But this is exactly where AI can actually be useful — so long as you don't depend on it to identify all of the design issues. It can review mountains of information and find things in it you might not have caught. You just can't assume that it will catch everything it "should" — that is, what it should be capable of catching is not necessarily what you are capable of catching.
Yes, and it requires a multi-layerd approach to how they system raises issues. One simple prompt pass is not enough, however a multi-tiered approach can increase teh success rate. It'll never catch everything, and neither will a human, the tool is merely a way to remove much of the grunt work searching though documents so teh analyst can focus on what is important and make it easier ot find where things are referenced.
Meanwhile, that periodic report has requirements, so you're going to have to ask it to write the report, then to review it to see if it met the requirements, then to review its own statements about whether it successfully met each requirement, because it won't do any of that sanity checking without being told to do so.
There are two different types of reports to develop - one that validates meeting requirements and one that is merely reporting results or periodic required reporting. The former is challenging, the later a lot less so, and reducing the time spent on the later frees up time for the former. Of course, many such reports do not need AI since they merely compile data, and that is easy to program in any of a number of tools. AI just adds hype and market cap...