Belu y Vicky de "In the Making - Podcast " grabaron un podcast conmigo para compartir parte de los que venimos construyendo hace 2 años en Horizon.
Hablamos de IA, San Francisco, como es construir desde cero y muchisimo mas!
Espero que les sea util a todos los emprendedores/as!
Dejo el link aca:
https://t.co/r8WP4BFfS8
As engineering, product, design, DS, etc. melt into a new kind of role, I was reflecting on what roles might look like in the future. For example, when I look at the Claude Code team I see what I think is five archetypes:
1. Prototyper: comes up with brand new ideas; churns out many ideas, most of which don't ship
2. Builder: quickly turns a prototype/idea into production-grade product/infra
3. Sweeper: cleans up the UI, simplifies the code and system, unships, optimizes performance
4. Grower: takes a product that has been built and iterates on it to improve Product-Market Fit
5. Maintainer: owns a mature system to make it secure, reliable, fast, and efficient as it scales
Many people span across 2 roles, and sometimes 3 roles. I also notice that these roles are not really tied to job function -- eg. across Anthropic, some designers match category 1, some 2, some 3; same for engineers, PM, DS.
A healthy team needs a mix of these, depending on the product:
- A product that is new and pre-PMF needs people that are strong at 1+2+3
- A product that is growing and has found PMF needs 2+3+4 and some 5
- A product that has strong PMF needs 3+4+5 and some 2
Maybe product roles of the future will look more like this, and less like the domain-specific roles of today?
Introducing Cognee v1.0: a major breakthrough in agentic intelligence.
It is 145% better than Opus 4.8 and GPT 5.5 at long context memory retrieval.
Cognee allows a 100 BILLION token context window 100,000x more than Claude. It's:
- 6.9x cheaper than GPT 5.5 and Opus 4.8
- Cold starts in 350ms & searches in 260ms
Why this matters:
Today agents forget important context, redo tasks, waste tokens, and slow down as workflows get more complex.
Cognee solves this.
It’s not a place to build agents. It connects to the agents you’ve already built, across any platform, and makes them significantly cheaper, faster, and more accurate.
Here's how it works:
So the real question isn't "how do I automate this workflow."
It's "which of these steps should exist at all, and which should fire before anyone asks? 😄
🧵Hot take for anyone building enterprise AI:
Most "automation" still waits to be told what to do. A human, or now an agent, reacts to a trigger and walks the steps.
The endgame isn't faster reactions. It's a system that acts before the trigger exists. --->
The pattern: every step in a legacy process is a workaround for a human being slow, forgetful, or reactive.
Remove that and the steps don't get faster. They get deleted, and what's left runs ahead of demand instead of behind it.