Discussion about this post

User's avatar
Peter Bell's avatar

This is what prompted my whole approach. I was stuck in analysis paralysis for a really long time, and I also noticed many tools were hard to integrate with AI and also came to the realization that I had no idea how quickly any of the tools I used might become uneconomic or obsolete. So I stopped.

Then I just said - what's the minimum that I need as a technical solo chef to build what I want. I needed a foundation model (I use claude - but don't tie myself to claude specific features so I can do council of elders, pick the right lab/model for the job and have business continuity if one foundation lab falters. I needed transcriptions (I picked granola as non-intrusive and good enough - better now it has an API and raised another round). I needed a place to store the git repo with all the prompts and skills and slow changing shared context - GitHub for now - we'll see if they keep having 500 errors. I needed emails and calendar (a google for work account - one for me, one for each primary agent) and I needed a relational database as my system of record for tasks, research, content, contacts, companies, pipelines and everything else. For now I'm on supabase, but (other than blog storage) I'm not using any deep supabase features so I could port to any other hosted postgres in a day.

That's my stack. No shiny object syndrome. If I see something cool I send it to my agents to review - not to see whether I should trial it, but to ask them if there are any patterns they could extract for my own orchestration harness.

You need to be technical and you need to have good technical judgement and a solid sense of good practices for reliable distributed systems. But if you are, it's not that hard.

For me it's been transformative.

2 more comments...

No posts

Ready for more?