Many engineers know the feeling. A lost battle with a circuit where everything goes wrong not because it was badly engineered, but because the silicone has bugs in it that were only discovered after the board has been prototyped and failed to work as expected. It ends up wasting time and money, causes delays in time to market and might make a client doubt whether you didn’t put the bugs in that silicon yourself.  Even though there might be silicon bugs that could have escaped testing, many would be documented by the manufacturer (and hopefully fixed or include a workaround) in the Errata. The Errata seems for many engineers to be an elusive animal, a document no one reads until after something has gone wrong(some of them do after all seem to be as long as the datasheet itself). That should not be so! Make sure you read the errata and ensure that nothing you’re trying to achieve with the device is affected by bugs (or that the workaround is acceptable). Moreover, make sure that the silicon version of the devices you obtain from your supplier are either the latest or don’t contain the bugs in early revisions. When in doubt, contact the manufacturer.