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

🎉 Just announced -- Superbuilder role 🎉

We are launching a new role on @base engineering today -- it's called Superbuilder.

Become Superbuilder #1 and apply. Read more in 🧵 https://t.co/GDn5LQU0da

Chintan Turakhia🛡️

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

seeker /native /believein /bedrock 🇵🇸

that said, if i were a young hacker with deep AI tooling knowledge, i'd be all over this role

if the persona is a young hacker then agreed it's a great role.

but in order to 100x developer productivity in a large org like Base, you should have some context on how orgs like that work.

reading the job description, it seems like a highly cross-functional role that will largely be operating in isolation. again, that's typically a experienced person.