Episode 120 / 2021.11.01
Andrew Welch, Ryan Irelan
Ryan Irelan & Andrew record another devMode standup where we discuss Ryan’s prepper tendencies, and he goes on a rant about a SaaS he’s had issues with (he’d like to see the manager).
We go on to talk about Conventional Commits, and how they can make your git commits better, and discuss drug smuggling. Andrew sees a shiny object, and goes off on a side-quest making a Vite.js Dockered Dev environment in the name of fixing a symlink bug.
Then we discuss how Jack Antonoff, and how everyone who is really good at creating a thing — whatever that thing may be — does it via a process, not magic.
Finally, Andrew tells Ryan to grab his go bag and join him on a coding adventure to work on a Twig Devtools browser extension.
- History of the Prepper Movement
- CraftQuest.io
- Chad (slang)
- Conventional Commits
- Angular Commit Message Guidelines
- Gitflow Workflow
- Jack Antonoff
- How Jack Antonoff creates songs from small ideas
- 10% inspiration, 90% persperation
- Midnight Express
- Billy Hayes
- Vite.js symlink issue
- pnpm
- Vite.js Docker Dev
- Vite Contributing Guide
- An Annotated Docker Config for Frontend Web Development
- Dock Life: Using Docker for All The Things!
- Template Comments Craft CMS plugin
- Chrome Extension Development
- Vite.js devtools
- VS Code Language Server Extension Guide
Andrew: We Alright, let's get going.
Andrew: Hello welcome to devmo fm a podcast dedicated to the tools techniques and technologies used in modern web development I'm andrew weltch from and ny studio 1 7 joining me today. The man who always has his go bag packed and ready to go. It's ryan ireland how you doing ryan yeah.
Ryan: Okay, hey Andrew doing good. You know funny thing is I did have to use some of my emergency supplies the other day.
Andrew: Why don't you real quick. Just let everyone know what we're talking about here. Okay, because people may not know.
Ryan: Ah, well Andrew has this fantasy that I'm like a prepper which is not true.
Andrew: No, it's not a fantasy. You have a go bag. We have seen pictures of it and it is packed with currency in ah in a bunch of different um denominations and with a whole bunch of other stuff so that you can just grab and go if you need to right.
Ryan: No.
Andrew: And think there's a firearm in there too like a walter ppk or something.
Ryan: You are just making stuff up I have a a suitcase a safe that is like the suitcase style safe safes that that has like you know important documents like passports. Maybe some cash important.
Andrew: A go bag. Yes. Money it Yes, okay Ryan if it contains passports and Money. It's a go bag. It's Portable. It can it contains passports and money just deal with it. It's a go bag. That's what it is okay.
Ryan: But important documents are.
Ryan: I. So after in back in February here in Austin or in texas we had that winter storm and people lost power for like a week and and all sorts of people lost water here in austin and so I ended up buying and the aftermath a generator and. Um, like longer term water storage and not because I'm a prepper but because I you know live through ah but anyway we no I mean we have rain barrels just for collecting rainwater from gutters.
Andrew: That sounds a whole lot like a prepper anyway. Yes, so you have a huge cistern on the roof of your house Now that's collecting rain. Yeah.
Ryan: But we also have like ah 21 gallons of drinking water in these like long-term storage containers. So ah and then I also bought a generator and then the other morning we had a pretty wicked.
Andrew: So Ryan is that a normal thing for people in Suburban Austin to have rain barrels.
Ryan: But short thunderstorm come through with some straight winds that knocked out power took 11 houses like 5 houses on my side of the street and then 5 or 6 houses on the street behind us and we all share a common power line. It kind of runs between the houses in the backyards and ah. So I I fired up after a couple hours I fired up the generator plugged in the fridge just got like you know, critical stuff going and that thing ran all day in twelve hours we were out of power I was like I am so glad I spent this 7 hundred dollars on this generator.
Andrew: And you felt justified and you felt happy that you made that purchase right right? and I feel like you have the same mentality regarding your go bag I feel like you're just dying for the opportunity where you're like oh.
Ryan: Absolutely.
Andrew: It's time and he grab it and go.
Ryan: And I mean I think I'm not like ah I'm not a dooms a Doomsday or I'm not a prepper but I do think that you need to be like prepared for the comforts of modern life to disappear for longer than just a few hours sometimes and I haven't to generate. That's pretty normal. Everybody has a generator. You have a generator andrew come on. Yeah.
Andrew: I Do have a whole home generator I live kind of in a rural area though where it's not especially in the winters that we have up here. It's not unusual for power to go out Occasionally I do have a whole home generator. But I think that's a different level Ryan I don't I don't have any rain barrels around my house.
Ryan: Yeah, oh is it what you can just do yeah all right? This wasn't on our topic list for this this show.
Andrew: And don't have no go bag I don't have any of this stuff. Right? So for anyone who doesn't know Ryan Ireland runs Krafquest Io which is a video training site and it's also a software as a service that he runs for you know his his living and everything and Ryan my understanding is that you have a little bit of a rant.
Ryan: But we get into the.
Ryan: Ah, so yeah, and also just like just some things that I've been reflecting on so I use a I'm not gonna name the company for but I use an ah an email marketing chat tool on like for the site right.
Andrew: Related to your saas that you want to get in and talk about. Yeah.
Ryan: And I have a um, some integration that I wrote there's ah I wrote a craft plugin that basically sends like when somebody creates a subscription. It adds them to that system with like the information about their subscription that way I'm smart like if I email people I email them based on. Actually you know real information whether they're like a premium subscriber or a free subscriber or they're a trial user. So Forth. So I decided that I wanted to move email tools. Um for all sorts of reasons and the first step in that is evaluating like. I need to get my data out and then what I real and and 1 of the most important things to do I don't not sure if you've done this andrew when you migrate an email list out of 1 tool into another is that you bring with it. The subscription status of each contact have they ever subscribed unsubscribed.
Andrew: Sure.
Ryan: From your list because you don't you absolutely do not want to automatically resubscribe them or accidentally email them again.
Andrew: Wait does this have anything to do with the spam I've been receiving from you lately is it related to that.
Ryan: And you mean my well written and carefully sent emails about things I've created.
Andrew: Yes, you're a spam is it related to that is this It did some kind of malfunction you have ah a wardrobe malfunction and no.
Ryan: Yeah I I I read no I read but I reject a reject your description. So I didn't I didn Ant export of my data and I saw it was like oh there's no like subscription status in this data. That's not I mean I and have moved tools before and so I ah contact the company I said hey how can I get the subscription status from your tool I need it in the the default export they say sorry we don't um, we don't include it and this is where things started to go wrong for me. So we don't include it because and then their reasoning I didn't feel like was truthful I felt like it was like a I don't want to say a lie but a a reason that didn't make sense so they said because it's a security issue because if you. If you know their status in bulk that you could somehow then like resubscribe them to to your list or something it didn't make sense so like and immediately my bs detector went off and I was like this sounds like someone just trying to like say basically from a technology standpoint. We didn't. We didn't build this in like it's not part of the export and so we're just go to give you some reason that doesn't make sense so I pushed back and I said well that isn't like I've used other tools exporting this subscription status is standard protocol and in fact, it's you're actually causing or or creating a dangerous situation because you are. Now allowing someone to export their data from your tool and import it into another tool and then actually automatically resubscribe everyone to your list right? because the the way these lists work is you don't when somebody unsubscribes they don't you don't delete their contact unless it's a um. Whatever the eu thing is you know where they request that you actually remove their data right.
Andrew: Yeah, it's a Gdpr so you're telling me that the dump that you get from this tool that shall not be named apparently because you're not interested in public safety for other people that but you're saying that the export that you're getting contains everything.
Ryan: I Don't want I don't want to shame anyone.
Andrew: Contains every single email address that is in your list. Okay, the the reason is bullshit and you know maybe it's part of their retention tool in in order to try and get you to not switch. You know.
Ryan: And right whether they've unsubscribed or not now there is a. So well I right? So I just said like I said this feels like it feels like lock in because now like you know your default bulk now now pretend that I'm like you know. Marly marketing or Mark marketing and I'm not technical and I can't write code. So now you actually are like you're basically locked in because you can't get the subscription status out. So what they so I kind of pushed back and I said you know what? Ah I've never heard of that rationale before for not encoding the subscription data. It sounds ridiculous. Not a security issue and I told them I said I said I think you're going to actually cause more people to unsubscribe or I'm sorry to to resubscribe customers accidentally and and and via in some countries violate the law. Um technically probably in the us as well through through cans spam I'm not sure if it's if it's so legal violation or not.
Andrew: Yeah, yeah.
Ryan: Anyway, um, at the very least it's like a moral and ethical violation to do that to people so they finally like I it gotten like started talking instead of to a support person talking to an engineer on the team and 1 of them finally is huh? yeah.
Andrew: You well hold on hold on hold on hold on Ryan Ryan Did you say I'd like to speak to the manager is that are those words that came out of your mouth in this discussion. Okay, all right? okay.
Ryan: Yes, Sir oh no, no, no, no and I no not at all and I was I was really I was really kind because like I really it doesn't help I want to get my data out and move to a different service. It doesn't help me if I'm mean to them.
Andrew: Yeah, and just a note to everyone out there whether it's someone working a cash register or someone answering the phones. It never helps to berate people that are on the front lines of support because they don't have the power to do anything Anyway, like you're you're just harassing somebody in addition to being a jerk.
Ryan: Right? It doesn't.
Ryan: No.
Ryan: Exactly. So um, the only so so I just tried to be. You know as nice as possible but I was frustrated because I was I was trying to get my data out in a way that's useful and responsible. So 1 engineer that I I chatted with.
Andrew: You know so.
Ryan: Finally said well like you know they said well we don't really see this as like being shady, you know there's also like there's you know there's like technical bottlenecks for us to do that. They said the the subscription status whether someone subscribed or unsubscribed is stored.
Andrew: Come on.
Ryan: Essentially in a different place than the normal contact data which to me basically is is actually okay like that that didn't make me mad What made me mad was that they tried to make it be about something else. What they could have said what they could go ahead.
Andrew: Now Ryan I know you you finish.
Ryan: I Was gonna say what they could have said is there's some technical limitations to how we have these normal exports work. It doesn't it doesn't work like in that way, we're really sorry the only way to get the data out is to use our api and that's what they had said they said you have to use you have to connect to the api right. You have to go get a list of every contact and then you have to iterate over that list and for each of the contacts you have to look up their subscription status and then get it and save it. Um, So of course I'm lazy I didn't want to do that I expected that to be in the tool and.
Andrew: Yeah, they're asking you to write their code for them.
Ryan: So what? what bothered me the most was that it was kind of pushed off as being like a security issue and they gave a couple rationales that were just like b s to be honest, like the the main thing is was their tool wasn't architected in a way to support that I assume maybe by performance or for other reasons and they try to play it off as something else. That's what bothered me the most because I don't like I've done enough code where I've like built things in a way to kind of I mean even with craftquest, there's some stuff where I built it in a certain way to her. It's kind of prevented me from doing some things I wanted to do because I built constraints into it like I totally get it and there's no judgment. There. It's the. It's just kind of like that pushing it off as this thing it isn't like just tell me that it's not technically possible with your tool to do it and you have to use the api. So I probably spent more time being frustrated about it than it actually took me to write twenty lines of python to get
Andrew: Wow. But that's still annoying man like you shouldn't have to write no Python script to do that you know and their their reason really is bullshit I mean I'm sorry like the privacy thing is just silly because again.
Ryan: It's totally annoying it if we ever mean wasn't that hard. But ah it yeah.
Andrew: They're actually almost forcing you to do the wrong thing because you're going to be like Okay, if this is the only way I can get the list I'm going to get the whole list and then everyone just gets resubscribed So it's the opposite of what they're talking about the.
Ryan: Exactly.
Ryan: Right? So let's say you have 20000 people on the total list but 10000 of them have unsubscribed over the years you have actually only 10 then you you effectively have now just started emailing 10000 people
Andrew: And now Ryan I'm not I'm not denigrating you here in any way. Okay, but them saying that this is a ah technical limitation and there are ah you know technical and performance bottlenecks involved in in doing this I mean look.
Ryan: Not be a first
Andrew: I Know you've got a robust thing going on with craftcrest but sorry I know you've got a robust thing going on with craft quest but we're not talking about no million member list here where there should be major performance implications of doing something inefficient. You know I mean it's ridiculous.
Ryan: It? Yeah no, it's it's nine Thousand contacts is all it was so it's not I don't It's It's not that much and a portion of them are unsubscribed. So anyway I ended up the frustrating part was like if you do something.
Andrew: Yeah, yeah.
Ryan: If you build something and there are technical limitations share that while also sharing the like what the workaround is and they did share the workaround but they only share the workaround once I pushed back after them saying there's a security issue. It is absolutely a non-starter for me for them to say that you can't get this. Description status out like it's just and they need to fix it and.
Andrew: It I mean it should just be a left join somewhere right? You would think if everything is in their database in fairness to them Ryan probably given the nature of their tool. They are very likely probably used to dealing with marketing people that have no technical chops at all.
Ryan: Yeah.
Andrew: And normally they probably can get away with saying this and no 1 ne's going to say anything about it. You know.
Ryan: So the end result was I did I ran the final export this morning and you know I think it took whatever 10000 probably almost ten thousand ah api queries or calls. Because you you call you have to call for each page of of the listing and then you have to call for each actual contact. No no, no like I can so I have like ah they have like an app store and you can build an app and that's how you actually like my craft.
Andrew: I Hope they charge you per Api query and you get a huge bill.
Andrew: Okay.
Ryan: Quest the plugin I built for craft it. It was already there so I could just put in the same credentials in my python script and and query everything so it was you know it was enjoyable to like you know work with python again and and and then I kind of got wrote a couple scripts to manipulate and massage the data that I got out. Um, because I really only pulled like email address and stat subscription status and then I you know was able to then import that into my other tool. It.
Andrew: Now I'm not going to force you to out these people ryme. But I would say that just in general things like this I mean I think companies should be mentioned and the reason they should be mentioned is not to shame them is because people listening. You know it's almost like reading a review of something it.
Ryan: That right.
Andrew: Helps to know the limitations of ah of tools that people might potentially want to be using you know.
Ryan: Sure I will I will say that it's not It's not intercom but I will out intercom because I use them as the example I said I said this is I told them I said this feels like this feels like intercom and I said in they're shady as heck because. The reason I call intercom shady is because of their billing practices. They have very opaque billing and they bill you based on. Um, how many what is it? How do they call? What do they call it like the the number of people you you contact in a month or you like.
Andrew: And.
Andrew: Yep.
Ryan: So like your your bill can like vary wildly and you don't have any insight. They never tell you like oh you're at this threshold now. So suddenly you could get a bill that was like 3 times what it was last month it's not them I will call them out because I think their billing practices are shitty I don't want to call them out because like I'm also like you're a developer I'm a developer like we've made.
Andrew: Yep.
Ryan: Architecture mistakes and we we have you know, coded things with limitations or things that we think could could be better So I don't want to out them for that. It's just it was just frustrating and I think about like if I wasn't able to do this myself to kind of. Say okay, you just gave me 2 api endpoints and now I have to go figure it out a lot of people couldn't do that. That's why people think we're magicians sometimes because you know you you couldn't do that. So no, no like non-technical people like non-coder you know, think that like I think so.
Andrew: Who thinks we're meet Magicians Rnna is that true that might be a little self glorification there I'm not really sure that you know.
Ryan: Yeah, totally no, no no, it's not I mean I'm not saying that we are I'm saying people think that because you know we can take this thing and and make it work. You know you haven't worked with enough Muggles have you.
Andrew: I I I think the you know non-technical people just think we're the people that they ask whenever they have any kind of computer related question at all, you know that I mean that's kind of my my take on it.
Ryan: Yeah, fair enough fair enough. Well that's your specialty. But so anyway, that's the rant. The I think the the moral of the story for me. There's 2 pieces 1 is if your tool that you build has limitations then just.
Andrew: I don't know about Magician maybe free consultant is probably the word that I would I would okay ryan.
Ryan: Like own it and say it and don't try to make it to be something else and and that goes for whether someone emails me says hey like you know I I you know played a oh I I played a video at 2 x speed and it didn't save you know. You know my play status like it didn't save it as played and I would say oh no, that's because it's a security concern that people aren't over like you know burdening the site with requests you know something like that when actually you know what it actually is broken and it's been broken and I need to fix it. That's like that's what you should do. Second part is um, see all these things as opportunities, you know I kind of had an enjoyable couple hours yesterday writing the python code and doing something a little bit different than than I do most of the week so
Andrew: No, you didn't I was getting I saw nothing but a stream of invectives coming over my my messenger from you? Yeah, yeah, it was like Tourette's unleashed yeah so ryan what is the of.
Ryan: No, that's ah you talking about over text message pulling it up pulling it up. Let's see well I might use the f word. Maybe i.
Andrew: What is the male version of a karen yeah there you go? What is the male version of a karen it's a Kevin right? What's a chat? No, that's different. That's a totally different thing. You're out of touch with no no chad is the 1 is the guy that all the the ladies want to hook up with so I think yeah, totally totally. Anyway.
Ryan: No No a chad like a pack of chads. No anyway.
Andrew: Whatever, whatever I'm glad you got that off your chest that was about as spicy as a vegan taco. You know, not it I was hoping for a little little more spice in there. You know.
Ryan: I Thank you.
Ryan: Nope I'm consider like a cool and collected person.
Andrew: All right? So I've I've got a couple of things that I wanted to bring up so first of all have you heard of something called conventional commits and this does not have anything to do with a conventional marriage or anything like that now is nothing to do with that.
Ryan: I I have not is it is I was going to say is it a marriageish thing can I can I Google it or am I not allowed to.
Andrew: Yeah, so you can go to conventionalcommits dot Org and this is something that actually my brother-in-law will brower pointed out to me because yeah, yeah, that's my brother In- law man I mean it sucks for him, but it's true.
Ryan: You way? Wait Wait Whoa Whoa Whoa Whoa! That's your brother-in-law I had no idea.
Ryan: Ah, for some reason I Also thought you were the only child you kind of strike me as an only child.
Andrew: No no, he's my brother-in-law because we both married sisters different sisters. Yeah no I got an older brother. Yeah.
Ryan: Oh are you an only child. Okay, okay, all right, got it. That's how you're you're okay anyway, go I Do you know that I.
Andrew: All right? So conventionalcommits dot org is something that my brother-in-law will brower pointed out to me. He works for an agency and he said my team has started using this. You know you might want to check it out and I I went to go look at it and my first thought when I looked at it was that's where it's coming from because I had seen. People using this in a number of library maintainers especially in the node js world but elsewhere as well had seen them using this format and I'm like how did they all conspire and get together and decide to start using it. So all it is is. As in the name. It's a convention for doing your gett commits in a way that you can do them to make them easily understandable and searchable based on the thing that you're working on and the type of thing that it that you're solving and. It's real easy to use. It actually comes from the angular world. Originally I believe but what you do is you just prefix every commit with a summer with a sorry and what you do is you just prefix every commit with a type right.
Ryan: I Yeah so I.
Andrew: So A type for instance would be fix Colon right? So It's a bug fix or it would be feet Colon. It's a new feature that's been added or refactor Colon and it's basically a way of using a standardized convention in your commit messages. To make them more useful when you're searching through or to see exactly what something is doing the other part of it is that you can put an optional scope so you can do fix and then in parentheses importer for instance to denote that the fix applies to the importer portion of the thing that you're working on.
Ryan: I.
Andrew: And then a colon and then just your regular commit message and that's really all it is so it's just standardizing on a few different types that make sense for your project or for what you're using and then an optional scope in parentheses of of what that type applies to so like I said fix importer or feet.
Ryan: So this is.
Andrew: Importer for a new feature in the importer and then a colon and then irregular commit message and that's all it is. It's a very very simple thing but it's something that I had seen people using and I'm like well how did they? How did they all get on the same page and start using this you know and it makes sense that this thing has existed for some time. And it's something that I have started using just very recently in some of the development that I'm doing and I'm just prefixing all of my commits with these various things. The cool part is that it lets you search for stuff in git really easily. So if you are Using. For instance, the scope to denote. Thing that you worked On. So Maybe the importer you can just search for importer and you'll find all of the commits that relate to that and also just by looking at it. You can see that this is a fix. This is a feature, etc, etc. The other cool part about it is in in addition to just providing a more standardized way to add information to the git commit message The other cool thing is there are tools out there that you can use to automatically generate a change log from the git commit messages because now there's a standardized format. Can pull out all of those things out and it can add them to the right heading and you know whether it's ah, a fix or added feature or refactor or whatever it may be I Just thought it was cool and I thought I would bring it up to see if you had seen it and and if not just to give you a a pointer and maybe you check it out.
Ryan: I I haven't yeah I have not seen this it does fit with a lot of these kind of like git conventions and I know that this looks like these might be some like anti. Um, ah git.
Andrew: Yeah.
Ryan: Um, is it git flow is that the camera or no I don no because there's there's a movement to kind of be like anti-gitflow now. but anyway but 1 of things. So ah, but the idea so gitflow is nice because gitflow just works with like normal git. There's no like you're not.
Andrew: Gitflow No I don't think it has anything anything anti-gitflow.
Andrew: Yep, yeah, right? Exactly it's agreeing on a vocabulary. It's you either either you on your own.
Ryan: You're not using like some sort of third party dependency that will then break your repository and this is kind of the same thing. It's just it's just leveraging the the getness of git and right.
Andrew: Or your team agreeing on a vocabulary that will help kind of add a taxonomy or a searchable ah list of tags to your git commits is essentially all it is rights exactly.
Ryan: Yeah, and then if you're if you're filtering like a git log command you can. It's way easier to do that You can pass like a a grep in or or whatever the I have ah a course or bunch of stuff on ah all the git stuff but this yeah this I had not heard of this. This is cool. Um I I don't know if I'm too easyz to do this or not but I dig it. So Why I guess um like scope to me like the the branch name would imply scope. But yeah I could see that's why I was saying maybe its.
Andrew: Um, it depends on how you work. So for instance I'm you know I'm constantly doing small updates to my plugins. You know someone just earlier today said hey you know this this thing's broken or whatever. So I'll just jump in there and do it and I do that right in the develop branch I don't make a branch like.
Ryan: Yeah, so.
Andrew: Fix small 1 line annoying bug you know I just do it I just do it right? then? Well when I'm adding major new features I will create a feature branch but I'm not creating a branch for every new thing. It's just it's so performative like it's just it's ridiculous at least in my opinion that would be something that I would think if you're if you're.
Ryan: Oh really? Okay I.
Andrew: If you're doing that. There's no way you're too lazy to add a little a little bit of text in front of your commit commit messes. You know for god's sake. It does man but when you're when I'm in there and I'm literally fixing 1 little bug that involves a 1 line change.
Ryan: Yeah, but like ah but a tool like Tower just makes it so easy.
Ryan: And her.
Andrew: I'm not making a branch for that I'm just not. It's just not happening. You know you do get There is something called time and there's something called wasting it now arguable if this was something that I was working on a larger team.
Ryan: You don't get you know you don't get charged per branch right? with get is free.
Ryan: Ah, thought that doesn't take that long and.
Andrew: And things really were more involved than okay maybe I would consider doing it if it worked better with the the team flow but doing it with miss.
Ryan: Well, you would have to if if you were if you were in a pull request like workflow. You definitely would have to create a branch for for every single change for sure. Yeah.
Andrew: Right? If you write sure and and that's fine. But I'm not making pull requests for myself generally right? It's not a common thing for me to do well. Some people do I'm just saying like you know you.
Ryan: So yeah, no I don't I don't do that either that seems like a whole lot of work.
Andrew: The cool thing about all of this stuff is you can buy into as much or as little of it as you want I'm just saying what what works for me is when I'm working on major new features. Yes I make a feature branch when I'm working on Bug Fixes. No I don't I mean I'm just committing them right to develop. And in fact, I do that for a very specific reason which is that. When someone reports a bug I show them how they can pull down the fix and test it before I even release it. You know so I said just grabbed from Dev develop just pull it down and away you go Yes, of course that could be done with ah the separate branch for everyone but man I mean it just it sounds way too performative for me like just.
Ryan: Well yeah, and also because of the you know because someone can check out a specific commit like the branch isn't necessary either for for that type of like targeted testing of a change and.
Andrew: Going through the motions for God Knows why? so.
Andrew: Yeah, but also like at least as far as I'm concerned when I'm working on stuff in develop. First of all I'm never committing something that is unfinished or unstable like it's just not something I do right? if I was working on something big enough that that could potentially become a bottleneck then yes that goes into our branch somewhere. Um. But it also then allows more people to potentially try this out before I release it as an official version too by just having that 1 this is the code in progressres branch. Um, but you know like anything depends on the scale of what you're doing in any event I just wanted to bring up this conventional commits because I thought it was kind of cool.
Ryan: Yeah.
Ryan: Yeah, no, it's great I was just looking at why there section in the Docs of why use conventional commits and automatically generating change Logs You mentioned some of these determining semantic version bump um communicating with teammates about changes triggering build and publish processes. Yeah, that's that's all I mean generating change logs.
Andrew: And.
Andrew: Yep.
Ryan: Already seems kind of nice typical.
Andrew: Yep, and like I said I don't know that and um, okay, and like I said I had seen a number of library maintainers using this. So. It's been in use for a really long time and presumably teams have found it useful to to work on I immediately didn't really have any objections to it and found it kind of useful to to do so i'm. I'm using it for now I'm trying it out and I'm seeing how I'm doing I don't know if I'm going to do the automatic change log generation I might I might not it depends like I have certain things that I do in there like I like to link to the if it's solving a github issue I like to link to that github issue. Although actually I'm putting that in the commit message too. So actually that would work automatically so never mind that's not an objection I guess I'm just not really sure if I want to manually write the change log or if I want every commit to potentially generate a change log because there are times where I do a bunch of like really dumb small commits. And I don't want every single 1 of those to be listed. There. You know what I mean like okay like I'll do a commit and then I'll be like fix wrong variable name. you know. like I don't want that in the change log you know
Ryan: Right? right? Yeah, well we'll.
Ryan: So I might give it a shot and cheers to your brother-in-law will for for sharing this very cool.
Andrew: Yeah, so I thought I would bring that up real quick and so I had something else that I wanted to talk about and I actually got a number of things that I wanted to talk About. Um. But you had something else on your list that you wanted to talk about something about there's no magic like what is that or is that just the everyone thinks we're magicians is that where you're talking about.
Ryan: Ah, this is these are so kind of some some rough thoughts but I've been watching um I kind of got deep into watching there's this producer and songwriter his name. Um is oh no no I forgot it. Um, hang on Jack ah Jack antonov sorry I couldn't remember his last name. Ah, he's so there's this producer and songwriter and performer jack antonoff and he's produced for taylor swift he has a band called bleachers. He's produced lord.
Andrew: Don't worry, you just added work for me when I edit the podcast don't worry about it.
Ryan: And I think um, a bunch of other stuff. Anyway, he did this series of videos where he actually broke down like how he created like you know a song 1 of his popular songs like basically with the tools in his studio like I did this on my like old. Legacy drum machine and I did this and I did this and you start to see it come together and it it kind of dispels the idea that that what he's doing is is magic is like you know that it's just like this completed thing you realize like oh like if you do this with other things like people that build. Furniture people. That's you know paint or or do whatever you start to see that anyone that's really good at what they do has a process and and they typically follow that process or use a set of tools or have some sort of framework that they use to create the whatever those the things are that they create. And it really takes like magic out of it. Yeah, there has to be inspiration. There has to you have to be talented. Obviously you have to know how to use your tools but it's not magical and I think the reason I bring that up is because it's ah first of all, it's 1 of the things that I try to do when I teach which is to is to show you know. There's like a framework to how to think about you know, modeling content for a site or writing code for a project that there's not It's not magical but also that it to me it helps people be more motivated and less nervous about taking on something new because if you actually learn the Whatever it is the thing that you want to create like the framework for creating that then it's just down to the details of what you want to create and it's not that you know that Jack antonov has some special powers that allows him to do things. He has a selection of tools that he knows how to use really well and he very methodically works. With those tools and with layers builds up in his case, a song but it could be building up. You know a piece of software. It could be building up a painting. It could be building up anything but you have to know what your framework is you have to be good at that and then it's actually then a very mundane process. Like if you've ever been i' know you've ever spent time in a recording studio andrew when someone's recording an album like professionally um, it's actually really boring's it's it's really really boring. It's ah it's it's a series of people doing a series of things that they're very good at that they do day in and day out to produce.
Andrew: Exactly.
Ryan: Predictable results and and that's kind of what I mean by, there's no magic which is like I think we should think about this especially when we see other people that have done really cool things in any sort of field or trade know that there's always like a process and architecture and structure underneath.
Andrew: Yep, so.
Ryan: Allows them to build that up in a methodical like working person way like they're not just sitting on their sofa and suddenly a you know a perfectly produced song comes to them like they might have a root of an idea and then they methodically work on that and build it up piece by piece right. Using the framework of creation that you know or producing a song that that they know so that's my whole philosophical rant and it's just something I've been kind of thinking about a lot so still kind of raw ideas around that but that's.
Andrew: 1 you could almost summarize that by saying that success is a ten percent inspiration and ninety percent perspiration right.
Ryan: I Guess kind of with the same you can jam that right into that same paradigm for sure.
Andrew: But in an analog to that for the kind of work that we do I Know there's a lot of some people have pushback against you know all the frontend tooling that is there but I kind of consider that to some extent the Framework. And the the methodologies that allow you to build these really complicated. Really amazing things that if you didn't have that it actually would be really hard to do some of these amazing things. So Yeah I would I would definitely agree with that I think that's ah, a useful thing and you you reminded me of something like quick tangent ride quick tangent right.
Ryan: Sure.
Andrew: When yeah, you were talking about the um recording studio stuff. My kids were telling me about the fact that 1 of their teachers when they were coming back from Spain got like hauled off into a room with you know people with machine guns or something like that. You know we're interrogating her.
Ryan: Oh I've been in the interrogation room go ahead.
Andrew: and and I was just like well all right, whatever something doesn't sound quite right? like I don't really see Spain doing that very often I was just like you know, maybe she had something in there. She wasn't supposed to bring back and then it reminded me that I had something for the kids I said you know you can get into trouble if you're bringing stuff. Back from a country that you're not supposed to bring and I said there's a a movie that was made out of this called midnight express have you ever heard of that. It's an older movie. Okay, so it's a good movie. It's a good movie to watch and it's basically so about a guy that he's trying to smuggle drugs I believe out of.
Ryan: I I have yeah I don't know if I've ever watched it though.
Andrew: Into or out of turkey or something like that ends up getting caught and spending whole bunchs of time in prison and there's a whole lot of stuff that goes along with it and I said to my and I I thought I had this really cool moment where I was going to impress my kids and I'm just like you know what? there's this movie called Midnight Express and the movie is based on a book.
Ryan: I by Billy Heath Wow Wow I.
Andrew: And I have that book for you signed by the guy who wrote it by billy hayes billy hayes is the 1 who wrote. So um I went night and my kids look at me and I know you're not going to believe this but sometimes I have fun like making things up and exaggerating things just to kind of mess with the kids a little bit I know that sounds totally out of character for me. But it is something that I do sometimes and so they kind of looked at me with that look that I get there. they' not sure if I'm telling the truth right? So I go and I I pull the books off the bookshelf and I open them up and I say look right here. It says to tyler from billy hayes and then another 1 to Jack from billy hayes right? and they're like.
Ryan: Nice.
Andrew: How did you? How did you know this guy like how did this happen and I'm like oh well yeah I used to play poker with billy hayes like the guy that and he you know he signed it for me and everything. Yeah yeah for real and they thought for a minute and this is where I thought I was impressing them and then my my older son was just like wait a minute so you have.
Ryan: You no kidding Really, that's awesome.
Andrew: A book signed by a criminal and then he was just like wait a minute so you used to play poker with a criminal like at our house like what I'm just like oh man that didn't go over the way I was hoping it would you know.
Ryan: Ah, yeah, yeah, there's that many times I I um I do a lot of like book pulling off of with the shelf situations at home and like I could probably count the times on 1 hand where.
Andrew: Yeah, so.
Ryan: Where that ended up with anyone in my house being impressed with me but that's cool that you had the books did you have have you forgotten about them that you bought those or or that now that you bought the all right right? right? that makes.
Andrew: I tried man that was 1 of those things where you know midnight express is not the kind of book you're going to give to a 12 year old to read. Not only is the material not necessarily. Yeah I don't want to say it's gonna be our rated but it's gonna have. Themes that maybe they don't really need to know about and then also it's just not the kind of thing they'd be interested in Anyway. So I just had them and I was just like all right? Well you know I'll give those to them whenever I think they might actually be interested in in reading it, you know and in in any event. So.
Ryan: I.
Ryan: Yeah, very cool. Yeah.
Andrew: 1 of the other things that I wanted to talk about is we have talked a bunch about vet that build tool speaking of you know Frameworks that you can be using to to build your stuff which I think is super awesome. I know we talked about it here and we've done interviews and I've been using it for a number of things I ran into a bug. Recently with vet and the issue is well let me take a step back the way that vet works is it sort of considers the directory that it lives in sort of like a public web server directory so when you reference any file in vet. It's just relative to. The the route where it is and it literally can be thought of like the nginx. Um web directory or the apache public html directory that's kind of how it works from a dev server point of view you spin it up and then you can just link to any file that is in its directory and it will just serve it up. And it does that for stuff that's in node modules for stuff that's in your source or any of that kind of stuff I think that's all well and wonderful. But I I like to organize things a little bit different I like to have my source directory outside of the build chain I call it and I like to have put that somewhere else and.
Ryan: Button.
Andrew: And so what I had been using was a sym link from the root vet directory to where I keep my source and everything was working great. But then with there's some kind of a regression in v 2 6 something I don't even know what version it was in.
Ryan: Right.
Andrew: Where it would resolve the simlink and include that in the path to the file right? which is really not what you want you want the unresolved simlink so it could just be like source Js App dot Ts or something you don't want um dot dot Slash. My cool folder Slash Source Slash Js You know what? I mean which is what it is resolving it to so I did the right thing I filed an issue I created a minimum um reproducible repository for them so they could work on it. But the V team is super busy.
Ryan: Right.
Andrew: So I said to myself self. Why don't you go in there and try and fix this yourself. You know like why don't you go in there and see if you can't figure out what's going on and and fix it and and give them a pr right? So I started down that road. The issue is that when you do an npm install of vet. You're not getting everything that's in the Github repo
Ryan: Yeah I.
Andrew: You're getting kind of just the build results is all that is in there. So the problem with that is it makes it really really difficult if you're trying to debug vt itself because you are dealing with minified concatenated javascript that has function names like d.
Ryan: Right.
Andrew: And parameter names like a b and c. You know like it's just not an easy thing to try to debug so I said all right? Let me try and figure out what I need to do in order to do this correctly. Um, and it turns out that vet is using something called pnpm. Which is a an alternative ah process or sorry package manager which is an ah which is an alternative package manager to npm essentially and it it has some what you would expect and ah features it's Faster. It's more efficient. It supports mono repos really? Well which is I think 1 of the reasons why the vet team is using it and mono repo is for anyone who doesn't know they're basically just a number of packages that can be pulled in separately but exist in 1 repository right? So it's just 1 big kind of thing where they go. And in order to do this locally. What you have to do is you pull down the whole you git clone down vet and then there are a few steps that you have to follow in order to get it up and running you have to you have to do some stuff with you know. Install and then link and then use a whole bunch of stuff and me being the masochist that I am I said you know what I'm going to build a dockerized way of doing v dev. I'm going to build a dockerized way of doing vet development in terms of development on vet itself. So that's 1 of the things that has been occupying me in recent times ryan is that I've been spending some time trying to build this thing and I'm trying to build it from the point of view of it's not just me I want to make something that is super easy. That if people want to work on vet and contribute to it or whatever they can just start this ah debug docker container up and everything will be set up and and ready to go for them working on it. How crazy am I to be doing this ryan what do you think.
Ryan: That's that's cool that you're slightly crazy is this the same is this. This isn't the project that you're trying to to lure me into working on. Is it.
Andrew: Yeah. No, that would be make too much sense that yeah I would have only 1 side project that pays me nothing. Yeah, that would make too much sense. But that's something that I'm hoping to to wrap up relatively soon.
Ryan: Ah know. Ah, okay.
Andrew: Because I think I talked with Matt gray a little bit because there there are a couple of sticky things in terms of what I wanted to do I want to make it as sort of insulated as possible that people want to have to know anything about anything and it it will just kind of magically work and there were a couple of additional steps that.
Ryan: I.
Andrew: Wasn't quite sure the right way to do them are but I think I got that ironed out and hopefully I'm going to have that done soon and then finally speaking of Meta work. Finally I can then move on to actually fixing the thing that I wanted to help try to fix and ah you know I don't know if I'm hoping that they fixed it before I have or not at this point. You know what? I mean it is quite a journey but I think that this could be useful like vet is something that long term I probably am going to be interested in doing stuff with. So if I have this set up I think that will actually be pretty good. You know in terms of me being able to.
Ryan: Ah, ah, it's all about the journey. Yeah.
Andrew: Plum into the internals or ah to write plugins for it I've already written a couple of vet plugins and then also just occasionally find and fix bugs maybe at some point even contribute an additional feature to I don't know.
Ryan: Yeah I mean that's the that's the only way really to be a contributor right? is to get the the local development environment set up and working and then.
Andrew: Yeah, and to be clear. They do have a contributing guide that tells you the steps that you need to do to get it up and working but I have a a setup where I don't install any of this stuff locally I don't have node installed locally I don't have composer installed locally like none of it. So of course I'm like you know i. I'm not going to install node locally just to do this so I decided that I'm going to dockerize it so I could do it kind of my way I do have an article coming on that by the way ryan of how you can and this is really timely with people getting their shiny new m one macbook pros or Macbook you know whatever.
Ryan: Very cool.
Ryan: You Yeah, including yourself right? so.
Andrew: Where you you can just never install brew. You don't need to install brew for anything at all, You don't have to install anything on your machine locally and you can just use the the docker life and away you go.
Ryan: And that sounds appealing to me. You don't have to worry about every time you get a new machine. You have to rebuild ah your environment over and over again.
Andrew: Yeah, and the basic idea is you can you set up aliases So when I type composer install What it actually does is it spins up a container that has composer in it does all of the work inside the container and then the results are dumped in the file system and it's done.
Ryan: It. So it's slower. But.
Andrew: And it's not no I mean because what happens is when once you've done it once it caches the the Docker image and it is shockingly quick to spin it up and do it. You would be very surprised.
Ryan: It cool I mean I know from working with the the docker setup that you have for the kraft boilerplate is that it is nice like if you try to run like 1 of the make commands that you have it will spin up the the containers if they're not already there.
Andrew: Yeah, yeah, and it's kind of like that the the difference is that for these these kind of 1 ne-off commands it's not doing it so in my docker setup the lengthy part of that spinning up is actually that it does a composer install and an npm install every time you spin it up.
Ryan: And yeah, once they're running in.
Andrew: And it's doing that intentionally just to make sure that everyone keeps their versions in sync when I'm working on teams but the actual overhead of spinning up. The container is is very low. Yeah so it it works really nicely and I just need to find time to to finish that article you know.
Ryan: Yeah, yeah, very cool.
Ryan: I Think you have all the time in the world.
Andrew: Um, running out of time I Wish well speaking of all the time in the world and speaking of go bags which is something that you might want to grab if you're gonna go on in it. An adventure I want to drag you on an adventure Ryan where we work on something that is.
Ryan: Gosh Yeah, okay.
Andrew: Out of our comfort zone and there is no money. There's no fame and there is no glory. What do you think.
Ryan: You are you trying to say um, that's what I'm motivated by are those the 3 things pay money and corey yeah, okay, um, yeah, let's.
Andrew: I Mean those are those are reasonably motivating factors for lots of people. Yeah.
Ryan: Ah, let's go.
Andrew: I and I can prove it actually Ryan I mean you're kind of disparaging me and saying I'm shallow but I can prove it. So would you do all of the work that you do on Krafquest for free.
Ryan: And ah yeah I would I totally would.
Andrew: Liar Liar I'm staring right into his eyes everybody he is lying so hard I'm not saying you don't enjoy it there. There are jobs that people do that They very much enjoy doing. However.
Ryan: Ah, why do you say? I'm lying though, it's yeah.
Andrew: If they were not paid to do them a lot of people wouldn't do them. They would find something else to do because not because they're shallow because you you need a certain amount of money to exist. You know it's just that's just life.
Ryan: And well yeah, ah, that's true I feel like there's a little bit more nuance to it than that. So What's your what's the adventure. Are we going like bike packing across the us are we we to go on like some sort of long trail. Trail Run and try to get the Fkt. What are we doing.
Andrew: Well I'm gonna give you the pitch real quick I'm I'm not going speedwal with you because I think it's a silly sport So I'm not gonna do that. Well you're you're a speedwalking champion. But yeah, anyway, that's irrelevant to what we're talking about here here's what we're gonna do. We are going to build.
Ryan: I I don't speed walk. But thank you go ahead.
Andrew: Ah, browser extension not just it's going to start as a chrome extension but it's going to be built in such a way that there will be common code and that we can also make it Safari and firefox and whatever other browsers that we decide to support right? So it's going to be a extension and it's going to be. Twig debug tools is what it's going to be and here's the way it's going to work. It's going to do a couple of things for you. So 1 is it's going to give you introspection so you view your developer tools and I'm just going to use chrome you view your developer tools in chrome.
Ryan: Ah.
Ryan: Right.
Andrew: And just like with the vue developer tools there. There will be a twig tag and just like with the vue developer tools. There will be a twig tab sitting there you click on it and you will see all of the blocks that were rendered on the page you will see all of the includes that were on the page. And you also will see the entire context context in twig parlance is all of the variables that were used on the page so you will have introspection so your template is not going to be this kind of black box where you don't know what variables exist in it and what you can be doing with it.
Ryan: Right.
Andrew: You're actually going to see all the variables that are in there and you'll be able to drill down and inspect them so you'll be able to see on this page. You know here's my entry and here's the data that's in here and here's the Index loop variable and and all of the the craft and plugin injected stuff will be there as well. Just like it is in a lot of other developer tools for other frameworks where you're actually able to introspect. You know what is actually going on because I think a lot of people especially when you first start out, you're starting out with twig and you write stuff over here in an editor and you have no idea what exists on the other end I mean.
Ryan: That right.
Andrew: Have no idea what variables are available to you to be working with or anything like that and then at some point you discover the percent Dd or the dump command and you start dumping variables to to see what's in them and that you know I mean it works but it's kind of a lame experience right? so.
Ryan: And.
Ryan: Yeah.
Andrew: And then maybe it's somewhere down the line. You discover the special variable underscore context and you do a percent dd context or yeah or dump the context so you can see every variable that's in there but I feel like you don't get there for a very long time I think there are lots of people that work with twig. Every day that have no idea that you can do that to see the variables that are in there. But also it's just not a real fun thing. Yeah exactly you have no introspection. That's what it is the other part of the equation that I would want it to be able to do is you should be able to.
Ryan: It. It's like it's like working with a ah very narrowly scoped flashlight and you're just kind of moving it around. Yeah.
Andrew: Click on any block in the inspector and it will highlight that block on the page all right? So we'll show you This is all of the stuff that came from the block content or or whatever and also you will be able to hover over these blocks if the developer tools are open. You'll be able to hover over the actual.
Ryan: So okay.
Andrew: Html That's in your webpage and it will highlight what block that all comes from as well as having some performance metrics you know showing how long it took for that block to render and a bunch of other stuff that would be really useful and this is something that my template comments plugin sort of does it adds comments to.
Ryan: I Yeah, that's what I was already thinking about? yeah.
Andrew: Yeah, it adds comments to the actual source code so you can view the source and you can see okay, everything bracketed in here came from this block but it's not as fun to work with It's not as nice to work with as being able to just hover over something on the page and see where it comes from and. I think that this is something that is really useful like I've had it happen both on my own projects but more when I'm taking over a project from somebody else and there'll be an error somewhere and you were like I have no idea where the html that is rendering this thing that is wrong is coming from and you have to plum down through all their templates especially with. Content builders to to find out where all this stuff is so that's my pitch is that we twig is this thing that there are no developer tools for it whatsoever and I think the having the introspection of seeing the context being able to look through the variables and then also seeing the blocks. Getting some performance timings on them I think all of these things would be useful and I want to do it in such a way that it probably will be using the protocol that vs code uses for its language. Servers. So you know it's going to have to use some kind of method for communicating. Between the extension and the front end to get the context and information I figure it might as well be done using a standard like why? Why reinvent my own standard to do something that other tools are already doing and that would mean that there would it would be written to a standard so that if someone wanted to use this chrome extension. With symphony or with drupal or with anything that uses twig. There would be a standard that they could write against so that they could do the their cms or backend specific part of it and it would all work with the front end. What do you think.
Ryan: So I think that sounds really interesting and and youre um, but I'm I'm down for sure. Ah, you also said like ah maybe like a browser extension for Safari things like that as well.
Andrew: Yeah, yeah I mean the basic idea. Um, yeah so I have not written a chrome extension or a safari extension as far as I know I don't think I have.
Ryan: I haven't I don't know if I've written a Safari extension I've definitely done chrome. Okay, but.
Ryan: So are Safari extensions swift I actually don't know are they javascript as well.
Andrew: No, they're not I mean and all of this stuff is very very similar. That's the nice thing about it is that the way to do it the way to hook into all the browsers is a little bit different but at some point you can have a whole lot of common core code like for instance, the.
Ryan: I yeah.
Andrew: Web socket that would be opened for the language server would be something that would work in all of them and the html that you use to because in the developer tools. The stuff that's displayed down. There is just html and you can include any arbitrary javascript or css that you want in there and it just renders it as a html page.
Ryan: And.
Ryan: Right.
Andrew: So There's a whole lot of stuff that is really common and I've looked at some other developer tools and some other extensions and what they do is they just separate it out by browser and then they have like a common directory and the bulk of the the work goes into that and then you just have whatever whatever it needs to be browser specific. To hook into their developer tools.
Ryan: That that sounds like fun. It's it sounds like it's in a lot of areas that I haven't worked in so that's that's appealing. Yeah.
Andrew: That's the point right? I mean that's really the point is that it would be something that is you know it's not entirely out of our comfort zone because it's all just Javascript html css but it definitely is doing things in a way that we're probably not really doing every day.
Ryan: Right.
Andrew: And ah I don't know I think it sounds fun and and more importantly I think it also sounds pretty useful. You know.
Ryan: I I think so and I've had ah a few browser extension ideas. So it be. This is a good much simpler than this so this is a good a good place to be um I'm in. So maybe we can update everyone in the next standup for our future standup about. How it's going I am.
Andrew: I'm not going to commit to that. Ah, but I think it's a cool idea and I think it might be fun to do now Now. It's a matter of either finding the time or if someone wants to finding the funding right? I don't think that's going to happen like I think that's it.
Ryan: Oh yeah, we well we could we could spin up the Github repository and and then once we have something that works. You can always have so github sponsors right.
Andrew: Pretty much a zero point zero percent chance of happening.
Andrew: I Guess I don't.
Ryan: Or we could start like a Youtube channel and like tell jokes and have Patreon account. So.
Andrew: Well, you know this is this is basically just therapy.
Ryan: Ah, okay, yeah, no I'm I'm down so you um, get in touch with my people and we'll get something on the calendar.
Andrew: Yeah I don't have any timetable for it. It's something that I've been thinking about and it's probably because it is something that interests me it. It probably is going to be something that I work on and not just like this idea that is floating out there. But I do have a ton of other things that I'm working on too. So.
Ryan: Yeah.
Andrew: No, no eta. But I thought it sounds cool and I wanted to kind of talk it through with you and see if you had any interest to all right? you heard it. We got commitment from Ryan I think Ryan is just interested in doing this because.
Ryan: And I'm interested count me in.
Andrew: He would like to use his go bag. This is something he can just grab and go on and Adventure. So I think he's very excited about that. But that about wraps it up for another episode of the devmode fm podcast if you enjoy the show make sure you subscribe tell a friend drop us a review. Really would appreciate it, especially those five star reviews on Itunes. So. It's really big for Discovery for the devmo Fm podcast I'm Andrew Welch you.
Ryan: I and I'm Ryan Iron I.
Andrew: So you are in you set it onair. It's official. You are in.
Ryan: Yeah, no I want to I want to do this I don't get to do I feel like I work on my own stuff so much and it feels selfish.
Andrew: Yeah, yeah, and I did I did discuss this with Ben croker too to see if he would be interested and he he said that it was getting his.
Ryan: Oh.
Andrew: His gears turning in terms of this is something that could be extended to do sprig and our our idea for that was that it would actually show you the diff of stuff that is coming in from sprig. So as it comes in it would like fade in.
Ryan: Yeah, yeah.
Ryan: I yeah.
Andrew: You know it would show like a background color and then you'd be able to see what request pulled this in from sprig and you'd be able to see the whole diff of of the page and all sorts of really cool stuff. So.
Ryan: I So the only the the extension real quick I have to help but a call the extension that I was have been thinking about building. It's been on my list is if you're on. Um, now mean you won't put it in there.
Andrew: So should I stop recording is this proprietary information.
Ryan: But if you're on like the K craft docs that it gives you links to relevant tutorials elsewhere and then if you're on yeah, that's basically it.
Andrew: Wait a minute wait a minute wait a minute you're writing a chrome extension that lets you hijack K Crafts Docs and and feed them into your videos is this what it's like is this some kind of like marketing clickjacking extension.
Ryan: You no no, no, no, no, no, no you you you install the extension and it's it just gives you the help or help information. So if you're on the Docs and you're like oh like like I want to actually see someone actually implementing this or see someone write about this then it gives you the the links off to like.
Andrew: Right? So links directly to Krafquest Io I got it all right? We we got where you're going with yeah all right right? right? All right? so.
Ryan: Other tutorials actually there or and N y studio if if you want to pay me per per quick. Alright.