> the signal-to-noise ratio in AI-drafted comms is brutal
This is also the case for AI generated projects btw, the backend projects that I’ve been looking at often contains reimplementations of common functionality that already exists elsewhere, such as in-memory LRU caches when they should have just used a library.
Bad example, you really should just write caching yourself. It’s far too little code to pull in a dependency and if you write it yourself in every project that needs it then you will get good at it, so cache invalidation bugs won’t be an issue.