hi i'm garvin (realized i never really intro'd myself here)
i recently joined @tomoji_ai as a founding engineer working with my best friends @elijahmuraoka_@mikelong107@benanchetaiii
some facts about me:
> grew up in hong kong 🇭🇰
> was a photographer for @TEDTalks in high school
> built 2 startups (https://t.co/3fdbBUJxCO and https://t.co/hB139GMdEC) all the way to $0 ARR
> was the 5th engineer at a fintech startup that grew to $5M ARR
> shipped an AI privacy code analyzer at @amazon then left 😎
> living in LA, looking forward to moving to SF early next year
if you're into startups, photography, building, or whatever, let's connect!
i might've discovered the DREAM coding setup 😮
orchestrator: grok @bot
coding agents: @claudeai
terminal: rex by @superlogical
cloud VM: @instabox_sh
what would you change about this setup?
and let me know if i should do a full breakdown on this
my current Grok @bot team setup:
garvy: my right hand man. mostly anything non-engineering related, i talk to garvy
head of eng: i talk to this bot for everything engineering-related. it helps me spin up and manage cloud agents. if it's a big/complex task, i talk to the cloud agent directly
repo managers: i work on multiple repos so having one orchestrator bot would flood the chat. to prevent this, i have a manager bot for each repo that reports to head of eng
nightly audit engineer: cleans up the codebase at 4am everyday
nightly coverage engineer: increase test coverage of the codebase at 4am everyday
jenny, head of ops (inspired by @lingxi): have 1:1 meetings with my engineering bots where she'll learn about the blockers from each bot and update the engineering playbook accordingly