Yet Another startup "discovers" formal development process can be quit useful.
Good thing it's not working on anything important or a lot of peoples cash could be seriously f**ked up.
IBM federal Systems developed the process to do this in the 1970's.
1)Do code audits which a)Record bugs but don't fix them on the fly and b)Find bugs, don't blame developers
2)Identify if there are bug "patterns" of error prone (or just wrong) code
3) Use those patterns to scan the whole code base for other examples and fix those before going back into retest
No "deep learning." No neural networks. Just small teams eyeballing the code and writing pattern recognition scripts fed from a code repository where all code changes were tracked by developer and date/time on a line by line basis. SoA in the mid 70's but today....
Of course that was for a code base in MB, when a 1 MHz 32bit processor with 1MB of RAM was screaming performance at a Rolls Royce cost.
You'd think in 2017 people could do a bit better, wouldn't you?
Yet with single processors several 1000x faster and memory several 1000x bigger, with potentially massive MIPS (GIPS?) available on demand, apparently not. :-( .