I am interested in systems that really try to tackle the multiplayer, multi-channel, central mind concept—like how a human would act. Especially the idea that long-running tasks get to receive relevant pieces of data right when they arrive and that messages can relate to multiple workloads at the same time. Is any such system being developed at the moment ?
I have two kids. They are very very different in their needs, sleep patterns, self security, and have been since their first days. Parenting is mostly hard for anyone getting serious about it, but i can vary tremendously from you kid personnality, the support system you have, etc... I suspect some parents (usually fathers) don't know it because they do not put in the works (and then give some advices on boundaries). Still, some have "easy" kids in the sense that they are not demanding a lot from the parent, and that can be fine or the sign of a troubled personnality. I completely understand the author here, as this has been also my experience - parenting is unbeleivably hard but _also_ beautiful and _also_ an experience that should change you to the core and make you grow. To me, however hard it can be, it beats the alternative. But I could unserstand that only once I've been through abandonning my former self govern by individualist values and goals to become a new person taking care of someone else, however hard and painful it might have been.
Same pain point on (2). So I had codex build me a small macos sytem tray app that lets me comment on anything i can select on my screen with the source app and metadata plus my comments. Once commenting is done i can click a button to coppy all comment to the chat input, and voila ! But really something i hope that gets integrated into the codex app itself. The present way they made it is not super helpful.
Having implemented a skill to connect teams to our admin system, we ended up recording it as a Mcp. the Mcp exposes only doc grep and api calls so it's completely useless in itself, but the main reason to go this route was distribution. Non technical teams want a UI where to add a url then everything just works and oauth is guided. Mcp permits that in Claude or chatgpt.
Also the calling of the Mcp is nicer in the chat UI, clearer for users.
I feel that a lot in my side projects: maybe one should keep the half-baked AI repo for oneself and rather share what the experiment, the thesis, and the learning from the building are. No one cares much about the (un)finished product, as it can be replicated better in most cases with a couple hours' work of claude coding.
For instance, I really liked how Karpathy shared a high-level idea on the LLM-based wiki. It was sadly followed by a long tail of no-one-cares-about "Here is my LLM wiki product" posts pointing to the generic LLM-generated landing page.
A bit tangential to the article themes, but I feel in some workplaces that engineering velocity has gone up while product cycles and agile processes have stayed the same. People end up churning tickets faster and working less, while general productivity has not changed.
Of course these are specific workplaces designed around moving tickets on a board, not high-agentic, fast-moving startups or independent projects—but they might represent a lot of the developer workforce.
I also know this is not everyone's experience and probably a rare favorable outcome of productivity gain captured by a worker that is not and won't stay the norm.
My team is asking the same. We are using jj with great success but tools like auto claude are designed around git and git worktrees. It's a shame - at least with git backend we can sort of make things work together.
