Ep 7: Pivot to the Conundrum Desk

0:09Welcome to Curiosity Builds by Hypandra.

0:09My name is Trevan Hauck and I will be your

0:11host and guide through this live

0:13learning in public experience that I am

0:17doing for my benefit and for yours. So

0:21today on this episode, I'm going to be

0:23working on this my Gabfest Ledgers

0:26project, which I got a new name, the

0:29conundrum.com. So that's the new name of

0:32this project, conundrum desk. It's still

0:33going to say Gabfest Ledger for now

0:35because that's the directory. I don't

0:36want to go through the headache. Maybe

0:38it's easy. I just don't want to go

0:40through whatever that is to change it

0:41right now. Um I know what it's called.

0:43So this is what it looks like. We're

0:45going to work a lot on cleaning this up.

0:47I hopefully will say what I'm doing well

0:49enough to convey what's happening, but

0:53there's a lot to do, so I'm going to be

0:55moving kind of fast for this episode.

0:58This is a really fun project for me. I'm

1:01going to the Slate Political Gabfest 20th

1:03anniversary, one of their 20th

1:05anniversary live shows in DC next week.

1:08and I was needing some inspiration to

1:11film videos and and practice my coding

1:14and my AI literacy skills, applying

1:18things that I'm trying to work out uh on

1:21a broader level for myself. And this

1:23seemed like a great way to do it. So, I

1:26am going to be cleaning a lot of this

1:27up, though. This got really busy. It was

1:29really fun to add all of these things to

1:31just to see what was possible. But now,

1:34I want to make it usable and not just so

1:36much. There's just so much going on. So,

1:38I think the goal is going to be make

1:41this not a page you have to scroll. Even

1:43though I like the scroll feel for like a

1:45newspaper, I want to take these

1:47different sections and just have them up

1:48here so then they slide through and

1:50rotate through. I also want it to like

1:53start with the conundrum desk. That

1:55needs to be the focus since that's the

1:56new uh name of the site. So, we're going

1:59to go in here. We're going to So, I've

2:01got my agent window over here. GPT 5.2

2:05Codex. set the planning mode ready to

2:07go. Over here, I've got our website, my

2:10website, the conundrum.com, ready to go.

2:13But we want to see the changes. So,

2:15we're going to launch the local preview.

2:17I'm going to go to my terminal. I'm

2:18going to type in bun dev. I probably

2:21should do a quick video kind of

2:23highlighting all of the shortcut

2:24commands and git commands that I know

2:26that are used in this a lot, just so

2:29people can see. We had an issue. Unable

2:32to acquire lock

2:41is in use port 32 instead. Let's see.

2:41Will this work?

2:43No.

2:45So, I think I need to

2:49Did I type in something wrong? Let's try

2:50it again. Let's kill the terminal.

2:53Actually, I have two terminals open.

2:56That could be why.

2:58I think I launched bun dev earlier just

3:00to make sure I had everything ready for

3:02people.

3:03And I need to do it again.

3:08There we go. So you can commandclick and

3:12open and it'll show the same thing that

3:15this is, right? But it will update with

3:18the changes and then also show errors

3:20and anything like that. We can also

3:22bring it up over here which I will do.

3:25You can go command shiftp on a Mac. Oh,

3:28but I need to copy the URL. Sorry.

3:31We want this URL.

3:33Command shiftp simple browser shell.

3:37Paste in your URL. It'll pull it right

3:39up here. Uh it's not a the greatest

3:41view, but you can see a little bit. Uh

3:43that way you don't have to keep toggling

3:45back and forth. I prefer this. I think

3:47this is a better preview. But this way

3:49there's something happening on screen so

3:51it's not so boring while we're doing

3:53stuff. Now I'm going to come over here

3:55and we're going to work up a plan. So

3:58when I am starting, I like to give as

4:02comprehensive

4:03a plan as I can with prompting at the

4:06start. Have it roll through everything

4:08it's going to do, ask me questions,

4:10double check it, add things, remove

4:12things, and then execute the plan. And

4:15from there, I usually don't plan

4:17further. I'd make small changes. But

4:19we'll see. There's a lot that's going to

4:21happen today on this. I think I also

4:24want this to go to the main

4:28um the main page because that's the

4:31changes we're going to have the most to

4:33begin with. So without further ado, I'm

4:36going to speak to text. Oh, someone

4:37asked me the other day what my speak

4:40software was. I use Whisper. It is this

4:44really cool

4:45speech-to-text

4:47AI enhanced software that allows you to

4:49choose the level of grammar like if you

4:53want informal or formal. It has a lot of

4:57features. It counts your words. It tells

4:59you how fast you're speaking. You can

5:01add spelling things. It's really cool.

5:03It does cost, but that's what I use

5:05because I don't like typing. So, we're

5:07going to get in here and give this a

5:08plan.

5:10All right. We have purchased a domain

5:13for this called the conundrum.com. So,

5:16we're shifting the focus of this website

5:18to be more on the conundrum. I do like a

5:23lot of the content and a lot of the

5:24features we have, but I want to focus

5:26the conundrum desk. So, when you arrive

5:29at conundrum.com,

5:32that's the first thing you see. All of

5:34the other things on here need to be

5:35rearranged around that. And I think it's

5:38too much going on on the landing page

5:40anyway. There's a lot of movement.

5:42There's a lot of scrolling. It's like a

5:44newspaper, which is cool. That was the

5:46first idea, but I don't want it to be so

5:48busy, and I don't want to get caught up

5:50in the minutia that I'm going to have to

5:53get caught up into solving little fixes

5:56for all of these little features. So,

5:58what I want to do is I want to clean

6:00this up. I want to land on the conundrum

6:03desk and then I want the four pill

6:06buttons that toggle through the

6:08different areas of the site. The meet

6:11the host, the browse the timeline, the

6:13visit the conundrum desk. I want those

6:16to take you to the section, but I want

6:19the sections to actually be static on

6:21that same landing page and then you're

6:24rotating through them. So they're going

6:26to the next part beneath it. And the

6:29conundrum desk is not its own page. It's

6:32just the desk that slides into view.

6:36With that, I also want to highlight the

6:40buttons that rotate a little more

6:43clearly. They're a little innocuous on

6:47the page with the color scheme they have

6:49right now. So, I think a little bit of a

6:50noticeable outline on the container

6:53would be good. I think that's plenty to

6:57get started.

6:58So, let's let's paste that in here.

7:07And I'm going to delete this last little

7:07part. So, yeah, I like to talk to my

7:10agent the way I talk to regular people.

7:13There are things I do specifically. I

7:14enunciate a little more because I am

7:16using speak to text. Also, if I remember

7:19and I try to intentionally remember what

7:22I've learned, I will add in certain

7:24things that make more sense or make

7:27things a little quicker. I might

7:29recommend a spacing number or I might

7:31ask it to double check linting on X, Y,

7:34and Z, things that I've learned. But you

7:37don't necessarily need to have that

7:39vocabulary, right? You might not have

7:42the word specifically, but you could

7:44have the understanding. So, if you're

7:46good at articulating and describing what

7:48you want, you can you can work through

7:50it. You could also spend time

7:54speaking or typing up what you'd like to

7:57see and then taking that and putting it

7:59right into the agent and seeing where it

8:01goes. If you are like me and you're kind

8:04of a little lazy, you want to be fast,

8:06you can just do the speak the text right

8:08in there. If I took a little more time

8:10and prompted myself to write it out

8:14first, I might tweak it more and make it

8:15a little more concise and maybe arrive

8:17quicker at where I want to be. But I

8:20like to make this fluid and more fun and

8:23more enjoyable. And this is this is kind

8:25of like my vibe. Um, if I was doing

8:27something more

8:31if I was doing something that had a

8:32deadline or was more professional in

8:36terms of, you know, showing a bunch of

8:37stakeholders or going into a

8:39presentation and I wanted something to

8:41be really, you know, slick and buttoned

8:43up, I would write it out and I'd be very

8:45very um detailed. But we're kind of just

8:48having fun here, so I want to keep it

8:50that way. So, which section should

8:52remain on the landing page besides the

8:54conundrum desk? keep all existing se

8:56sections but simplify their content

8:58layout something else. So I don't like

9:01that. So I want to keep all of those for

9:03now but I want them to be moved up to

9:07the top so they rotate through kind of

9:09like a carousel el

9:11but you're just sliding over to the next

9:13the next section.

9:16Okay. Now next question. For the four

9:18pillars, do you want a simple anchor

9:20scrolling between the sections or a

9:22carousel el tile? Hey, carousel el type panel

9:24wrap within the same page area. I'm a

9:26carousel el fan. Uh you might know this

9:29about me. I mean, this was my my uh my

9:35curiosity build created this little

9:38carousel el which I'm in love with. I some

9:40people might not like it, but this is so

9:42cool to me. And this is all all Trevan.

9:46So carousel el big fan. Let's give it a

9:49try.

9:51Now, it's going to go through and

9:52planning out its moves. It's going to

9:54read files, get context. It might even

9:57do a little search on the internet

9:58depending on what we're asking it to do.

10:00While it builds the plan, it will start

10:03to create a file that we'll be able to

10:04see over here. It'll kind of just open

10:06automatically and put it in a rich text.

10:08And all that means is it's more legible

10:11than just smaller, you know, terminal

10:13text. If you look at the way this text

10:15is written right now, this is basically

10:17rich text, right? It's formatted. It's

10:19it's contained. There's bolding. There's

10:21spacing, there's lists. This is just,

10:24you know, terminal stuff. It's just

10:26straight up. It's like kind of like text

10:27editor, just straight text. It's not as

10:30uh convenient to look at. Um, this

10:32thing's still going. Sometimes complex

10:35plans take a while, but that's good. We

10:38want it to be thinking. And then look,

10:39it will run into something and ask me

10:41another question. Should slash conundrum

10:43remain as a standalone page or should it

10:45be removed and redirected to the main

10:47landing page? Yeah, I think we need to

10:49redirect it. No standalone page.

10:53That's true because right now if you go

10:54to the web page uh and you click on it,

10:58the conundrum desk, see it's

10:59slash conundrum the front page just

11:01conundrum.com. Visit the conundrum desk.

11:04So we want it to just all be in one

11:06place. And look, here's that plan. So

11:09it's giving the context. The conundrum

11:11landing plan is what it named itself.

11:13It's showing the different text files

11:16that it's going to look at and read.

11:18It's showing a snippet of the code that

11:22it's going to impact and then it's going

11:24to show me the plan here. So, create a

11:26carousel el style container component. Add

11:28these things. Refactor the landing

11:30page. Improve visual emphasis of the

11:32pill container. That's the outlines I

11:34was talking about. Redirect the

11:35standalone conundrum page. Right? We

11:37want it to just all be on the front

11:38page. We don't need a redirect um or we

11:41don't need another page, right? And then

11:44a QA sweep. It added verify carousel el

11:47transitions. I am skeptical of its own

11:49QA. I I

11:5290% of the time and maybe it's the way

11:54I'm prompting. I don't think so. You

11:57need to do your own QA anyway, but 90%

12:00of the time you're going to catch a

12:02bunch of stuff. So, anywho great that

12:05it's doing this, not super confident in

12:07its ability. Implementation to-dos,

12:09create the landing carousel el, restructure

12:12the page, add the container outlines,

12:14and make sure this doesn't happen

12:16anymore. this little slash conundrum.

12:18It's giving the to-do list. If I wanted

12:20to add to-dos, I could. If I wanted to

12:23add another agent to work on this or

12:25something else, I could. That's going to

12:26spend more tokens. I also am not very

12:28experienced using multiple agents at the

12:30same time, so I'm kind of hesitant to do

12:32that. Once you have your plan out and

12:35you're happy with it, like I am, you

12:36just click the build button and it's off

12:38to the races. You can see what it's

12:40doing here. Sometimes sometimes it all

12:42happens at once, but we're going to just

12:46do some editing magic so you don't have

12:47to wait. And we'll come back when this

12:49is done doing its build.

12:53This

12:55is now where we're at.

12:58Too still too much. I'm trying to do too

13:01much. I want to just focus on the

13:03conundrum desk. This is supposed to be

13:04something cute and cool as a tribute. I

13:08you know I always get so many ideas and

13:11I want to keep doing things and you know

13:14strategic application is important you

13:17know not always using the tools you have

13:19to do everything that you can because

13:21you know sometimes it's not cool. It

13:25might look cool to do it in the moment

13:27but altogether it could be too much or

13:29just not intuitive and overwhelm the

13:32user or just turn them off from ever

13:33going back. Additionally,

13:37I prompted the AI to get rid of these

13:40sections a and put them kind of like on

13:43this carousel el thing where they slide

13:45through. I could have been a little more

13:47explicit. This is close to what I

13:49wanted. Also, if you noticed, I asked it

13:53to highlight these to make them more

13:55noticeable. It did, but then it didn't

13:57like space them correctly. So, as great

14:00as it is, like I couldn't write the code

14:02for all of this, it still needs a lot of

14:05shepherding. Um, and I could be doing a

14:08better job. So, I think what we're going

14:10to do is dial this back and just get rid

14:12of everything but the conundrum desk and

14:14just make that our main focus and see if

14:16we can get that really nice and snazzy.

14:18And if we have time, I might try to add

14:21like a ticker. I like this ticker. And I

14:23like these meet the host things. I think

14:24these are cool. you know, if they could

14:26you can click them and well, you used to

14:28be able to click them and they would pop

14:29out, but I don't know where John's

14:32going.

14:33So, you know, things to work on here.

14:37Uh, anyway, we're going to go back to

14:40Let's refresh this. John came back. Uh,

14:44yeah,

14:46I think we're trying to do too much. I

14:47just want to focus on the conundrum desk

14:49feature. So, we're going to dial this

14:51way back. Get rid of Oh, whoops.

14:57I

14:57not Korean.

14:59I think we're trying to do too much. I

15:01want to dial this back. I want to just

15:03focus on the conundrum desk. So, we're

15:04going to remove the other sections, the

15:06open the front page, meet the host,

15:08browse the timeline sections, and

15:12just have the conundrum desk be the main

15:15focus. I want to move the conundrum desk

15:18all the way to the top, right underneath

15:21where the navbar would be. I want to get

15:24rid of the conundrum desk, a desk for

15:27shaping question and arguing start the

15:29spark. That hero title, that hero text

15:32is redundant because it's already

15:34written on the actual desk. So, get rid

15:37of that. Get rid of the dine box. Move

15:41the whole conundrum desk up. And then

15:45get rid of the Gabfest Ledger title and

15:49just put underneath that special

15:5420th year tribute.

15:58Okay, let's see how that goes.

16:02Oops. Get rid of that little part. All

16:05right, I This is a lot. So, I actually

16:09think I am going to switch this over to

16:10plan so that way we can double check it

16:12again and we'll send this off when it's

16:14got his plan written up. Um, we'll come

16:17back and read it together and see uh

16:21what it's going to do. Oh, yeah. First

16:22it it will ask me some questions. So,

16:25exact text should replace the current

16:26kicker now special anniversary issue.

16:29Use special 20th year tribute. Yep. For

16:33now. Should I remove the carousel el pill

16:35navigation entirely? Uh yeah, remove the

16:38carousel on all the other sections, right?

16:42Okay, creating a plan. Oh, it's a fast

16:44plan. Not as complicated as before.

16:48Um eliminating things for the most part.

16:52So yeah, these are the places it's going

16:54to look. These are the step-by-step

16:56plans. Remove, move, update. Optional

17:01cleanup. If the landing page carousel el is

17:02no longer used anywhere, remove it.

17:03Import usage page text. That's true. We

17:05do want to clean up unused code. It's

17:07good to save features that we like

17:08somewhere, but we don't want to ship

17:10things that have a bunch of unused

17:13text and files on them. It makes them

17:15heavy. It makes uh things take longer.

17:16And it can also cause confusion later if

17:18the LLM's see that something might be

17:21there and it's named something similar

17:23or the same thing that we're doing, but

17:24it's not the same thing. It can get

17:26confused. Trust me, you need to be

17:28specific. I am still trying to dig

17:32myself out of naming too many files.

17:34Hypandra. So,

17:37we are looking at this. Simplify landing

17:39page. Remove redundant hero text. Update

17:41the hero kicker. Yeah, give it a go.

17:44Give it a go. We'll see. This might be

17:47kind of quick, but if it's not, I will

17:50fade to black for a second and come back

17:51so you can uh see it faster than uh it's

17:55going. Still pretty fast though.

17:59Still pretty fast. I kind of think this

18:01will be

18:03just a minute or two doing stuff.

18:08Yeah. Yeah.

18:21Okay.

18:21There we go. This is cleaner, right?

18:25This is cleaner.

18:27So, it's going to finish its plan. The

18:31last things that it'll do is uh linting

18:34errors, changing any um spacing or copy.

18:4020th year tribute.

18:43Yeah, we have to figure out the content

18:45better. I'm not too worried about the

18:47the content, the by lines or the text. I

18:50can work on that later. It's the layout

18:54I need the AI for. Right. So,

18:58Great. If you want to remove the kick

19:00line completely so the desk is first

19:01visual, say the word and I'll do it.

19:03Yeah, I think that's fine right now. Um,

19:06okay. So, I don't like

19:10what's I mean, I like this, but I I want

19:13to get more specific on what I want to

19:15do. So, I want to generate a conundrum.

19:18So, what is it doing right now? Let's

19:19see. So, it just generates this. How

19:21much privacy would you trade for civic

19:24trust and institutions?

19:26I'm wondering where it got that from.

19:27Context note. So, it's just having this

19:30all these little pieces here, but I

19:32don't think they actually work together

19:33or make any sense, right? Um, let's see

19:37if I Delightfully absurd. Will this

19:39work?

19:41If a filibuster could only be performed

19:43in interpretive dance, what changes?

19:46Okay, I do like that I put that in

19:48there. Um,

19:52that's great. I'm surprised it worked.

19:54trivial.

19:56If potholes were a ballot question, how

19:58would campaigns look? So, I think we can

20:00add a few more things over here. These

20:03build tools, I'm not as impressed with

20:07them for this feature, for this kind of

20:10thing. So, I don't know if we'll even

20:12need this. I think we'll just need the

20:13tone, the generator conundrum,

20:18maybe custom refinement. It would also

20:20be cool if you know you could save ones

20:23that you generated. That'll be kind of

20:26complicated though. Um, okay. So, why

20:31it's interesting it pushes beyond the

20:33headline and ask where legitimacy comes

20:34from.

20:37Yes, sure. Is that always going to say

20:39that there? No. Sometimes the LLM. So in

20:42full transparency when I did this

20:44originally I went through a really

20:46complex prompt with claude code just

20:49over in claude and then used that prompt

20:51to give to Codex to build everything

20:54out. I was super verbose and very

20:57detailed. I explained the conundrum desk

21:02but I did not give it content. So almost

21:06all of this content

21:09is LLM's filling it in and assuming. So

21:14I want to one say that out loud so you

21:16know that a lot of the stuff that's

21:18coming up here it's creating. I need to

21:20go through and double check. Even if you

21:22ask it not to. Well, if you ask it not

21:25to, hopefully it won't, but if you don't

21:27say anything, it a lot of times will

21:28just be like, "Ah, we could do this

21:30here. We want this here. We want this

21:31here." Um, I like how this is showing

21:33recent. I'm wondering if recent is shown

21:37for everyone that comes here or if it's

21:39just um cached to your to your um

21:44computer. I'm going to ask that

21:46question. So, we can ask change your

21:49agent to ask

21:52on the recently generated conundrums

21:54that appear on the conundrum desk. Are

21:56those just for the local cash or will

22:01everybody who goes to the website see

22:03what came up recently.

22:16So this is nice because it's going to

22:16read what it does and then explain to me

22:18hopefully what is uh happening. So that

22:21way I have a better understanding of the

22:23interface and the UX experience. Yeah,

22:25the local it's local to each visitor I

22:27would assume, right?

22:29Yeah, if you want recent to be global

22:31shared, you need P to persist history

22:33server side and read it into the

22:36component. I can outline the approach if

22:37you want.

22:39You know, would be cool

22:41if recent ones were generated and then

22:47if you liked it, you could give it a

22:50thumbs up. And then we have like a

22:52ranker over here for conundrums.

22:55And then people can just keep generating

22:57them.

22:59And uh or maybe they can generate them

23:01or they can put their own in. And then

23:04the recent ones are over here. People

23:06can read them and click them. It'd be

23:11also cool if they could answer them. Now

23:13we're getting way over over uh committed

23:16to ideas here. But I think this where

23:19you can vote and keep it. I think that's

23:22something we want to keep. So what we're

23:25going to do is probably get rid of the

23:28build tools, get rid of the custom

23:30refined, keep the tone, maybe add a few

23:32more tone options, get rid of the

23:36context note and the seed sparks and

23:38this why it's interesting thing.

23:40And then I want to add a enter your own

23:44conundrum option.

23:47Okay. So, let's give that prompt a try.

23:59Whoops. I have my other setting on my

23:59speak to text in Korean. And for some

24:00reason, if I hit the button and I don't

24:02say anything, it just throws in a random

24:04Korean sentence. I think it just panics.

24:06It wants to answer.

24:14Okay. I do want recent to be global

24:14shared. I want it to persist server side

24:17like you're saying, but I also want it

24:20to be interactable. I think it'd be an

24:22interesting experience if users can come

24:25in and not only generate a conundrum,

24:29but they can enter their own idea for a

24:31conundrum. And then whatever's

24:33generated, whatever's entered appears in

24:35a recent

24:38um list like it is there. And those

24:41recent ones can be thumbsed up or

24:44thumbsed down.

24:47And we can see how they rank. And those

24:49conundrums that rise to the top will get

24:51more and those that don't will go down.

24:54I'm wondering if we can arrange a system

24:57like that.

25:00In addition, I would like to remove the

25:02build tools and the custom refine

25:07and

25:08the context

25:11note

25:13for now. Actually, no. I want to keep

25:16the context note, but I want to move the

25:18context note over to the desk tools

25:20because we should be using the context

25:22to inform the conundrum generation. It's

25:25kind of strange that it's sitting under

25:27the conundrum desk. I'm not even sure if

25:30that interacts correctly.

25:37I'm actually going to leave

25:37this pasted in here so I can double

25:40check that. If potholes were a ballot

25:42question, how would campaigns look? So,

25:45context note, make it specific to a city

25:47or a small detail. Make it specific to

25:49Seattle.

25:50But then, how do I enter this, right? Do

25:52I hit enter? No. Do I hit generate? Does

25:54that No, I don't think Yeah, it's not

25:58connected here. It would be cool if it

26:00was connected, but it's not. So,

26:03we're going to go back over here. I'm

26:05going to change this. So,

26:13stop there.

26:13Oops.

26:16Delete that.

26:26It looks like the context note doesn't

26:26really have any interaction. You can

26:28type into it, but I'm not sure what it's

26:29affecting. It would be great if we could

26:32move the context note over to the desk

26:34tools and then when a conundrum is being

26:37generated, it will not only look at the

26:40tone, it'll look at the context. So if

26:43someone wants a conundrum about Seattle

26:45or Diplo or

26:48you know

26:51beneficial nutrients,

26:54they can put that in there and it'll be

26:56part of the conundrum.

26:59If you don't know how to build this, we

27:01do have tools in the Hypandra repository

27:07that should help with these items.

27:11They're already created. So, let's

27:13double check you have access there. And

27:15if you do, I want to take some of the

27:18tools and apply them here. You don't

27:21need to build them from whole cloth.

27:28Now, I'm changing this to plan. The

27:28reason I said this, okay, and I probably

27:32could have said this a little better,

27:34right? We have tools in the Hypandra

27:36repository that should help with these

27:38items. Let me refine this a little bit.

27:54For another project, Hypandra, we've

27:54created a

27:56set of tools that allow you to modify

27:59questions and input and generate and

28:01that's where these are being drawn from.

28:04Do not try to build them yourself.

28:09if you don't have to. We should grab the

28:13code and context from Hypandra if

28:15possible. We will be making adjustments

28:18though. So, I'm going to see if it's

28:20able to do that. Um,

28:24let me know if you're able to access

28:26that repo or if there's something we

28:29need to do to make sure you can pull in

28:30any components we would like. I also

28:32want to make sure things are kept clean.

28:35I don't want to mix two repos or sets of

28:39files.

28:44All right, we'll see. That's something

28:44new. I've not tried that before. Um when

28:47I built out the original Gabfest ledger,

28:50I did it on the Hypandra repo and then

28:52we moved it over. Uh where should the

28:55where should we persist global recent

28:57conundrums and votes? Supabase.

29:00I think Supabase because that's what we

29:02have. How should voting work per

29:04visitor? Anonymous one vote require

29:07login allow unlimited voting.

29:11Anonymous

29:13people can

29:16thumbs up as many as they want, but you

29:20can only thumbs up a entry one time or

29:24thumbs down one time.

29:32Can I access Hypandra repo from this

29:32workspace path or URL?

29:35Yeah, I think I can get that for him or

29:38her or whoever this is working with me

29:41here. Uh, give me a second. I'm going to

29:43grab that file off my desktop here.

29:54Okay.

29:54Where is that folder?

30:01Okay. there

30:01and should be

30:04should be this.

30:16Yeah.

30:16Okay. Hopefully I'm copying this

30:18correctly.

30:33Now it's going to go through and do two

30:33things at once

30:39parallel exploration.

30:39I'm probably going to fade to black for

30:42a minute here uh while it's building a

30:44new plan and then uh come back to you

30:47when we are live.

30:51All right, I'm back. It's got a few more

30:52questions for me. Uh, how should this

30:55the shared list be ordered by default?

30:58Most recent first, vote shown, but no

31:00reordering, top scores first, hybrid.

31:04So, I think I want to have a most recent

31:07conundrum

31:09kind of

31:12scroll bar on the side where people can

31:15see the most recent ones and they keep

31:17appearing, but you can kind of scroll

31:19down through and see them if you would

31:22like. Maybe you can click on it actually

31:25and it will take you to all of the

31:27recent ones. And then on the conundrum

31:30desk page,

31:32I think on the other side of the desk,

31:34so we've got the desk tool side, we've

31:36got the conundrum desk side. Let's

31:40create a side on the right that's the

31:42same size as the desk tools. So, we're

31:46expanding the desk out a little bit. And

31:48over there, we're going to put the

31:50leaderboard,

31:52the most popular conundrums, and they're

31:54going to be standing there, and people

31:55can vote on them while they're while

31:57they're on that leaderboard as well. So,

31:59basically, you've got to make it to the

32:02leaderboard from the

32:06recent entries and then you got to stay

32:08on there because people can vote it down

32:09or vote it up.

32:17Okay. When a user submits their own

32:17conundrum, should we store only the

32:19question task or generate and store

32:22rationale, tone, context, metadata?

32:25I

32:27think we want it to be displayed.

32:30So

32:32I think

32:34yeah, we want the question, we want the

32:37tone, the context

32:44because we want everybody to see it. So,

32:44I think when a conundrum is generated, I

32:48would like to be able to click on it and

32:52then you just kind of see the guts where

32:54it's like, oh, it was used with X, Y,

32:57and Z. And if it was user submitted,

33:00then

33:02whatever they put in there as well. But

33:05maybe they didn't put anything. So, we

33:07can list that. You know, maybe you just

33:08had a conundrum in your head like, would

33:11you rather be a tree or a fish and you

33:13didn't have to have any adjustments and

33:15went straight in there.

33:23Okay, big answers.

33:23Big answers. So, while it's working, um

33:26I'm going to go work on something else

33:28and we'll come back and and see what

33:29what it did.

33:50Okay, more questions.

33:50So, when someone clicks the recent

33:52sidebar, where should the full recent

33:54list live? A section below the desk on

33:56the same page. Scroll to it. A model

33:59drawer overlay on the same page. Ooh, I

34:02like that.

34:07We'll see what it comes up with with

34:07that. Interesting.

34:16Mhm. Yeah, planning mode is great. Uh

34:16especially if you are really intentional

34:18with how you prompt, whether it's

34:21speaking, you know, fluently like me or

34:24or writing out like very specific

34:26prompts that look almost like code.

34:29Putting it in planning mode is great

34:31because it will interview you a little

34:33bit. It still needs so much help, but

34:36it's it's better in a lot of ways than

34:38just putting what I put in there and

34:40have the agent have at it. It ask me

34:42some context so it could get some

34:44context and make mistakes less, spend

34:47tokens less. So context

34:52plan, add persistent layer from

34:54Supabase. Create API routes for feed

34:56and voting. Update conundrum generation,

34:59Refactor the conundrum desk UI, wire

35:02the data fetching and implementation.

35:05This is probably one of the heaviest

35:08things I've tried to do on my own. We

35:10will see how this goes. Uh after this,

35:14I'm going to commit it and call it uh

35:18and call it a little bit, I think. But

35:20we'll see.

35:26And I mean, after this gets cleaned up,

35:26after we kind of arrive as close as we

35:28can with this, I I think we'll uh we'll

35:31commit this

35:32and see what it looks like live.

35:36So, we'll be back when this is

35:40this is up and running.

35:43Actually, I think because this is going

35:44to take so long, we will yeah, we will

35:47uh we'll come back on the next episode

35:50to show you uh where we're at.

35:54Groovy, groovy. So,

35:57just to

35:58leave you with a conclusion here, we are

36:01revamping the entire Gabfest Ledger

36:04into the conundrum desk. And we gave it

36:07a really long prompt. It asked me a

36:09bunch of questions and it's working on

36:11this plan. So, we'll see how it does on

36:14the next episode of Curiosity Builds.

36:17Stay curious and don't forget to commit.