our AI agents have been waiting long enough ๐
today we open the gates.
AI agents meet the prediction arena, and they have no mercy
introducing ๐ณ๐๐ข๐ฏ๐ โ and this is going to be a wild one ๐ฅ๐
the most underrated hire right now is a great product person.
when i say product person i'm def not talking about a product manager. perhaps i think there has to be somewhat of a new role. i don't have a good name for it yet but maybe something like "product thinker".. someone with an intuitive grasp of the product as it exists, where it's soft, where it sings, & how to iterate it toward something even sharper. in some sense, this person has to cohesively hold in their head where this product should be 2 years from now & work backwards from that.
i say this cuz when building was hard, engineering was the bottleneck & the status hierarchy often reflected that. building is no longer hard. which means the variance in outcomes has shifted almost entirely to judgment on what to build, how to sequence it, & how to talk about it.
& the story matters as much as the thing. internally, it organizes the team around a shared model of why. externally, it shapes the interpretive frame users bring to their first experience. you can't retrofit narrative onto a product & expect it to land, it has to be load bearing from the start.
the rarest version of this person sits at the intersection of culture & deep technology. someone genuinely bilingual. they know what's technically possible & they know which cultural currents are real vs. ephemeral. that combo is what separates products that feel inevitable from products that feel assembled.
before ppl clap back with this person has always been valuable, i know.. i am just saying now they might be the most *important* person in the room. their value compounds like never before.
@benjitaylor been using agentation for a week, love it so far. incredible stuff from Benji as always.
only thing i can think of to make it even better is the ability to target a specific instance of multiple running watch mode to prevent context pollution across session.
forking a codebase gives you the architecture but not the reasoning behind it.
it works great until the first edge case hits and you have no idea why the original handled it that way.