AI makes you boring

>and the flurry of domain experts responding like "wtf, no one needs this"

People have been saying this about Show HNs for time eternal. There have been an insane number of poorly thought out, poorly considered, often Get-Rich-Quick type of creations, long before AI. Things where the submitter clearly doesn't understand the industry they're targeting, doesn't provide any sort of solution, etc. Really strange if people actually think this is a new phenomenon.

Indeed, a recent video that I rather loved touches on this - https://www.youtube.com/watch?v=Km2bn0HvUwg

Its subject is "Everything was Already AI", the point being that everyone is quantizing and simplifying and reflecting everyone else and the consensus, in such a fashion that people acting like AI ruined everything...yeah, it was already ruined. We already have furry artists drawing furry art just like countless other furry artists, declaring it an outrage that someone used AI to draw furry art, and so on. As the video covers, the whole idea of genres is basically people just cloning each other.

Be right back, going to put on a cowboy hat and denim and sing in a drawl about pickups and exes.

The content of the article seems OK, but I'm still going to generally disagree with it. Maybe my take is just confirming the thesis, but I don't find the larger things I do with AI to be borifying (yes I just invented that word).

I've been ramping my use since the start of this month, and have already made serious progress on a number of projects, many of which have been on ice for years, and have also built out a stable of supporting tools. And I've found it generally exhilarating; making good progress where there was none before is pretty heady.

One of the more memorable experiences I have was a problem that I had to deal with for years, had thought hard about, and then in the end Claude resolved it cleanly with about 1/3 a screen of code (would share the link, but there's no "share" in the mobile app):

=============== I often use [snoop](https://github.com/alexmojaki/snoop) because I like the features and output formatting, but it doesn't support async. I have found [ASnooper](https://github.com/LL-Ling/ASnooper), but it only supports async. I'd like to add ASnooper's async feature to snoop.

I'm thinking of creating a project that imports both, and patches the relevant parts of snoop with the async functionality from ASnooper. I have some notes from looking into the snoop code: - A `ConfiguredTracer` object is exposed in `builtins` (configuration.py, line 142). - Whenever the `ConfiguredTracer` object is called with an async function, it raises (tracer.py, line 166). - The trace event is passed to a formatter, and then a writer (tracer.py, line 280-281). ... and in the ASnooper code: - An `ASnooper` object is exposed (__init__.py). - Whenever the `ASnooper` object is called on an async function, it creates formatter and writer objects (core.py, line 69-75). The approach I'm considering is to wrap `ConfiguredTracer.__call__` with a method that delegates async function tracing to `ASnooper`, and replace the `OutputFormatter` and `OutputWriter` classes with versions that delegate to `snoop`'s implementation. I've prepared a repo for the solution: """ . ./README.md ./pyproject.toml ./tests ./tests/__init__.py ./src ./src/async_patched_snoop ./src/async_patched_snoop/__init__.py """

I've also extracted excerpts from both projects, as unified diff contexts (attached). Any issues, questions or suggestions? Or a better approach that doesn't involve forking the targeted projects? ===============

I prompted Claude with this along with a file containing the diffs (constructed with the help of another prompted tool), Claude informed me of the issues in my approach and suggested a couple alternate solutions, I selected the one 1 preferred, Claude asked for some more context and then did the implementation, and now I have async support in snoop. Probably took me over an hour to construct that initial prompt, and under 5 minutes of conversion to completed solution. I really don't think that that's boring.

I've had to dig into node modules to try to debug code from a closed source library that we depended on.

I'd much rather wade through AI slop than minified code, which may have previously been AI slop.

Opposite of my experience, I think AI gives tools to expand thinking and creativity significantly, leading to much more interesting results

AI is excellent for helping to write things like tech specs, procedures and manuals.