jihad ↑
@jihad
this is a really cool idea, BUT... for every "superbuilder" a team has focused on build agents and streamlining team ops with LLMs... you'll also need a "context designer" or "librarian" making sure that the underlying data and information architecture is sound enough to get the most out of these tools tools are everywhere; software is easy to build but using LLMs at scale makes it infinitely more difficult to maintain coherence and consistency across internal context and external narratives without someone focused on that full-time, your team's AI empire is a house of cards https://x.com/chintanturakhia/status/1915866734437056911
7 replies
1 recast
10 reactions
jihad ↑
@jihad
that said, if i were a young hacker with deep AI tooling knowledge, i'd be all over this role
1 reply
0 recast
2 reactions
Chris Carella
@ccarella.eth
new teams starting today will have such a huge advantage here.
2 replies
0 recast
2 reactions
derek
@derek
and youd have to 2x-4x this lol
2 replies
0 recast
1 reaction
Kapaskie
@kapaskie
Solid point. LLMs are powerful, but without strong data architecture and someone constantly curating context, all that potential can easily get lost in translation. Having a "context designer" seems like the missing link to avoid chaos as AI scales.
0 reply
0 recast
1 reaction
Koolkheart
@koolkheart.eth
Absolutely nailed it. Most orgs are underestimating how fragile AI-assisted workflows become without strong context stewards. The future org chart includes a Chief Librarian
0 reply
0 recast
1 reaction
Jason
@jachian
In a few years it’ll look like the equivalent to migrating from mainframes to the cloud. Not one company I’ve heard of that managed such migration fully
0 reply
0 recast
0 reaction
Garrett
@garrett
tastemakers 🤝 superbuilders
0 reply
0 recast
0 reaction