The career, the industry, the stepping back, and the selective return
Overview
Kenneth's relationship with technology runs the full arc from building foundational infrastructure to stepping back from it — for his health, and for the deeper inquiry the stepping-back made room for. Technology here is treated as three things at once: a tool that can serve human thought, a trap that can consume it, and a canvas for the kind of design work that Python turned out to be an unusually good medium for. The domain holds both halves of that story, the making and the questioning of the making.
The Arc
The builder years, roughly 2007 to 2017, are the ones the wider world knows. Kenneth created requests, pipenv, and a cluster of ecosystem tools in Python, held the informal title of "Python Overlord" at Heroku, worked in Developer Relations at DigitalOcean, served on the Python Software Foundation Board, gave conference keynotes, and for a stretch stood as the single most-followed Python developer on GitHub. The influence was real, and it was built almost entirely out of small tools made to feel obvious.
The transition, from about 2017 to 2020, is quieter and harder. Mental health challenges made the pace of active maintenance untenable; the major projects were handed to community governance rather than clung to, and the energy that had gone into shipping libraries went into writing and creative work instead. Stepping back was not defeat so much as a change of medium.
After 2020 Kenneth spent several years mostly as a critic of the thing he helped build. The Algorithm Eats essay series turns systemic attention onto engagement optimization, making technology a subject of analysis rather than only a thing to create. simplemind marked a selective re-engagement, and RetroVault made the builder unmistakably active again: a native Mac application, originally called OpenVault, built around a self-hosted RomM library, controller-first play, and save preservation. The full chronology lives in the Career Timeline, and the Python legacy itself in Python Libraries. Digital Legacy asks what all of it amounts to once the author steps away—the code that keeps deciding, the archive as insurance, the pattern that outlives the person.
The Industry Problem
The disengagement has a diagnosis behind it. What the industry became, in Kenneth's telling, is a machine that mistakes motion for progress:
"There's a kind of stagnancy in the tech space where we think we're innovating all the time but internet apps and websites etc are either focused on exploiting human psychology or just optimizing for getting cash out of your wallet."
"I miss the 2010s internet."
The nostalgia is not merely sentimental. It points at a period when tools were still made to be used rather than to capture — before the dominant business model of software became attention extraction. The Algorithm Eats series documents that shift systematically, tracing how engagement optimization consumes the very human flourishing it claims to serve.
The "For Humans" Response
Against that stands "For Humans", the counter-philosophy Kenneth practiced in code before he ever argued it in prose. Technology should serve human cognition rather than exploit it — reduce cognitive load rather than manufacture it, empower rather than addict, and treat developer experience as an ethical stance and not a marketing one. It is the same conviction that animated requests, generalized: if a tool is hard to use, the tool is wrong, not the person. Extraction and service are two different answers to the same design question, and "For Humans" is the insistence that the answer is a choice.
Current Stance
The present position is not anti-technology but selective. Yes to RetroVault, simplemind, music made with PyTheory, AI collaboration, and consciousness research; no to the industry's pace, its optimization culture, and its extraction economics. What remains constant across the builder and the critic is the underlying question—what technology is for, who it actually serves, and what it costs the people who use it.
Related
- Career Timeline — Full arc
- RetroVault — The current native Mac project
- Python Libraries — The legacy
- Digital Legacy — What survives the author
- For Humans — The philosophy
- Algorithm Eats — The critique
- Health — Why stepping back
- AI Research — Selective re-engagement
- Python — The language
- Open Source — The ecosystem
- Hacker Ethic — The tradition's original creed
- Conference Speaking — The public platform
- Design — The designer's eye
- Ethics — Technology as ethical choice
"HTTP libraries should be for humans, not machines."