Once that pattern clicked, I started finding uses for Kody everywhere. Things that used to mean another little service, script, credential, or webhook became capabilities any of my agents could use. That’s really why I keep recommending Kody. It removes a bunch of boring glue work and makes it much easier to use different agents without rebuilding your world around each one.

deleting the product it's funny how you can sometimes tell if a team culture is dysfunctional just by looking at how their app is laid out. behind every feature, or tab in a sidebar likely lies a PM or someone responsible for an OKR. the problem is when individual performance is measured by these metrics. it becomes the singular focus of the responsible person to make those numbers look good, since it determines whether they get rewarded or axed, even if it comes at the detriment of the overall quality of the product. this is why you mostly see features get added, but rarely removed. if you own a feature, then it being removed feels like an aura loss. this is even worse in the agentic era when the cost to add features has become so low. you can simply will a new feature into existence overnight and add another tab. but users will notice that you ship your org chart. teams that make people play silly games under the guise of performance management rarely build great products. to build a great product you need to first fix your culture

Actually @AlemTuzlak just TanStack AI-pilled me - it's *insanely* good. I can't wait to dive in there

i feel like people do not grok how important celld is. it's scalable applications of arbitrary complexity. the only dependency is s3. once you see it, you'll realize there's no point to traditional javascript runtimes in serving applications - only for build processes (eg bundling) and scripting. the networking and scaleability are deeply rooted not only in the distributed runtime (celld), but in the programming model itself (largely kenton's design) I wasn't quite sure when I started celld how well this could be made to work, but we've been running it in bigger capacities and getting user reports over the last months. Actually handles load surprisingly well. (any experience in the comments to share?) because the programming model does not expose the underlying linux system, you can actually think of celld as a distributed operating system - running in user space of linux. it only runs one program / doesn't support multi-tenant, but it has system services like an operating system. it's all about networking - i like to think of it as the practical modern version of plan9 or even erlang beam.