Yeah, Ken’s lost it. It’s too bad, too; he used to go around saying “Hi, my name’s Ken, and my job … is just Requests.” However, Ken is actually a medium-talent hack who isn’t interested in putting the work, but in appropriating the work of others and passing it off as his own.

Ken’s goal with all of the snowy blog posts is to obscure and rewrite history. See, previously, on Lobsters, we learned from another Python community member that Ken converted some $30k USD of donations from 2018-2019. He said so himself:

Because [reasons], the fundraising funds were allocated to myself, to reimburse myself for all the time and energy I’m putting into Requests III, which I want to make a really great product.

Ken also tried to take over multiple community projects, including by vendoring their code and insisting that he was licensed to do it, putting his name on forks of Somebody Else’s Repo, and falsely positioning himself as endorsed by Python Software Foundation.

So, now a half-decade later, it’s time to try to change history for Ken. Previously, on Lobsters, we analyzed his attempt to reframe the whole incident in terms of burnout provoking a bipolar psychosis. I think that the most revealing part of this, assuming that his candor survived Claude’s extrusion process, is that he doesn’t actually deny his psychotic delusions; he merely implies that they no longer hold today. This doesn’t really accord with how psychoses are treated; it doesn’t sound like he’s built up a library of tells and hints which he can use to steer his thinking. (As the reader surely knows, Claude isn’t gonna help with this.) I think that he was much more revealing a decade ago with his retrospective on his first stay in a psychiatric ward:

I went through many stages of identity conflict at this stage as well — I realized that I wanted to leave the hospital, and not stay there forever (as I originally wanted). I felt like I was in a puzzle, and one way of getting out was to become a doctor! So, I started walking up to the doctor (and all other levels of staff) and acted like a coworker, helping them do their job. At one point, I asked one of the nurses for a Direct Deposit Form (after seeing another patient with one), believing that was the key to establishing my employment. I was keen to inform them about my understanding of HIPPA compliance and the hospital’s migration from an AS400 to a newer technology stack (EPIC).

Is this why he joined the Python community and tried to work on upstream and core stuff? A sort of Frank Abagnale adventure where he’s treated like a genuine authority with skills and knowledge? Note that this was two years before the aforementioned conversion of funds. It’s okay, though, because Ken blamed this all on mental illness. Specifically, he blamed the woman he was dating for provoking his previously-undiagnosed mental illness and starting a yearlong (!!‽) manic episode:

Around the same time, right after having gone to my first Kundalini Yoga class, I ended up meeting (and, falling in love with) a mesmerizing woman of mysticism that tenderly guided me off-the-deep-end with this style of thinking: numerology, synchronicity, Reiki, manifestation, the Mayan calendar, tarot, crystals, &c. My symptoms slowly got much worse. We shared a very deep and special bond. I heavily admired her, and felt I had much to learn from my newfound companion. We ended up spending nearly every day together, going on dates, making love, taking trips all over the world, getting matching tattoos, performing thrill-seeking stunts, and attending shamanistic ceremonies together. We had an incredible time (the best year of my life), but there was a lot of unhealthy and certainly uncharacteristic behavior for me. Over the course of the manic year I spent with her, my delusional worldview (and hallucinations) had grown significantly worse, which lead to the absurd themes of thinking featured in the above event.

At least he’s not a fascist.

On a personal note, in Numpy as Synth Engine, Ken released some slow inaccurate code for audio synthesis, generated for him by Claude. As a musician, I know that we can do better, so previously, on Lobsters, I explained how to actually make nice-sounding sawtooths and Hammond-style organs, including links to working Python code. Again, I could just call Ken a hack, but I think it’s interesting how he doesn’t aurally perceive the clear issues in the audio output; in a certain sense, he’s a producer of music but not a consumer of music. (Readers who are musicians will confirm that the typical working musician listens to more music than they produce!)

I appreciate the emphasis on conviviality or human centric design. But boy I want to nitpick on the following:

when we collaborate with AI systems, we might be interfacing with the archetypal patterns that have guided human wisdom throughout history. This makes programming with AI a form of accessing collective spiritual wisdom rather than just advanced tooling.

I agree with the first half, that yes, you are engaging with archetypal patterns that is often present in human wisdom but that is where it stops. There is no guarantee the LLM has selected the appropriate pattern for your use case. There is no wisdom from the LLM because there is no conviction from its choices. The LLM, at best, is a superstitious machine that sees that X pattern worked in a situation with similar signifiers. Wisdom is understanding which signifiers are of consequence given your context, which requires being able to ignore/forget irrelevant context - something an LLM is terrible at doing as evident by all the “context engineering” tools that exist. It feels like a chicken and egg problem where in order for the LLM to “get right” what is the appropriate context it must first have the appropriate context.