Slightly Caffeinated

Chris Gmyr (00:00)
Hey, welcome back to a slightly caffeinated podcast. I'm Chris Gmyr Hey TJ, so what's new in your world this week?

TJ (00:03)
I'm TJ Miller.

man, there's not really much new. I have been just buried in the depths of like prepping for Laracon and like just not working on Prism. I'm like desperately trying to like find time to catch up on the repo. I know there's PRs. I know there's issues. I am so sorry, everybody. I've just been like in the depths of like trying to work.

Chris Gmyr (00:27)
Yeah, that's all right.

TJ (00:33)
and deal with like mental health and like prep the house for leaving for Laracon and like getting the talk ready and practicing and just that is that has been all consuming.

Chris Gmyr (00:45)
Yeah,

yeah, that's a lot for sure. But you only got a week more to go and you'll be done with the talk very soon. So hopefully things will kind of slow down and get back to some sort of normalcy.

TJ (01:00)
Yeah, I'm, I'm feeling pretty dialed in on the talk now. we, in the like speaker chat yesterday, we were like going back and forth on like timing and like slots and like, just making sure that like everyone's, cause, after your talk, they're like, they wanted a little bit of time. Cause it went over so well, like last year with Aaron to like ask Aaron, ask a few questions, after your talk. So.

Chris Gmyr (01:23)
Mm-hmm.

TJ (01:26)
They're doing that again this year. And so we were just kind of like clarifying slot timing and everything. And I was like, Oh, great. Uh, I was off by five minutes. like, um, I had my talk and then I was like, Oh man, I need like five more minutes. So like I added a bunch of stuff and then come to find out it wasn't. And like, I don't need five more minutes. And so, uh, yesterday I went in and just like cut an entire section out and the talk is actually so much better for not having that section in it.

And it's exactly on time. So I am finally feeling confident about it. I've got a couple lipstick items I want to take care of. want to like, I want to see if I can bump the font size a bit bigger. But I know if I do that, there is one slide that gets unwieldy. Like, no, there's two slides where the code fits exactly as is. So if I bump the font size up anymore, I'm going to have to like.

Chris Gmyr (01:58)
Thanks.

TJ (02:23)
figure out how to rework those code snippets and I'm not 100 % sure how to do that.

Chris Gmyr (02:32)
Is there a way to change the font size for just those single or a couple of slides or not really?

TJ (02:38)
There should be. So I'm using slide dev, and it's all just like HTML and CSS and everything. So I should be able to apply a class to the slide and then adjust the font size accordingly. So I might just do that for those two slides and then blow everything back up a bit bigger.

I'm feeling, I'm feeling good and excited about it, man. I'm nervous about being on stage. That's for sure. So I'm hoping just like the amount of practice that I'm putting in is going to, pay off with the nerves of, of being on stage. So like the last lyric, like PHP tech was great. I felt super confident on stage for both presentations there. but there's just.

like that's multi-track, right? So you've got like a small, you're no matter what, you're splitting the crowd up. And this is gonna be like very focused in front of lots of people. And last Laracon, I like basically blacked out on stage. I don't remember, I remember like one or two moments of like being on stage and that was it. Like that's it. I remember like very like one or two moments and like.

Chris Gmyr (03:23)
Mm-hmm.

TJ (03:43)
everything else just complete blur until I got off of stage. So.

Chris Gmyr (03:46)
Yeah,

that's right. It's going to be bright up there. You're only going to see the first couple rows anyway. Just pretend that it's like kind of back in tech and you just have, you know, 50 people, 100 people in the audience and I don't know. Keep it like that in your mind.

TJ (04:02)
Yeah, yeah, was, ⁓ my son misspoke the other day when I was telling him I was nervous about it. And he's like, just imagine everybody in your underwear. And I'm like, imagine everybody in my underwear. Okay. That that's a new one. And I think I like that. Like imagine people in their underwear. No, imagine them in your underwear.

Chris Gmyr (04:19)
Yep, yep.

Good job, kiddo.

TJ (04:22)
I'm

like you misspoke, but I totally love it. Yeah. Yeah. How about you, man? What's new in your world?

Chris Gmyr (04:24)
Yeah, that's awesome. So funny.

man. Also not terribly much. Just project work, trying to ramp up on possibly a new project coming down the pipe. Maybe starting next week that I'm some preprep on and trying to actually knock out some actual coding tickets for a little while. So that's been exciting. Getting a couple of utility things out of the way so other people

can just focus on strictly feature work. But that's been pretty cool. So just learning more about the tech stack technologies, using a little bit of cloud code here and there. But yeah, going pretty well.

TJ (05:05)
Sick, man. I'd love to hear more about this cloud code that you're using. That's dope. I'm glad you're getting into some space where you can get back to doing some coding. I know you've been working a lot on the planning and logistical and research side of things. So finding your way back to code, I think, will be a nice break from all of that.

Chris Gmyr (05:21)
Yep.

Yeah, yeah, and might be short lived. Just diving in for a couple weeks and then I'll have to pop back out and do something else. But that's all right. That's what I'm here for. So it's all good.

TJ (05:32)
Yeah.

Yep.

Yeah, sick dude. You want to talk some coffee?

Chris Gmyr (05:40)
Yeah, let's talk about some coffee. So I thought it would be interesting to talk about the different types of coffees and how they're processed or finished. So there's different processing methods. There's like wash, there's natural or like natural sun dried and then honey processed. Have you had, well, you've definitely had the wash because that's kind of the default, but. ⁓

TJ (06:05)
Yeah.

Chris Gmyr (06:06)
with like natural or honey processed. Have you had any of those? you prefer one or the other? Can you taste the differences? What do you think about the different processing of coffees?

TJ (06:17)
So I mean, granted, it's like kind of the default and like what you'd expect mode, mostly washed. I have tried natural once or twice, and I've only tried honey processed once before. Honestly, I don't really think I could tell you if I could taste the difference between them. But I'll also say that I have a super washed out palette. Like I really.

I'm not that great. Like, I can sip a coffee and if they're like, I can only really pick out like notes and like different flavors if they're rather strong. ⁓ Like my, my partner, she, like, she can pick out like sip a coffee and tell you all the different notes, like has a really refined palette. I'm

Chris Gmyr (06:53)
Mm-hmm.

TJ (07:04)
I really can't. so for me to say that I really don't know if I could taste the difference between them is not really say much, but yeah. Yeah. I'd like to try some more honey processed again. I think that's like a really interesting, interesting take on it all. So how about you, man?

Chris Gmyr (07:13)
Okay, I'll take it, I'll take it.

Yeah, I don't, I can't say if I've had honey processed. If I did, maybe I didn't know it or wasn't aware of it. But my favorite is the natural process of either washed or natural. And counterculture has a handful of natural, sun dried processed beans. A handful of times a year, they probably come out with like anywhere between four and six different.

TJ (07:39)
Yeah.

Mmm.

Chris Gmyr (07:51)
bags of different beans throughout the year. So when I was drinking more of a variety of coffees, I would always get the natural sundried because they were just like a lot more vibrant. were fruitier, just brighter and just super nice to drink. you would like, we drink all of our coffee black. like there's nothing else to hide the taste to it.

And between the washed and the natural, the natural had like a much more like bigger, brighter pop to it. And it was like, wow, like this is really good coffee. And I don't know. That's what I liked most about it is like it there. They tend to be lighter roasts because that's how you get like some of the more flavors out of it. So it's not like as, you know, burnt away from the darker roasts. But we usually drink medium or light.

TJ (08:29)
Yeah.

Chris Gmyr (08:42)
Anyways, so having that natural fruitier, even more floral at times, just brightness to it. It's like you take that first sip after doing it wash for a while, like full amounts, and it's like, wow, that's really good stuff.

TJ (08:43)
same.

Man, I'm have to order a bag then and see if I can pick it out because, yeah, that's where I definitely start to notice flavors, like I said, is when they're much stronger because I just have washed out pallets,

Chris Gmyr (09:10)
and

Yeah, so try it out. I'll have to see on Counterculture. I'll have go back and see what they have and some of my coffee database, which ones were really good, and which ones are available. Because they switch them up all the time. So even something that was available last year, for example, they might not have it this year. So it always changes a little bit. But I'll take a look and see if I can find anything that we've gotten before that's available right now.

TJ (09:22)
Hehehehehe

Sick. Yeah, I'm definitely taking up on that because, yeah, just nerd about it. I don't know. I want to try it out again.

Chris Gmyr (09:49)
Yeah.

Yeah. And processing is probably like a little bit more on the nerdier side instead of just like the roast level and things like that.

TJ (09:58)
yeah, for sure, for sure. Yeah, how to post-processing your beans. What do you prefer? Yeah.

Chris Gmyr (10:00)
you

Yep.

Yep.

TJ (10:06)
Yeah, yeah, I've only tried the honey processed once and it was like a so, this was.

probably 10-ish years ago, there was this really small local coffee roaster, and he was ultra artisan about it, and he had some honey processed stuff that he brought in. And it was a big to-do, and everyone was like ooh-ing and ah-ing about it. I was just like, yep, tastes like coffee to me,

Chris Gmyr (10:35)
Yep. that's funny. Yeah, so actually just looking at counterculture and I'll put the search link in the notes, but they have a handful of them right now. So they have two from Uganda and then Yerga Chef from Ethiopia. Yeah. The Yerga Chef is great for cold brew coffee and like colder drinks.

TJ (10:44)
That sick.

Oh, that's going to be the ticket. We're we're.

Yes.

Yes. Yeah, we're, we're big fans of, African, African beans. I'm nothing wrong with like South American, but like we definitely have a preference for like African beans. ⁓ so yeah. Hmm.

Chris Gmyr (11:01)
to

Mm-hmm.

Yeah,

I'll put this in the show notes now, and I'll text you on the side so you can check it out later.

TJ (11:20)
Sick. Yeah,

no, I'm definitely going to order some. Sick, dude. Well, moving in from coffee, something I wanted to talk about last week, but we ran out of time. Newsletters. So I believe, I believe, I don't know, they talked about it a bit on like mostly technical. Aaron and Ian, and Aaron had mentioned that he does a like weekly newsletter.

and on my personal site, I have a newsletter signup. I think I've got like four or five subscribers and I've never, I've never emailed the list. but with, with the direction of like Prism and like updates with Prism stuff and like, I don't know. I've been thinking about.

And like Aaron was just talking about how he's found a lot of like success and enjoyment out of doing his like weekly newsletter kind of as like a nice, like weekly, even is just like a reflective weekly recap for himself. ⁓ he's found a lot of value in doing it. And this is something like I've tossed around for a while. but I've always been a little hesitant to like make the commitment. Cause if I'm to make the commitment, like I want to be consistent about it. ⁓

Chris Gmyr (12:15)
Hmm.

Yeah.

TJ (12:28)
And so I've been, like, I've struggled a bit with, like, making the commitment side of things, but I think at the very least, there's going to be like some prism content on there. Like, at least, at least I can talk about, hey, here's a release and like break that down. but I don't know, man, like, what do you think about newsletters? Do you, do you subscribe to some, do you read them? there's only like,

I think the only newsletter that I regularly read is like Matt Stauffer's newsletter. I've got to get on errands, but I'm thinking about it,

I don't know, yeah, like what are your thoughts on him?

Chris Gmyr (13:05)
Yeah, I like some newsletters. tend to oversubscribe, not read as much. But there's like a couple that I will read all the time. Matt's being one of them. I really like his cadence. He does monthly. He does like a little bit of like personal, you know, updates in there. And then he gets into like favorite, you know, tweets or blog posts or like news from Titan or just like interesting things, you know.

TJ (13:12)
Yeah.

Chris Gmyr (13:31)
So I like that mix. Some of the other more technical ones are like newsy newsletters. Like I don't really read all that much. Very few things I let hit my inbox. So I know we talked about this like a really long time ago. But I use Reader from Readwise. It's like a read later like bookmarking service. ⁓

TJ (13:53)
Yeah.

Chris Gmyr (13:54)
It's kind of like all the things, like all in one. And in there, you can have an email address that goes right into your feed in Reader. So I use that email address to bypass my inbox, my Gmail personal inbox, or the ones that I'm already signed up for. I have a custom filter that searches for the from email addresses from all these newsletters. It'll apply a newsletter label automatically.

TJ (14:02)
Mm-hmm.

⁓ sick, yeah.

Chris Gmyr (14:23)
set as read and archive and then forward to reader. So a lot of my stuff is just funneled into reader. And then whenever I check that, like I'll see what the headlines are or maybe some of the content and either just like delete them or read a few of them. Because I have like different things in there, like some tech, some like health, some financial, some credit card rewards, travel, know, type of thing. it's.

TJ (14:27)
Mm-hmm.

Chris Gmyr (14:46)
kind of is like a broad gambit of things. And sometimes I'm just not looking for something or not in the mood to read a bunch of stuff. So I'll just delete them. So yeah, it kind of depends on the content that you're putting out. Like I, again, really like Matt's newsletter. And if you were going to do it, I would say kind of err on the side of less frequent. So maybe starting out with monthly.

TJ (14:49)
Yeah.

Yep.

Chris Gmyr (15:13)
because then, you know, you'd probably have a bunch of stuff to, you know, reference from Prism or even like live streaming. When you get back into that, ⁓ coming off of Laracon might be a good time to do that. So even if you have like a signup form, you know, on your site or on Prism, before Laracon, not that you need more stuff to do before Laracon, but that might be like a good call out. Like during your talk to us, like, if you want to keep up on Prism updates and what I'm doing, hop onto the newsletter.

type of thing. So I've thought about doing it before, but I don't feel like I have that much content to generate outside of this. But just finding some more time to write some more blog posts. And there's a handful of topics that I want to write about, but just haven't had the time to really distill those down and have a writing plan to do, just because there's, I don't know, feel like

so much other stuff and kind of underwater on some other things. So haven't had the extra time or motivation to tinker with stuff like that. But I've dabbled with it on and off the thought of it at least. But yeah, I haven't put the trigger yet. I think you're more apt to, or better set up to do something like that moving forward.

TJ (16:08)
Yeah.

Yeah, think it's just, I think with Prism now, I've got an excuse to have content. And I think there's like, that's also sort of an excuse for people to sign up for the newsletter is.

is like Prism content or even just like AI content. And I think I can probably get into a workflow where I'm like.

I have an efficient way to like save stuff for later, like interesting articles, interesting tweets, things, things that I found along the lines with like AI and stuff too. so yeah, I, I think I'm going to pull the trigger on it. I, like I said, I have it, I have the infrastructure and everything set up for it. I just like, haven't pushed it and I haven't actually done anything with it yet. ⁓ yeah, maybe, maybe I should.

Chris Gmyr (16:49)
you

Mm-hmm.

TJ (17:09)
should push something on there. I can always add it to the last slide. Like, yeah, starting a newsletter. Like, sign up.

Chris Gmyr (17:17)
Yeah, put a nice little QR code on there that people can scan on your last slide or something, get all your info, newsletter, things like that from the stage.

TJ (17:26)
Yeah.

Chris Gmyr (17:26)
Yeah, but I mean, I would sign up for your newsletter,

TJ (17:30)
Yeah,

I've thought about it for a while and it just like...

I don't know. just, seemed like a big commitment and I didn't want to like do it and not like do it, you know? I didn't want to like do it and do like two newsletters and then fall off the wagon. I kind of wanted it. Like I was kind of waiting for a position where I like, I could commit to it, but also for the longest time, I just like, I felt like I lacked content, but now I feel like I have content. And I also was like, yeah, who's going to be like interested in this stuff when now there's like people using Prism.

and people interested in prisms so like

I think there's an excuse and justification for it now, much more so than there has been before, so...

Chris Gmyr (18:12)
Yeah, yeah, totally. Because you can even explain what some of these new features are, or maybe new benefits of a new model coming out, or ⁓ new features in the Prism package itself, or something that you're really excited about in the AI world, or even upcoming Prism releases, or even featuring people's projects that are out there also.

TJ (18:22)
Yeah.

Chris Gmyr (18:39)
think you can cherry pick so many things out there that are available within Prism and Lirval and AI in general. And especially starting off monthly, I feel like there's plenty to share around that because you bring so much benefit and knowledge to that as well. It's not just sharing the link out, right?

TJ (18:58)
So this is going to sound weird because one of my reasons for not doing it has been commitment.

But like, feel like, I almost feel like a weekly cadence would be easier for me than a monthly cadence. Like, and I think initially that sounds counterintuitive, but like, I feel like doing a monthly one, there's like this pressure. I don't know, at least like internally, I feel like there's like more pressure to do a monthly one than there is like a weekly one. And there's like,

It's much more on me to like figure out what.

Like I've got like a month of like stuff to like try to remember to put in there and like I've got to like track all of that. And if at least I do like a weekly cadence, it's not impossible for me to remember what I've done over the course of a week, but like trying to like save stuff up and like remember what I've done over the course of a month could be pretty intimidating. it at least like feels kind of intimidating. Whereas like weekly seems a little bit more approachable.

And I'm sure it's a certain point, like.

It seems like a big lift now, but at some point I'm sure I systemize it and like have stuff. Like I get enough stuff in place that like I create a lower lift for it. I think that's something that like Aaron was talking about too, is that like he systemized things and like created an environment where it's like a low lift to do.

And so I think I'd like to like go that route. So I'm like, I'm actually thinking more about doing a weekly than a monthly.

Chris Gmyr (20:30)
Would it be beneficial to only be writing on a weekly cadence? Like you do the work on the weekly cadence but only send it out monthly? So that gets you like in the process of curating what you need to curate to then just keep like a living doc somewhere and then just pull the trigger monthly.

to maybe like a little less pressure of actually like sending it, but maybe you have enough stuff and enough positive pressure to do that weekly. I don't know.

TJ (21:05)
I don't know. Maybe, maybe I'll put a poll out on Twitter or something and see what folks think about like doing a weekly or monthly and just kind of seeing like what kind of cadence people are interested in. Cause I, I could go, I could go either route, but I've definitely been sort of leaning towards weekly. And I just like, I kind of liked, I liked Aaron's approach to it and how he had mentioned, you know, it,

it being a nice sort of like, just a nice time to like reflect and review what you've done for the week and publicizing, like putting that out publicly. I don't know, something about that,

something about that, just like hit me, hit me a certain way.

Chris Gmyr (21:47)
Yeah.

Yeah, I mean, whichever way that makes you feel best and like there's no laws or rules saying that you can't change it in the future. So if you like do it weekly for a little while, because you'll have like, it seems like enough content, enough momentum to even kick it off weekly. And if that becomes too much or things slow down, you know, bounce to every other week or even monthly in the future, you can still have your like writing cadence every week.

TJ (21:56)
Yeah, right.

Chris Gmyr (22:14)
whatever systems that you put into place over time. yeah, if you want that quick momentum, then kick it off weekly.

TJ (22:21)
Yeah. Hmm. Something to think about, man. Appreciate the feedback. it's, it's, like I said, it's been something I've been like kicking around with and like I, it's out there. on my website. People can go sign up for my newsletter right now. Um, you're not going to get anything at the moment, but like you can sign up. Um, but also like talking a little bit like lead gen, right? Like, I'm, I want to do a prism course. I want to do a prism course really bad.

Chris Gmyr (22:36)
Yep.

TJ (22:48)
I've been thinking about it for a long time. I actually really wanted to do one earlier this year, but like Prism just wasn't in a place where it was ready to do it. but coming off of Laracon, going to be tagging 1.0 soon-ish. I think it's going to be in a good place to do the course and like pull the trigger on it. And like, I need the leads. Like I need, I need the list of like people to like email and tell about the course and everything. that's, that's kind of part of it too is, ⁓

honestly a little bit of lead gen heading up towards like a course or like products or sponsorships or stuff like that to you kind of like formalizing things a little bit.

Chris Gmyr (23:21)
Yeah, I mean, I know you were kind of debating whether or not to pull the trigger on 1.0 before Laracon, but that might be like a good entry point into the newsletter too. It's like, we're going to be ready for 1.0 soon. Jump on the newsletter to get notified first about it type of thing.

TJ (23:43)
Yeah, yeah, for sure. think that's, that's something I'm leaving off with. So yeah, maybe that's something I will add into the last slide. cause 1.0 is at this point coming after Laracon. there's just, there's no way I think I can get everything done that I want to get done and still be prepared for Laracon in time. I'm hoping by Laravel live Denmark.

that we're at 1.0. That's kind of my loose goal now is to be 1.0 by that conference. I think that's a good excuse to be on the newsletter too is like, find out about 1.0 as soon as possible.

Chris Gmyr (24:19)
Yep, totally. Yeah, I like that idea. Then that gets you not as much pressure for tagging 1.0 before you go to Laracon. It gets an added benefit of getting people on the newsletter and a little bit more exposure in there. And then, you know, in the meantime, before you can, I don't know, maybe start drafting up newsletter launch email number one. Get it ready.

TJ (24:44)
Yeah. Yup.

Yeah. I might, ⁓ right now I'm using button down email for everything. may consider switching over to bento just cause Aaron loves it. and I like using things that people recommend. So I might, I might switch providers right before I pull the trigger on it. So that's, that's something I'm to have to look at and maybe I'll, I'll work on, the plane or something. ⁓

Chris Gmyr (25:00)
Yeah.

TJ (25:10)
I'm on my way out to Denver. I don't know, it's just getting close, man. I leave on Sunday. It's Thursday, so this is all coming up really quick and there's a lot I want to do. So I don't know, maybe I don't sleep tonight.

Chris Gmyr (25:14)
you

Yeah.

Yeah, but even if you just like captured email addresses, like you can always export them, import them into the new place anyways.

TJ (25:29)
Yep. Yeah, a hundred percent. So cool, man. Moving on from newsletters, I think you'd added something here about Cloud custom commands. that's something that we talked about, I think, last week a little bit. And we may be starting to find some excuses for using slash custom slash commands and stuff. So I'd love to hear about your experience here.

Chris Gmyr (25:51)
Yeah, definitely. So this was definitely prompted from last week's conversation. And as I'm working through the week, I was like, OK, what can I possibly make a custom command for? So I basically started off with two things. I created a refresh repo command, which basically you run it. It scans. It basically re-initiates the

The Claude MD file. It reads what's there. It looks at the application, sees any new dependencies or commands or whatever the case is, and updates anything that it deems important to add back to that Markdown file. And it's just nice if you have a repo that has a lot of development, a lot of people working in it, and you don't always want to capture every single...

new merge or rebase every other day to it. maybe your brew updates, running that, the repo refresh once a week or something like that would be good, because then you don't have to type out, rescan the repo and do this and that and the other thing. Now this will just take care of it. So that was, I think, the first one that I made. So that one's been really helpful, refreshing everything, because the first time I ran it,

It picked up like, I think the last time I refreshed it was, I don't know, three, four weeks ago. So it found like a whole bunch more stuff. It updated architecture changes, like a whole bunch of things to it. So that's been really helpful. Probably going to run that on a weekly basis now on all the repos that we're working on. The other one is what I just named a branch context.

is I'm either switching to a branch that I'm working on or pulling down for a review or something like that of the repo refreshes for main branch. And then when I'm going into something else, scan for changes, tell me what's in the last handful of commits, and kind of refresh your understanding of what has changed in the repo in here. And then we can either work towards something else

together or I'm asking you for why did this change or why did that change or whatever the case is. It's just refreshing the immediate context for that branch. So that's been helpful as well. ⁓ Yeah. So I guess I'll pause there because then I have another whole workflow. So any questions on either one of those or any specific details that you were?

TJ (28:12)
That's sick.

No,

man. I think that sounds great. Those are very useful things to have as slash commands. Yeah, I'm still personally finding my own use cases for them. I haven't dove too far into it yet. But maybe after Leracon, I'll spend a little time coming up with some stuff. I think those are like, I think it serves as some decent inspiration for some other slash commands I'm thinking up right now.

Chris Gmyr (28:28)
Yeah.

TJ (28:53)
Yeah, what else you got?

Chris Gmyr (28:53)
Yeah.

Yeah, so the next one, which I do a lot, is PR reviews for others. And coming into a new tech stack, there's some things I am just not aware about, or best practices, or whatever. So there's a default slash review command that comes out of the box in Cloud Code. And that gives a decent understanding. It'll tell you what's changed.

what maybe some of the new dependencies are, some architecture changes, things like that. But I found that it's kind of high level and not really to the depth that I wanted to go with addressing questions or open items or concerns or review or change requests, things like that. So what I did is created a new PR review command that started off with

the base review command out of the box and added a bunch more on top of it. So what I did was took an example PR that I'm working on and I had a couple of questions or call outs or whatever and basically asked it to pull out all the questions or call outs, rank them.

as like high, medium, low importance and lift for changes. And for each one, validate the comment, question, or call out. And then add supporting information one way or the other. So for an example, to bring it kind of back to Laravel is I make a PR that

I don't know, doesn't use the action pattern or doesn't use dependency injection or something like that. Like it's a new input class, like inside some other code. So you as TJ come on the GitHub PR, you're like, hey, can we use an action pattern here? And then you can use dependency injection and this and that, whatever. So the command will pick up that you had a question about this called out using dependency injection and an action pattern. And it will validate how

correct that is given the rest of the application and coding conventions in the tech stack, right? So because Laravel is kind of hot on action pattern, it should yield like, yes, TJ is correct. We should refactor this to using an action pattern with like method dependency injection or whatever the case is for that specific code change. And then it'll create a plan

TJ (31:25)
Mm-hmm.

Chris Gmyr (31:28)
based on that. that is the first command. And it'll output a plan in the .cloud slash plans folder that I specifically made. So I've been just reusing the cloud kind of hidden directory to put plans. of course, all these custom commands are in there. But plans will get them out of the repo. So I don't need to ignore them or do anything else, because I might want these plans to be long lived. So this also comes back to last week where you

TJ (31:53)
Yep.

Chris Gmyr (31:55)
copying and pasted the plans into a markdown file or something like that so you can reuse or restart later. So this will keep the plan in the Cloud Plans directory. And then I made a ⁓ couple other commands to follow up from the plan. So it'll create a plan based on the branch name, so like abc123, whatever. So it'll say like prview-abc123, and then a

execute plan command. And what this will do is you give it the branch name or even it'll sniff out the current branch name and it'll see if there's a plan in the plans directory and then it'll show all of the items that have been called out like high, medium, low priority and number them like one through five. And it's like, here's the plan items ranked in the specific order. Which ones would you like to tackle?

And you say, like, one, two, five, whatever. So you push one. It'll review the plan. It'll review the code. It'll implement all the changes based on the outcome that you wanted for that item. So because it's just a markdown file, you can go in and say, yes, I agree with TJ. We should definitely refactor this. So that'll be saved in the plan. So now when clog picks up item, work on item number one,

TJ (32:49)
and we'll love it.

Chris Gmyr (33:17)
which is that refactor. It'll go through refactor. It'll add or check tests against it. It'll, you know, lint and fix anything that it needs to. And then it'll say, we're good to go. I'm checking off that number one was done on this date and time. And then when you, it'll ask you if you want to refresh the plan or continue to like number two or number three. And if you click the status of,

a plan, it'll say number one is checked off, but you still have two through five that are still open. So you can come back to this plan anytime, switch back and forth between different plans and branches and different reviews or work that you're doing versus reviewing for others. And you can just pick up where you left off because the plan will auto track what you're doing. And Claude will update those plan check boxes and items and

TJ (33:47)
Yeah.

Chris Gmyr (34:09)
keep things rolling. And you can also refresh it. If you push a bunch of changes, then you're getting more comments. You can just refresh the whole thing, and it'll come up with a new plan. And you just refresh the whole thing and continue moving forward. So yeah, that's the work.

TJ (34:17)
Sick.

I'm so tickled.

We don't have video to go along with our podcast, but I've just got the biggest shit eating grin because that is, I love this. This is exactly the kind of thing that I'm thinking about for like slash commands. That is so dope, man. You're going to have to send the adjust to this because I'm going to need to riff on this a bit.

Chris Gmyr (34:43)
Yep, totally. So there's a couple of different commands. There's the PR review, which gets it started. There's a plan status that you can just call like a one-off, and then like the execute plan. And then any of these will auto sniff the branch or PR that you're on, or you can send an explicit branch name, and it'll pull that down. It'll switch for you. It'll

revamp and work on the plan. It'll do the PR review, even if you're not on the same branch that you want to kick off. So there's a little bit of that autonomous action to it. So yeah, it's really cool. Still tweaking and changing a few things. But I think it's just going to get better and better from here on out. So that's something that I was tinkering with this week. But I'm like, this is awesome. This is cool.

TJ (35:26)
yeah, dude.

That is

super sick. I am way into this. Yeah, I need just, I'm going to riff on this for sure. For sure. That's cool, man. I dig it. I dig it. I was working with Cloud Code the last two days. And I'm just like, what is going on? This is not doing good code. is just, this is a disaster. What is going on? And so I was lamenting with it.

Chris Gmyr (35:39)
Totally, totally. ⁓

TJ (35:56)
lamenting with Matthias over it and just like, what's going on? He's like, well, did you tell it to ultra think? And I'm like, I forgot.

Chris Gmyr (36:04)
Yep.

TJ (36:07)
Just

like, forgot. So I wonder if I can put that in the Claude Markdown file and if it'll just like always like default to ultra thinking then. Because I don't care how many tokens I eat through. I want it to think as much as possible when I'm writing code because like it legitimately makes things significantly better. yeah, I just like, I felt like such a big dummy for not telling it to ultra think.

Chris Gmyr (36:14)
Yeah. Yeah, I think you could definitely do that.

Yep, definitely.

Yep. Yeah, so I think putting it in the base cloud file and even maybe adjusting it in some of these, yeah. I'm sure you could put a big H2 header about thinking. It'd be like, always ultra think, no matter what the prompt is, if you wanted to go that route. Yeah, that should probably work.

TJ (36:40)
I wonder if it'll pick up on it.

you

I'm gonna do it like right now with the like Prism repo. I'm like not gonna sleep on this.

Chris Gmyr (37:01)
Yep, totally. Cool. So what I might do once I get some of these commands a little bit more fleshed out and I don't need to adjust them as much, I'm probably going to move them to the global clod directory so that I can use them across repos and projects and stuff like that and not have to copy and paste them or whatever across projects. So that'll be.

helpful in the future too.

TJ (37:26)
Yeah, yeah, I should probably move a bunch of like coding stuff, like my Laravel PHP coding standards. I should probably put that in the like my global just because I find myself copying and pasting that across new projects, but I don't start a ton of new projects. So yeah.

Well, sick man. Yeah, we've got Larycon next week. So we...

We may record next week. We may skip next week. We'll have to see how dead I am after the conference. ⁓

Chris Gmyr (37:54)
Yeah, I think

we'll probably have to skip because you're coming back, but I'm going to be out of town for an extended long weekend. So we'll pick back up and do like a recap on week. But yeah, good luck at Laracon. And it's going to be awesome. I wish I could be there. But you're going to do great. The talk is going to be great. You guys are going to have a good time. See all the Laracon folks and the cash money guys. So I wish I could be there, but it'll be awesome.

TJ (38:04)
Yeah!

Yeah, yeah, it'll be a good time. Yeah, I'm so bummed

you can't make it, but ⁓ maybe we'll have to do a... I know Dorinda probably... Dorinda definitely won't be able to make it, but we should do a stateside, get together sometime. Like a half birthday, like a half Laracon something like mid-year.

Chris Gmyr (38:38)
Yeah.

Nice. So yeah, luck. You'll do great.

TJ (38:40)
Cool dude. Yeah.

Thanks man.

Chris Gmyr (38:43)
Sweet. Well, want to wrap up? All right. Thanks for listening to the Slightly Caffeinated podcast. Show notes and all the links. Social channels are down below and also available at slightlycaffeinated.fm. Thank you all for listening and we'll catch you in a few weeks.

TJ (38:45)
Yeah, let's do it.

Yeah, we'll see it.