> It really does cut time by 10s of percent.
I used it for about a month. It gave me a few false positive that really burned me - it's not worth the risk. Maybe future versions would be better.
back
2 comments
I've gotten plenty of false positives, but the mistakes turn up in testing and are pretty easy to spot when reviewing the code. Anything more subtle is likely to have been missed when written by hand anyway.
What happened to burn you so badly?
What're the examples of false positives?
Agreed it gets things wrong very frequently. But I've found it much easier to use its suggestion as another "input" to writing code.