Team training. We are, I think, on part four of this series working through our agency dashboard. We have a
Small team. I think we're under seven people and we've been building a dashboard
Vibe coding a dashboard or at least building it in this new way. We've did some shaping stuff
We went through and did like a task grid
I think last week and so I'll just tend to take a second here and show you guys a
Little bit about a little bit what I've worked on since we talked and
All in I think I've maybe spent three hours since last maybe four hours since we
Since we last talked here, and I'm gonna try to find
Here it is our dashboard. So we share this real quick and then I'll jump in with the team
Hopefully this will show so we again in recap. We did a whole like sticky note thing
We put that into digitized notes here, we've slowly just been like coming up with things to
Spend our time on as a as like with teams. We framed up some different projects here
We talked about our process. You guys go to the old videos if you're want to catch up on how we got this far
And it's good. We just kind of drew what was already happening already a lot of times when you're framing stuff
It's just taking time to like shape the now process once you like figure out how it's actually working now
Then the future state actually becomes very clear
So but a lot of times you just want to jump to like well
It should work like this and we just go ahead and brain like put this together
Of how it should work and then we don't but this is actually good and therapeutic to go through
How it's currently working and then we come with a few versions of how it could work
And not to say like the thing we've built yet is working this way, but it helped get our ideas on paper
And so I'll show you a couple new features here, let me share this other screen make sure I've got
This okay, and I'm literally deploying a version while we're speaking. So I'll see if this has got the latest code here
so a couple things that we did we showed you the task grid last time in
the monster app I
Idea that there's something that Ryan had created and so
One of the features we actually threw in here was to make our own task grid
And so this little thing that you see here is actually inside our dashboard now
And so every project will will have that we have like a little home screen so you can actually see
This one. I think this is a one week. Yeah get a one week project here and
I'm gonna zoom this all in since my screens a little big here and
This is the view that you would see inside the dashboard for a project
You can actually see the toggle try time here. You can see like I spent an hour this morning on it
So maybe we're in like 15. I didn't spend a few hours yesterday doing a bunch of stuff, but
15 hours all in got a lot done for that. So all of this has been built in this view here
We had a client project view or we could view projects by status
And we have a clients by month so we can kind of see when their stuff is scheduled with a few little tasks
Client security here. Just making sure we match the right user to the right client
We added this task grid was a little fun bonus
We added the team view so that team view like the team can actually go in and see their
Schedule and we also have like their financials and stuff so we can see earnings
And my screen just stopped sharing. So this is great. Let's try that again
Okay, cool, we'll see if that happens again
and then
So we did a lot and this is only 15 hours in to this product. So every one of these slices here is pretty much
Like one work session. I would say I had this little command palette today
And we can now like search for a client like I can type Anovo and hit enter takes me to
You know what's going on with with that client. I can easily search for a project like new view
Hit enter jump to this project again. So these are these are super helpful when we're
Just getting in between a lot of different projects. Also a great shortcut if you're building an app
That you don't have all the navigation just figured out just quite yet
You don't have all the navigation just figured out just quite yet
This command palette is genius because you can just get around to the thing you want to get to really quick
Um, so I don't have like a good search functionality
Uh, if you were looking for a project, there's not like a list of projects somewhere to go and find projects
I'd have to go to
a dashboard here
You know the things were assigned to me or if I pick someone
I see these projects are assigned to me or maybe I could go to the client
And then I could look up what that client was doing and then click into a project that way
but it's kind of
hard to get there so
Now, just with the search, we can just type something like request pool.
We can type in, you know, a client's name like that, jump straight to it.
Um, so it's kind of a lazy way to do navigation.
Um, but also, uh, I think most of us are using this for, at least for me, like I
use it for notion and, um, uh, Slack all the time.
So this is a great little hack.
I think, uh, I think it took me like an hour to put that in.
So also something we should definitely add to other apps.
Um, I'll show you something as well.
Um, this task grid thing is a great little exercise in general
when we're building projects.
So, uh, let me go back to the new view here.
Um, we were using like a link to Ryan's tool.
Um, and this is kind of nice to have it right here though.
So you can add a slice and I can just type something like, um, maybe there's
a new view, uh, for like, maybe I'll do like a, a team member, like, uh, by
status view, we have a client by status view, maybe we'll do the same for the
client here, I mean, for the team members and you can just type things.
So as soon as I hit enter here, it kind of just jumps to the next thing.
And I can say, you know, set up Kanban, uh, whatever, add to like a horizontal
nav, I don't know, set up.
Um, I don't know what else we need, you know, parameters and we don't, I'm not
going to build it on this call, but you guys can see what happens is like, I get
my little total here, which is really nice.
Um, I can of course drag this box to the front here just to, for, since everything
else is done and kind of keep it up here at the top, um, I can quickly check these
things off, um, if needed, I can even drag something from one item to another.
Uh, which is helpful.
And you can see like, once we check all the items off, this kind of fades away.
So you don't really have to pay attention to that.
Um, and then there's other things here we can mark unknowns here.
So if there was a section of the project and there were still things that were
unknown, it's a nice little flag there.
We may add some more flags as we go, but these are just, it's basically like a
whiteboard with just you sketching out things.
Um, when I'm building stuff, I actually typically have a piece of paper in front
of me and I literally just have like a heading and a couple of bullet points,
like checklist underneath, a heading, a couple of bullet points.
Um, and so this is a great way to recreate that.
And I think there's a lot of cool things we can do with this.
Since each task is now in here, we can potentially have, um, even assigning
like tasks, if two people were working on something together, we could assign
a slice to each other, things like that.
So that can all happen.
Um, obviously you can mark as completed.
Um, I can, uh, I think you can delete something.
You can also duplicate it.
So if we had two very similar slices, but slightly different, like I have
this project view by status for clients, but now I have like a project
view for status by for the team member.
Maybe I can duplicate this whole slice and just tweak a few tasks.
Um, so hopefully that becomes really useful.
We can still obviously jump back to Notion really quick because most things,
if we want to change the status of a project, we still go to Notion.
That's kind of our source.
And then that will sync back.
Um, and we have a two way link now as well.
So you can click on the dashboard there, jump back to this page and so forth.
So, um, let me bring everybody back on here.
Um, if you guys want to be on screen, you can, you can turn your
camera off if you don't want to.
Um, and I think I lost my screen share again.
Out of here, but yeah, I'd love to hear any, um, thoughts you guys have.
I think we may have maxed out the number of people on this, uh, on this invite.
So, uh, let's see.
Um, yeah.
Any thoughts?
You guys are welcome.
This is just open chat.
Um, so far, let me pull this.
Hey, it's command palette live, or is it just on your live?
I'm trying to, what's the keyboard shortcut again?
Command K.
Okay.
That's how we're going to live beta test this right now.
Did you have to, uh, bake in the command palette or was that something
that just kind of, you had already Bruce?
Um, no, it was pretty, um, quick.
I, I'll, uh, I wonder, yes, if I can go, um, let me grab, I wonder if I
can show that history real quick.
I was going to say, I mean, I'm not a developer, so I'm sure
developers can say we love command.
Yeah.
This is the process here.
Um, let me get it.
Uh, I don't want to just be having to hunt and click on things.
Yes.
Um, this is kind of a nice, I forgot how we can get like the full history here.
Anyway.
Um, I'm trying to show the plan for this.
I wonder if we can show me the original plan.
Uh, I wonder if it'll do that.
It's like not showing the history, but I'll, um, I'll see if I can go here.
It is maybe it was an MD file.
somewhere, saved somewhere deep.
And I'll see if I can find it.
Oh, here it is.
So this was the I just went into plan mode again with Claude.
And we came up with this little plan here, pretty simple.
I think the prompt I said, I just spoke it out.
So I used Talktastic as well.
You should all use some sort of dictation AI tool
at this point, save yourselves.
And it's very helpful and therapeutic, again,
to talk the thing out versus having
to sit there and type it, try to be perfect.
But this was pretty simple.
We had some routes.
We went back and forth a little bit
because it wanted to use all the keeps.
Claude loves just writing and reading things
right out of Superbase.
It's super lazy.
And so you have to tell it, hey, you
see how every other database call is using an API?
How about you do that?
You just keep following the instructions I give you.
Same thing here.
And I specifically asked for it somewhere.
I didn't want to use any kind of third-party thing.
I think another app, we tried to implement this somewhere,
and we used Algolia.
And I can't remember what that, maybe that was for Tribe.
But it was pretty simple.
And I was able to search for keywords, a title of a project,
a client.
And then I committed that.
And so we went through and like, ha-ha.
I don't know if that got shown, but that was my E&D file.
May have to delete this recording.
So if we go in here, basically went through like,
I think we did, yeah.
So there was one commit where we just gave the initial commit,
like one component for the command palette,
updated this, updated the route here.
And then I added search clients.
And I added some status colors.
And then I added the ability to search team members
if you're an admin.
So those were like four kind of commits that
made up that little feature.
So I think that was the whole process for building that.
I don't know if that was the question you're asking,
but that was sort of the process of building that.
I tried it out.
I have a suggestion, a little improvement.
Yes.
In the command palette, like Command-Enter
should open in a new tab instead
of like replacing the page.
So if you type like Anovo and then, oh, Command-Enter.
Yes, that's a great idea.
We will add it to the list right now.
I kind of want to be able to also get directly to the grid,
I mean, the task grid.
But maybe we should be like Command-Enter opens new.
Great, I love it.
I'm going to delete this.
Yeah, any other thoughts?
It's interesting because getting it live and then just
playing with it, you kind of notice things.
It forces you, like I open Notion.
Let's grab Notion real quick.
When you hit Command-K here, it actually shows all the results.
And then as you type something, it tries to find it.
I also noticed I use the, so if I hit Command-Spacebar,
I use Alfred on my computer.
So I actually prefer this view.
Sorry, I got like two.
So if I hit Command-Spacebar, it just has just the input field.
And then as I type something like Notion,
it then search for Notion.
Then as the results get fewer and fewer,
it shortens the box below it.
But what was happening initially on this version
was it was opening tall.
And then as the results got, the input field
would get more centered.
And it would jump around.
These are huge issues.
These are the real problems.
It's just like these little things you notice.
But just building it and making it work,
and then just kind of playing with it a little bit,
I was spending more of my time on the product, almost the UX
or the UI, more of the UX.
Because like, hey, I want it to be super fast.
And now that Notion says that, and I want to pull this up,
obviously, that Command-Enter makes tons of sense.
Tons of sense, we should definitely have that.
I think you can do that in Notion.
It's funny, because these are things that you just do.
You don't even think about it.
Yeah, I think if I go like this and I hit Command-Enter,
yeah, you're totally right.
That's how it works.
So that's the same for the idea as well,
like VS Code or Cursor.
VS Code, does that?
Yeah.
Yeah, if you were to open, yeah.
Yeah, you're right.
Exactly.
One question.
The test grid is being stored on.
super base yeah uh but yeah and like on the super base side we have like a let's say copy
of all the data or the for instance like the notion data we are getting only for notion and
toggle we are getting from toggle and we are not like storing it on our super base it's
it's a start okay so probably that's interesting yeah projects are actually synced um uh so there's
a copy of the project and then there's a project in notion and same with clients okay so uh when
the the magic piece here is like when you're in the um project connections here there's a little
uh edge function that runs every hour i believe it is and then there's a second one that so one
sucks in all the notion all the notion projects comments and clients and there's a bit of logic
that it um just looks for new stuff so it's not bringing every single new project in it
has a way of tracking if something's synced not or not and it tracks it to the id and so then
if you were to change like the name of a client or you were to change the name of a project
it will just update um there and so we've one of the features here which if you're building this
from scratch and especially if you're vibe coding this you would just say like oh i want a place to
like change the title of the of the project that would be a mistake um because now you've created
just infinitely more work for yourself to now change the project name here but also be able
to do it from notion and then which one like wins if they're like out of sync um so we made a very
simple thing like we're already in notion if i want to change this or you know write other things
or do stuff down here uh i'm just going to do it in notion because i'm already here that's why i've
got links everywhere to open it in notion um so that was like a little hack um but actually
simplifies the product quite quite a lot um instead of having like a two-way sync it's
just a one-way um but then we do have a toggle um time yeah because yep because uh that's very
interesting because then we are very close to being able to like uh basically have uh a
cursor or cloud agent to run tasks directly from the task grid and being able to update it and like
so then we can kind of do the half wagon thing like that loop thing we can basically do hey you
need to loop uh in this task grid until everything is completed and until all these requirements are
met and then you'll be just like um overseeing the loop itself and and like reviewing the output
based on what's getting in and out of the task unit so it's very very very interesting and like
we can do like even stuff like for for make this process better on the first moment we could like
each box when we are going to like send this to to note to the agent we could have a specific
context that we attach it for each box for instance if i know that the task grid will touch
on this this and these files i already attach this to the box of the task grid as context for that
execution this way when i send it for for the model model to execute it you'll be able to to
retrieve the data properly now that's yeah and there's there's like layers of how uh that's yes
definitely um a dumb simple way to do this in like 15 minutes would be something where you could
like one of the options here would be like copy for ai and it just sucks up like all the tasks
it knows what thing got finished it goes you know what the whatever and you just paste it into your
uh that's really good you can like copy for the whole like task grid and it's like mark it down
with the like uh check it yeah just mark it down but i got another like very simple request that
would be powerful it like ability to put like links in the like task grid uh like item you know
like a to-do item could be like a markdown ish like in the back end it's like markdown
and it could be a link you know if you like select some text and paste a url then it becomes like a
link does that make sense uh so you wouldn't be able to like hyperlink to it no no no i mean like
let's say you have like one uh you have like one to do their command plus enter opens new tab let's
say you like highlight the opens new tab yeah and then you like paste a link that should be like
become like the you know blue underlined and oh like if i was typing here and i highlighted that
i could hyperlink
link something yeah like that becomes like a link
interesting and then you could uh so if i had like
multiple words i could link this one yeah exactly so that way like when
you're doing the um what do you call it but then it can't
you're not a sudden deal now you've got like a whole rich text editor
yeah it could be like scoped down to just like make it mark down you know
what's the use case are you wanting to like the use case is that like janata
said like um like when you're passing it to ai
um two use cases one is that i want to connect
to uh like a notion task where i'm taking like
a lot of notes about a specific like to do
another uh use case is that um that feature that janata was just
talking about like copy all then it would copy like with
the markdown so that way the ai knows that this task
has like a link to a page or something text
better yeah i almost wonder if it's almost at the task level or it's at the
slice level interesting yeah like we could like have
a to the option to like double click at
task and maybe add context for that specific task yeah
that's for something i okay so this this is this is good i mean
i think um uh there's a couple use cases for this
i mean an easy thing to be like hey i need to pull all this in
generally it is kind of uh diverting quite quite rapidly into something
totally different which is and i almost think it's a different
thing like almost like an ai like i just duplicate this whole thing
and then it's just for like building the context
for the project perfect yeah because yeah
command enter opens new tab like there isn't any way
uh uh and sorry this is on one it's in the
wrong box what did i do here this should be over here
um so part one i was like why does that even okay
so that that should be over there um like i guess it could infer this but a
lot of these things has like search client search projects like i
know what it is um but the llm is not going to know what
it is based on these like um these little like tasks are going to
be so this is almost like a scratch pad um
i understand your point but we are getting close like
i know but it won't be able to know exactly but
it can read the context of the project so if you already have like
a users or a table that it's the same name it will probably assume that you
are talking about it and usually it's going to be right
but but i understand like uh it's it's it there is
it's it's complicated to like how much are we like but but i really like this
idea of like having the context builder and and like having this
separated step because it's actually is like when we
finish the task grid we kind of finish the
planning phase in some sense the shaping phase we finish
with the the task grid so it will initiate the build phase
i think it's like uh there's a you build it out here
and again this is if only there was a way to uh breadboard this
and uh see this flow because we're kind of not listen going out of our uh but
this is this is good i almost wonder if there's a way you can
like click on this and say like um like prep for llm or
something and it goes into a different mode how about i have a suggestion
llm like you just add like like a copy icon next to like the top level like
task grid the even the higher one oh i'm here
yeah it is and then when you click that it just
like copies as markdown you know like with each
of all of this yeah all and then you can like delete
if you want well if it knows the status like it
sees this and it knows it's done it can obviously skip that and go to the next
or just copy like everything and like as markdown you know like a
checked box yeah uh one one interesting thing that we
could do like uh it's similar to what uh hippo prompt
to do uh can you see my screen i'd have to hang on
one second let me okay i got it just wanted to share this
we have a few things being shared the same okay let's see
did that work i'm not sure
i'm gonna stop sharing my we may be maxing out but i think you can have like
eight people
i can i can just screenshot it it's because it's it's on my side let me
hang on there you go we should be good whoa
okay
we can do like the hula thing like
I think we broke a restream, okay.
I will send a screenshot on the team channel.
Sure.
Because it's like just an image is like, because Hippoprompt has this, this idea of the context
builder.
So you basically, you write some instructions and you can select specific files and you
can then run a discovery mode that will basically scan your page and generate a plan for you
using less tokens than usually the model uses to generate a plan.
So it's maybe something along those lines, because it would be very powerful to like
having a play mode that knows exactly the context of the code base.
Like having the plan agent to know exactly the context of the code base that you're talking
about.
So, but yeah, very interesting.
The future looks bright.
Yeah.
Let's see if this will, sorry guys, I messed up everything.
That's exciting.
Gennady should be like giving like more, like should be given like a training, you
know, with like planning better, like you're using plan more better and all that stuff
feels like you're on the cutting edge.
It could be as simple as this, where we like click here, we have copy markdown and then
it just pastes into like this.
Sorry.
And I think everybody's faces are over there.
On top.
Yeah.
And something like that.
I mean, yeah, these are like quick things we can start to add.
I think in this mode, since this is a great place to experiment, like let's just put things
in here, like have the same little copy icon up here and just grab everything, all the
slices at once.
Because you could say something like, Hey, I want to work on this project.
Here's the status or something.
And then of course the other thing would be really easy to do would be to have some sort
of MCP.
So we could go like use the Anovo dashboard MCP and just have it like look at what's going
on in the, like just pull those things dynamically.
So yeah, you could do that.
I think that would be cool because to me, the reason we're doing this, the task grid
is to actually separate shippable pieces or things that are somewhat separated and kind
of pull the project into small pieces.
So that's kind of the value of the task grid.
We stole from Ryan.
So I want to keep that.
I do think there's a value in having a human separate things versus the LLM.
Although it would be cool if you were working on a new feature and you wanted to sit in
your cloud code in the terminal and actually have it generate the first draft of it, maybe
based on various screenshots or whatever.
Then you could kind of reorder it.
I don't know.
There's probably some like back and forth there where you can use it, but there's a
huge value.
I think something simple where we could like copy it and manually bring it forward and
back I think is great.
I think I'm kind of in favor of this like really dumb version right now because there's
a lot of value when we're finishing a massive shaping session.
Like we did go through this guy and I think we, I don't remember where we shaped it specifically,
somewhere down here, maybe down here.
Once we get kind of clear about what all the views are going to look like, and typically
if there's two of us on the call, creating the task grid is actually very, very quick.
It honestly takes maybe five or 10 minutes to manually do it.
But then, so it's quite a great, it's a great way to capture specific action items
now like based on the plan.
So I want to, I don't know, I don't want to lose that human element of it and outsource
all of it to the AI, although I totally see the value of like two-way communication,
like once you're back into coding.
So you can play with it.
Let's start with the copy markdown.
Maybe there's even just like a, like when you're hitting a new slice, you could just
hit paste.
Like you can like have the LLM create the markdown and just paste it into like a slice
here.
Something.
Yeah, that's what I was thinking.
So, you know, say you do ship this out as markdown to an LLM and then it's like working
on some stuff and then say it does a couple bullet points.
How would you then, you know, you almost want to have it generate the new markdown file
with the ones checked off so you can put it back in here and not have to go through it
and line by line, check out which ones it's actually, which tasks it's done and can kind
of update it.
Yeah.
Generally as well, I'm doing like to me each, generally it's, it's almost like a one task
to one commit ratio as well.
I don't know how you guys work, but I mean,
and these are pretty big things.
Like you can almost see like I did, you know,
search clients was one commit,
search projects was a commit, get the first setup.
This will be another commit here.
So maybe there's something in there as well.
It's like at the end of the commit, we like update the,
and that's where the MCP idea could come from,
where it could maybe like just update it for you.
Because I think this would be cool if you could also,
if it was live and it was kind of live synced,
I could have this up in one window and my,
and have Claude over here and be telling it.
And then I could kind of zoom out and sort of see stuff,
literally start to like visually get finished.
It'd be pretty magical.
It'd be very satisfying.
Very satisfying.
You just like see this like dynamically getting like,
you know, multiple, like just jumping around.
That's what we're trying to maximize is satisfaction.
Yeah.
But I do, yeah.
I think we ballooned it into a completely different thing,
but it is really interesting what you could do with it.
Yeah.
I think it's good and we can always,
you know, go back to this.
Like, this would be a good moment
if we wanted to start here.
This is how I'll always ends up
with a little breadboarding something.
Oh, we have like a,
bear with me as we go.
And we also have a,
yeah.
If you guys have any thought,
I'm just going to do this while we're talking.
Cause I think there's something we can capture.
Yeah.
I was thinking about, you know, where to put the,
where's like the highest leverage
to put in like another AI's like slice
where we just like keep doing with the humans.
Our first, I think the big one is definitely
like shaping current system, you know,
keep doing human, like framing
and keep doing human is like shaping the next,
like the, what it could look like,
but like for shaping current system.
Cause there's a lot of times like unknowns,
there's a lot of code to read and you don't catch stuff.
So with like AI examining the code,
are you able to like actually catch way more and yeah,
to get like better shaping
that we're not like missing anything.
Yeah. I think it is.
It's kind of like you do the first draft
and then it would be great to like,
Hey, I want to build this task grid.
Then we kind of kick that over to the,
the sort of planning mode.
And if it could sort of read out of here,
here's what the initial plan was,
then it could challenge those ideas and say,
Hey, there's probably here's five other tasks
or edge cases you didn't think of.
Okay, let's go ahead and add those tasks.
Maybe then it goes from, you know,
four items to like eight items.
And now I have a much better idea
of all the things that needs to be done.
And then we kind of get ripped through all of those things
one at a time.
I do think there's a good,
it's almost like we have our process as well as a,
as a team.
I think it's good to have,
even if somewhat of a dialed in process for the LLM as well
to go from, you know, here's the task we go through each,
you do one thing at a time.
Don't try to build all eight things at once.
I mean, you could, but like one at a time, check it.
We're doing verification at each step
and then we commit things for every step.
And maybe we have like,
we could use and use the cloud skills as well
to have a way where it can like,
hey, it knows that we need to go find this project.
You'd have like, it's not a one-to-one match of like,
this project is matched to one repo.
It's like, we just have to have a way to connect
like this to the Innovo dashboard repo,
but there could be 10 other projects similar
that also connect to the same repo.
So I don't know the, how that piece would work,
but to me it's-
To connect a client to a repo.
So if a project is from a client, then it's to that repo.
Unless it's one client.
We're assuming that each client only has one repo.
Which-
Yeah, in some cases it doesn't, it has more than one.
Yeah, so like if we're gonna try,
we're gonna have two repos for the same project.
So it breaks down quick, but I do think there's a,
I think if you had an MCP where it went and grabbed,
like had even a wizard that was like,
is this for this client of this client?
Well, then you just like search for what the project is
or some way to connect.
Like I'm working on like specifically,
like we give it exactly that name and then it can go.
go and pull tasks based on the name or something.
I don't know.
It has to be something like that.
But the other thing we didn't talk about,
this was all getting it from the LLM back here.
Like I was thinking all of you guys would be very interested
in getting it from here and back into Notion.
But since that's not like the first thing
you all thought of, I think we skipped that.
Now you can just copy the link.
Yeah, exactly.
Anyway, very good.
Okay, so the other thing I have is a little,
if you guys are, I know we looked at this
for the team stuff here.
And so I have this little like privacy mode.
So like any dollar amounts here,
if you go to any of our other screens,
it puts the whole thing into a privacy mode
and everything gets blurred,
which makes it quite nice for demos.
So the other thing feature here, if you guys have,
you can go in and set your availability here.
So you can click in and set the availability
for upcoming months of how many weeks
you wanna spend or work.
And then we can start to predict,
fill in those projects moving forward.
We can try to go a few months in the future.
And this should help like clear up some confusion and stuff
if there's like a debate on which month
something's happening.
Was it one week?
Was it two weeks?
What's the date of when to expect this?
It does actually have the date
of which payment's coming when and amounts and all that.
So should be helpful there.
So, and I'll add some more screens,
maybe the status one and other things,
but I don't know if there's any other thoughts
between you guys, if you had looked at this yet.
Oh, I was, one question.
On the Superbase, there is sensitive data
or can we have access to the database?
We can have, I think it needs to be through
like something controlled, like the API or the MCP.
Yeah, I would-
No, I mean like the Superbase project itself,
like I don't have access to it, I'm not sure.
We are supposed to, yeah.
Okay.
No.
Just because I wanted to play a bit with it during-
Yeah, I think one of the things I was gonna do
is make like a beta version of it
so we could hack it a little bit
and then not have to worry about breaking something.
Yeah, because I think like I can run like Superbase locally
so I can make all the changes and then like,
once it's good to go, I can apply it to production.
But I wanted to play around with it a little bit.
Yeah, I think like a, I was gonna experiment
with the MCP stuff first to see if we could go
and basically access the entire app from your terminal
or let Claude access the app.
Because then we can have kind of a controlled way
that they can like update tasks
but maybe they can't delete projects, for example,
or have some security around it.
So I can, that was kind of my next thing
was to play with that, but.
Yeah, definitely do the beta thing
because like given access to like us, especially Jonathan,
I think he'll like build crazy stuff.
Well, you guys don't think you have enough work to do.
I don't know.
There's always space for a new side project.
Here's the thing.
Okay, here's my thing.
I do think it's extremely valuable
for every single one of you to have some side project
to be working on because it is insanely freeing
to just be able to make these types of decisions
and try stuff.
Because when we're working with clients,
we're in this extremely like cautious line by line,
can't get anything wrong, don't wanna break production.
But like if I, I hack with LM
and change those edge functions all the time
and they just run and they update 500 projects.
And like if we do, like what's the worst that could happen?
Like I accidentally delete them all in Notion.
Maybe I know that's the worst thing I can restore them,
but I don't know.
Like it's not, it gives you a lot of flexibility
to play with it.
So I highly recommend having something
and just lets you like experiment.
Cause I've learned a lot here that I'm now like
when I go work on tribe,
I'm like thinking of things a little differently.
Like we should have a command palette in tribe.
Like that should be like a one hour reactive task.
You can just quickly jump to a user
or jump to like a group or a course or something.
I didn't realize it was so simple.
And then once you add it, you're like,
oh wow, this turns it like for the power users.
It's just like a game changer for power users.
Hopefully, that's actually a great idea for we can add it to reactive and I can take a
look like, yeah, I have some stuff to finish with, but I could take a look.
Nice.
Awesome.
Great.
That's it.
Any other thoughts?
Just one comment.
It's not very related, but it's something interesting that I learned regarding this
automation processes.
It's like, I was having an issue with Tribe today earlier, where specifically the deployed
version by CodeMagick was crashing and getting stuck on the launch screen, but this was not
happening on the debug mode and this was for a very specific way that Firebase starts
the project.
But that's not the point.
The point is that the way I fixed it was by allowing Clouder code to connect with the
Chrome console using the Puppeteer.
So this way, I basically said to Clouder, hey, iterate over this project until this
error is not a thing anymore, because every interaction needed to generate a build release
and serve it locally on my local host, because it was the release mode that was the problem.
And the debugging process was basically like generating the release, open it, seeing the
Chrome console and making the changes according to what I was seeing.
And what I did was I basically said, hey, now you can see the console yourself.
So iterate over this until this is ready for me to test.
And this made my time a little bit better fixing this.
So very interesting stuff.
I didn't hear about it before.
It's called Puppeteer.
I did that.
It sounds great.
But it's very, very interesting.
So you just had the AI run the build command, and then it waits for the build command to
complete, and then it runs Puppeteer?
Exactly.
Cool.
It waits, then it runs open Chrome with the Puppeteer on that specific task.
Fully autonomous.
Yeah.
It opened the Chrome, tested, saw the problem, closed it, come back, made the iteration,
run Chrome again, and did this for like four or five times until it reached a point where
it uploaded.
And I was like, man, that's great.
That's impressive.
You can also use Playwright, I think, a similar console.
Yeah, I think it's similar.
I've done that before.
Because if you have UI bugs, it takes like a screenshot, or it will navigate, like, login,
go to this page, click on this thing, look at the screenshot, analyze it, and it kind
of gets in a little feedback loop like that.
Do you try it with a Flutter app, the Playwright?
I'm trying to remember what it is.
Because I'm not sure if it will find, because the Flutter doesn't have the DOM.
Yeah, we have like just the canvas, so we don't have the HTML components for the Playwright
to navigate, so I'm not sure if it will navigate properly.
But that's one of the problems with AI and Flutter, like, not having the DOM.
It's cool, but it's like, for some stuff, but for this point specific, it's very noisy,
because all the IC is just like a bunch of unreadable code.
But yeah.
That's why we send all the Flutter projects to Gennady.
Thank you, thank you.
I'm thankful for the difficulty of using Canva in Flutter.
Awesome.
We'll probably get back to, like, some other training.
I think this is probably good on the agency dashboard series.
And then obviously we can keep using it.
If you guys have suggestions, let me know.
I think I may make a new channel in Slack just for this, like, almost as its own app
to give thoughts to, versus blasting you guys on the team channel for this.
But yeah, we'll keep testing it out.
And at least it's kind of in a space where we could start to use it, I think.
And now it's less of a concept and more of something that's, like, V1, I would say.
So I think what I'd love to do next, maybe, is kind of almost start at the very beginning
of this project.
And just, like, if you guys are starting a side project, kind of here's how, in one hour,
I would go from, like, a totally blank repo to, like, something deployed with auth and
some basic database in Superbase.
And then maybe walk through, like, Mark Lau's, like, Ship Fast template and some quick things
you can do to fix it, like, integrating, you know...
Google off and things like that really, really quick.
Um, cause the, that stuff you shouldn't be spending any time on, uh, you should
be spending your time on like the actual application and what problems
you're solving and such.
So, um, yeah, definitely worth it.
Uh, I think the idea of like just building something yourself in your
own, it's just, it gets you through the reps of going from nothing to something.
And the other thing I was very helpful was when I'm working on my own thing, I
found myself going back to the same tools of using the framing to use
the shaping, to use the task grid.
Um, it's a great test to see if those things are actually useful because
when you're using your own stuff, you're like, oh, I'll just hack
it or vibe code or whatever.
Um, but I found like, oh, I actually feel overwhelmed by this project.
Oh, well, there's a tool for that.
Like that's what the shaping's for.
That's what the task grid's for.
Um, so I felt more confident in our, in our system as we went into it.
So all good stuff, but thanks for joining us guys.
And, um, yeah, we'll, uh, we'll jump into something else next week.
Thanks.
That was great stuff.
Good stuff.