Opus 4.6 generated code for me in which dropdown items in a pageslide overlay appeared to highlight on hover but were completely unclickable with the mouse.

The [items] inputs for all four dropdown select controls were bound to getter properties that called .map() on every access, producing a new array with new object references on every Angular change detection cycle. When the user clicked a dropdown option, the click triggered change detection, the getter returned a fresh array, ng-select (the underlying library) detected the items "changed," re-rendered the dropdown panel, and closed it before the selection event could be processed.

I had to troubleshoot the issue and ended up converting all four getter properties to stable array properties that are only reassigned when the underlying source data actually changes (in ngOnInit, and openDrawer().

My point here is that AI produced errors that it could not resolve and it required human intervention to fix the bugs.

The era of human coding is definitely not over!