When you develop a big project like Show Hub, do you write a spec doc or product requirements doc outside of AI tools and then upload it? How do you start?

22:04to the number of people you're expecting or doesn't have the support, you know, role-based security or there's a whole bunch of things that I'd love to be able to make sure people have the right expectation or ability to say, oh yeah, I got to add that in and not just rely on AI to tell you, oh, don't forget to do this. Right. And so when you, I don't know how you

22:32start your projects but obviously conceptually you have an idea for a product you kind of know what it what you want it to be but I like for me and I've only done like a couple of I mean extremely rudimentary basic apps and I always started with like a simple a simple prompt but how do you start like a big project like show hub obviously many people in the community that watch

22:56this show know what it is but there there are many that don't so like when When you're going to develop a web-based application, do you write like a spec doc, a product requirements doc outside of the AI tool and then just upload and say, this is the product spec sheet? Or like, how are you doing that? You know, I use AI to do it.

23:22And one of the easiest ways is to say, hey, I want to build an app to do. And then it's a two or three sentence thing. and then you tell it, interview me for what you need to know to build the spec. Not to go ahead and do it, but to build the spec. Because often the spec can be huge, you know, 20 or more pages with lots of detail.

23:45And one of the things you want to be able to do, especially these days, is be able to break that up into phases. because once you start playing with it, you may have different ideas about the, you know, future or enhanced features. And so have it interview you and then have it create it and tell it. And I'm going to have this other AI bot build it out.

24:12And that piece is actually surprisingly interesting because it'll say, oh, if you're going to have ChatGPT build this, here's some things that, And it will disclose things that it thinks are deficiencies or extra things that it needs to know about. And that's really fascinating to see. But then so then I'll I'll have this doc, whether it's two or 10 pages, and then I'll give it to the bot that's going to be building it and say, look at this and tell me what's missing or confusing and give me how are you going to approach it?

24:50and then it goes ahead and does that. And I say, go ahead and whatnot. And it builds it. And usually I want the smallest, like show me enough so I can see that it's real, play with it because I'm human just like everybody else. My expectations of the future are going to be changed once I put my hands on it. So I want to see that MVP prototype,

25:18whatever, as quick as possible. And then I'll do a phase two or three that builds it out and adds all these things. And typically in that interview process in the beginning, I'll ask, have it make sure it talks about, so what's the end goal? Is this like a app that you're going to put in the app store? Is it something you're going to be in production with thousands of people using? Is it

25:43just for you and your friends, like make sure it covers some of those sort of things as well. Yeah. You know, I got to admit, I don't think I would have thought the fact that you asked it to interview you to, uh, provide what it needs to develop it. I probably would have wasted hours writing a document. I don't think I would have thought about that. That's, that's super clever.

26:07I'm going to, I'm writing this down right now. I'm going to remember this, uh, go ahead guy. Yeah, so I'm probably going to get some grief in the chat for this one, but this was in service to the community, so I came at it with a good heart. So whoever's going to give me grief, yeah, I'll deal with you later. But basically, I had a couple people message me over the last year or so asking, where's this episode? Where's that episode?