i see, but my statement does not become false because of it. his agent pushes several commits an hour in a continuous loop, meaning this respected developer is not involved in the process at all.
I briefly worked with him personally. He is 1. a perfectionist and 2. equipped with the intellectual and programming firepower to not get stuck in the resulting paralysis that a lot of people get stuck in but blast through tasks that should be impossible to do at all, let alone with a high degree of quality, successfully, through sheer intellectual firepower. The end result is that he is well known for already having not just one incredible Haskell library, but a number of them.
I can promise you he will not produce and release "slop". He would be an order of magnitude more offended at the idea than you are, I'd imagine.
In the original commenter's defense, I _did_ let the agents I have working on this get a more than a bit test harness crazy back when I was able to use GHC itself as a behavioral oracle. That worked fine through the initial build out, but then it rushed ahead with a broken CI due to misalignment in priorities, and then kept piling fixtures on top of fixtures and didn't properly track their cross-dependencies. My work on this in the last 48 hours has mostly been about getting that part under control and stable across my target platforms so I have better bedrock to build atop.
therepanic · · focus · HN ↗
i am not sure anyone actually understands what is going on under the hood of the project. looks like average slop.
>> Exactly a week ago (as a joke), I started writing THC,
you? i hope you have read at least something of what your agent wrote about the project.
vintermann · · focus · HN ↗
therepanic · · focus · HN ↗
jerf · · focus · HN ↗
I can promise you he will not produce and release "slop". He would be an order of magnitude more offended at the idea than you are, I'd imagine.
edwardkmett · · focus · HN ↗
In the original commenter's defense, I _did_ let the agents I have working on this get a more than a bit test harness crazy back when I was able to use GHC itself as a behavioral oracle. That worked fine through the initial build out, but then it rushed ahead with a broken CI due to misalignment in priorities, and then kept piling fixtures on top of fixtures and didn't properly track their cross-dependencies. My work on this in the last 48 hours has mostly been about getting that part under control and stable across my target platforms so I have better bedrock to build atop.