Ep. 12 - The Sad Accountant with BJ Szyjakowski | Developers:After Dark

You should see the notes I have. It makes no sense. Like, if you're looking at it, it's misspelled. It's all shorthand and it makes no sense. But in my mind it's like it all comes together like, like a beautiful, like, poem. It's amazing. It's like haiku. But. Hello and welcome. Friday 21st February, and we are here on episode 12 of Developers After Dark. With me, as always, are Dennis and AJ and if you haven't, if this is your first time viewing or you haven't caught up on any of our previous episodes, you can find them all on the HubSpot Developers YouTube channel. So you should definitely go and check that out amongst all the other videos that are there. You don't just, don't just go for me. Don't just go for me. I know you love me, but don't just go for me. So that would be at HubSpot Developers, if you're on YouTube, just kind of poking around also too, just to pay a couple of bills, you should definitely, if you haven't already. We probably said this almost every episode now, but the developer Changelog is something that you're going to want to subscribe to and that's going to be@developers.HubSpot.com changelog. One of the other things too. Dennis, let me ask you, how do you feel about your dev skills? Are they rusty, like a lawnmower in the garage over winter?

Yeah. Wow. You know me well. You know me well.

That's.

See, I do, I do. And do you think like, Python's just a snake in The Amazon or JavaScript is just how they write your name on the Starbucks coffee cup or Ruby on Rails being a grunge band in Seattle is. It is.

If you could get me some sort of resource that could help me really understand what you're. Actually, I have no idea what the words you said were, so, you know.

It'S funny that you mentioned that because there is something, there's something it says, little known secret. Maybe people have heard of it, maybe they haven't, but it would be the HubSpot Academy. And if you go to academy.HubSpot.com you will find certifications, resources, things to take that rusty lawnmower and make it sharp, be able to mow the lawn 10 seconds flat. Don't take my word for it. You should go there, definitely. So I feel like you just have.

A list on the side with like comparisons of things to just rattle off.

Oh, it's amazing. It's like haiku. But that's not what you're looking at when you're looking at the notes, I'll tell you that right now.

What was that movie? It was a sling blade about the guy with alarm.

I'm talking about.

No, no, this is all. This is like your generation too. I, I will find links and we'll, I'll. I'll add to. It's about a guy with a llama or who has.

That's fair. That's fair. Yeah, I know what you're talking about. But I don't know if that's exactly.

What.

Sounds like one of those like OG Blockbuster finds, you know? And you're like, that is a fail.

And I can totally respect that because I used to work at a video store for years. So that's how, that's why, that's literally Dennis. That's where that whole kind of issue of mine comes from, where I'm stuck in a certain. I don't know if he is aware, but like in one of the episodes we just. I kept like making movie references and like a quiz and movies, but it was all stuck in like this, this like four year, three year span. And that's all I know. Like any other movies outside of that I was completely oblivious to. And Dennis made the point of pointing that out. Kindly.

Susan Sling Blade.

Yeah. Billy Bob. Okay. Yeah, that makes sense. That makes sense.

Oh, Nick, by the way, in celebration, it's actually developed After Dark. I've decided to crack open a athletic brewing company. I'm not supposed to say titles on that.

Right.

So I. I'm drinking a beer here.

Nice.

Okay. Okay.

Non alcoholic.

But you know, I'm trying.

Right?

That's.

I was gonna, you know, I didn't want to ask, but I was, I was, I wanted to ask and I was just kind of like, it's. I mean, it's after dark. I mean, we could pretend, but we're live. I mean, anyone with a watch might be able to call us out on this slightly.

But yeah, it's not quite after dark over here either. You can very much see that these, this is a very intelligent, very, very sophisticated lighting setup I have going. It really is nice.

Yeah.

Any lights? Better than none. My. I have like. I literally had to go buy light because there is no light in here. And it was just like, it's horrible. It's absolutely horrible. And everybody be like, yeah, after dark.

That makes sense.

Because it's dark where you're at. And I'm like, no, it's like 2pm or it's like noon. I'm like, it's just. There's just literally no light in this place. So it's just one of those things. That's why the name fits so well. But. But one more thing I wanted to mention too and there's actually. I was only aware of one but now there's actually a second one coming up. But for D Hugs Dennis, there's obviously and this is going to be a slightly. A good transition here, but you have coming up on the 27th that would be taking HubSpot to the next elevation, a react powered showcase. Right?

You get it, you get it.

Yep, yep.

That's with our star reviewer bj. So I'll let him talk all about that today. And then on the. Was it the 14th? Does that sound right?

In that area there's a March 13th.

13Th. Yeah, 13th of March we have the one with Replit where we're going to start. I'm going to start a series on AI and development and disruption and what these people have their opinions about. Replit say, well, it's an IDE that you can basically type in what you want to make and an app pops out and it's not all true and I want everyone to be aware of that. I want them to state their case and how this is like how development is going to be for the future. So show up, ask questions, be thoughtful, things like that.

I literally was in repl it and I basically said like create me a Figma plugin that has like two options and then literally pastes that option to the canvas or whatever when you select it. And it did its magic. It did a little bit of talking to itself and it was like, oh, this isn't working, I need to fix some stuff. And then literally was like, just go ahead and load the plugin and sure enough, boom, done. I mean it was just like, you know, a triangle in a square. But I was like, hey, I can.

Build off of this at least.

So we don't need BJ's anymore. Yeah, put me out of a job.

Thanks.

Thanks for coming.

Appreciate it.

Thanks for being a guest. It was nice talking with you. But Dennis had mentioned that there is a. With the previous DHUG that we were talking about with Elevate that there is a. There is a correlation to our guest. So I will let him tell everyone who he is and what he does.

Is that me go for it. Yeah. So my name is bj. BJ Schkowski. Because I think my last name might be useful somewhere and it's just a mash of consonants slapped right next to each other. I am on the Content Assets team here at HubSpot, and content assets team is kind of in charge of all of the default CMS assets. So if you love it, I'm the guy to talk to. If you hate it, talk to someone else.

Yeah.

If you made it, it was made before I joined the team. Spending a lot of time building out, Elevate and playing inside of all the new, like, REACT pipeline stuff that's kind of going on and. Yeah, having a lot of fun doing that and hanging out with y' all outside of this context.

Excellent. Well, why don't we get things rolling a little bit and tell us just kind of how you started? Because everybody has that, like, that point in time, right, where they're exposed to something that they say to themselves, well, this can be. Well, this can be a career. This can be something I could see myself doing in the future. With regards to everything that you've done up to this point, where was that moment where you kind of saw development and you saw engineering and you saw these things as something where it's like, hey, that's something I could see myself doing as a career.

Yeah. Yeah. Do you want the long story or the short?

Go with the long story. We want to tell the story.

Yeah, we're going to go back. We're going to go back. So, you know, I think my first, like, introduction to, like, HTML, CSS and stuff like that was, I think, in middle school in, like. I forget what the name of, like, the elective was called, but it was something along the lines of, like, exploring the web or something like that.

Design 101.

Yeah.

How fast. How fast did that go out of style after you did it? Because, like, I remember taking something and I. I think it was, like, right before college and it was like, it was obsolete, maybe.

Yeah, right after. Yeah. I mean, I have no recollection of what the heck I even did in that class. You know, like, I remembered, like, what the project was that we worked on, but we had a full semester to, you know, try to build a website. And, like, that was pretty much it. And I had no idea what I was doing. I was just copying and pasting from other people in, like. I just was like, oh, this is, like, kind of cool. But it was just HTML and css. Didn't touch it again until many, many years later. But I remember that being kind of cool. And I remember at that point being like, well, interesting, and went to college, didn't know what I wanted to do. Pretty typical as one. Yeah. Like interested in like music stuff. I was interested in art. Kind of wanted to do something along those two lines. But then I actually enjoyed like playing music and enjoyed like drawing and animating, stuff like that. And just heard a lot of horror stories about people, you know, going to school for something that they love coming out of it, just hating it, never doing it again, you know.

Right.

So I figured like going to school for something generic would be like better. So I went to school for accounting because that was the like hardest business administration like major that we could do.

Is it accounting?

Accounting, yeah.

Left field. I didn't realize, I didn't know it was coming. Okay.

Yeah, yeah, I can, I can do your taxes, but yeah. So I really enjoyed like accounting work. Like I enjoyed like. It's basically similar to programming. Right. It's just a lot of logic. People think it's like a lot of math, but it's just like at its hardest like finding percentages of something and multiplying that on something. But you know, you always have like check figures and it's like just figuring out problems. So like that's kind of fun. And fun fact, if this is one of the main things that I remember from my accounting, my accounting days at school is that if you are an accountant for the FBI, you get to carry a gun. So you know, if you, if you want to carry a gun and not shoot people, you can be an accountant for the FBI. You'll be sick. Anyway, I really didn't like people. This is what it came down to. A lot of the people that I was working with, you know, I was during my like college career I was. And a little bit before I was working at a climbing gym. I was like a big climbing bum for, for a long time. Started climbing when I was three at like our local gym here in Milwaukee and was just like showing up to class in like tacos and shorts and like sandals and it's just like this laid back personality and everyone else in my classes were like suited up and like business attire and I'm just this like outlier over here.

Let me ask you, what was the, was the draw to climbing because of the fact that, I mean in a certain sense it's kind of an individual type of. It's not like a team type of thing where it's like, you know, an entire. It wasn't more like because it was a solo effort when you could do climbing. So you didn't have that because like I have the Same thing where it's like, I. I'm not. AJ can attest. Some people could call me not a people person, you know, to a certain extent. So, like, there's things I'd like to do where it's like, I could just go off and I can do this, and this is, like, kind of peaceful for me. Did you find. Is that. Is that kind of what drew you to climbing?

Not entirely. So, I mean, I started so early in my life that I had, like, zero. It was just, you know, like, my dad was into climbing. So, like, then I started climbing and, like, you know, I don't even know who I am at that point, like, why I'm doing the things I'm doing. However, like, I think once I got to, like, you know, high school and into college and, like, who I was was starting to, like, settle in or come out a little bit more, that was definitely, I think, a part of it. You know, I'm an only child, so, like, I think up until relatively recently, like, a lot of my interactions with people and, like, how I, like, viewed people had to do with, like, activities that we were doing together. And, you know, I'm all about team sports. I played soccer for a long time. But I. I think climbing is just something because it's so individualized, like you were saying, it's something that you can kind of just progress and, like, make your own and do whatever you want with it. But I wouldn't say necessarily that the draw was that it's like a solo activity.

So now most. Most people don't start it at three years old. I gotta ask, just because. Because you put. I remember you had mentioned that you were doing it when, you know, you started when you were three. Like, that had to have been hell for your parents. You know what I mean? Like, I remember with my kids at three, like, running around, I was just like, don't touch anything. Don't climb on anything.

But, like, still got, like, the pool noodles out on the edges of the table type thing.

Yeah, yeah. I. My dad started me, like, rock climbing and skiing, like, when I was around three. And that's largely because that's the stuff he was doing. So he. He taught classes in, like, our little hills here in Milwaukee or around, you know, southeastern Wisconsin. Yeah. And, you know, while he was teaching classes, he would, like, bring me out with them and, like, he taught climbing classes at the local gym here on Saturdays. So while he was teaching classes, I would just be, like, kind of climbing around. So. No, I mean, I'm. I'm sure at some point it caused some kind of panic, but I think it was expected. That's great. I think it was too chaotic. Yeah.

So are you more of a fan of the indoor climbing or are you more of the, like, outdoors, like, let's go scale a mountain kind of climbing?

Yeah. So I mean, that's just the interesting, like, conversation in and of itself with me is like, I worked at the climbing gym for like eight years. And while I was working there, I was really gung ho about climbing in general. So I didn't really care what it was, if it was gym climbing because it was easy, like easy accessible, easy. I was fine with that. Spent a lot of time in the gym, the weekends during, like summers, I would definitely try to get out outdoors. So a lot of climbing at like Devil's Lake and like other places in Wisconsin here. And then like, of course, like larger trips out to like Yosemite, North Carolina, West Virginia, California and stuff like that. And they all, they all have their.

Own.

Their own appeals. But I, I definitely don't fall in the camp of like, you're only a climber if you do, you know, if you. Boulder V12 and like, you know, or pulling hard, or you're only a climber if you're like a track climber outside placing your own gear. No, like, you're a climber if you think you're a climber. It doesn't matter.

Yeah.

I feel like that's the way with website development too. Right? You're a developer. If you're actively trying to hammer out code, you're a developer, you're in the developer mindset, you're in their shoes right there. So you may not be a skilled one, but you're doing it.

Yeah. The reality is that we all start there and we are all also there in comparison to someone else who's miles ahead of us. Yeah.

Because you can even start a new language and you're right back to square one, you know, if you're not understanding. So it's. Yeah, I always found that to be quite, I guess, odd is the way to put it when people would be. Have that mindset right, where it's just like, oh, you just don't know. Or you just. It's like, no, you're still a developer, you're still this or that. Just even if you're going through the learning process, which, you know, it's not easy, but like, you have to give credit for people that do it. Right. Because there's some people that'll be like, yeah, I'm not, that's too much. I'm not doing that, you know, so. But yeah, no, that's, that makes perfect sense. From there though, you kind of, that's where you kind of shifted into more of a part of your career. Shifted into things where you started touching on HubSpot especially right after that. Then.

Yeah, yeah. So I ended up getting like just kind of burnt out there and with climbing in general. So then I kind of took like a little step back and was just kind of like throwing darts at the board just to see like what stuck, you know, I was like, well accounting is out of the picture. I graduated like down graduated without that. So I didn't need like a high paying job right away. So like, you know, I wasn't in any hurry. But I started like. I guess my tactic was like, I don't know what I'm going to do or like what I want to do. So I'm just going to pick something and see how it feels and like you know, let that kind of guide me. So I knew that I enjoyed like writing so I started doing like some freelance writing and did not apprice myself. Absolutely hated it. So I was like, this isn't working. And then got in contact with like a marketing agency in the, in the Milwaukee area here. They were a startup at the time and they, I was like, do you guys need any content writers? And they're like, nope. But we see you have a degree in accounting. Do you want to do something like data analytics work for us? And I was like, as long as you know, I don't know what that means. Sure. Like I'm comfortable in spreadsheet and I can like do math so like that's fine. But yeah, they, they were like evangelists of HubSpot at the time. And I think this is back in like 2015 and 2015, 2016, around there. So they were like into HubSpot and like that's what they like used and that's what they were pushing on their clients. And one of the things they had me start to do is like building landing pages for their, their customers. And I just remember that, you know, the editor. I can't remember if it was the template, the template builder or if it was like the page editor. But I just remember looking at this like box and then looking at a website being like, I don't get how like these squares. The old template editor. Wow.

Yeah.

And it wasn't. Yeah, it was. I was really confusing for me and I was like, hey, I think that If I'm gonna build these things for you that I'm gonna have to learn how to like code. And they're like, okay, well we don't have a lot of work for you, so you can like, you know, allot this much time and like bill us for it.

Okay, so considered a data analysis or that was your job title at this point still?

Yeah, at that point, Yeah. I mean there was, it was like a three, four person operation. So we're sitting in like 70 hats, you know, and they're just trying to like give us work. But yeah, they were okay with me like billing them for like just learning and like messing around. So I just started like coding a lot on my own I think I like was heavily leveraging this one resource called the ODIN project, which is like, it's like a boot camp equivalent kind of like free resource. But the way that they make it free is that they don't necessarily like, they link to a lot of documentation. So like if you're doing something in like react, like they're just gonna link you to the REACT docs, but everything's free and there's like Discord channel and some forums and they kind of guide you through some projects. So I was like leveraging that to like just gain some chops and basically it was just like self taught to the point where like they started growing and I was like, okay, I'm like having a lot of fun, like I can start to like speak this language a little bit and like, like it's making sense and like I'm like not bad. I was pretty bad at it actually at that point I was, I was not good but it was a lot of fun and I was getting paid for it. So I was like, I think this is something that I could see myself doing. And I remember working at like a coffee shop one day because we were all remote at that time. Pre pandemic days. This is revolutionary. We were all remote.

Yeah, that's true. That's awesome.

I was working at a coffee shop and someone saw that I had like, I think I had Design Manager open and I don't think I was in my code editors yet. I was just one of the design Manager people and they came over and asked me a question about something I had never heard of before and that was SQL. And they asked me like, oh, do you know how to make this SQL query? And I'm like what? And that's what made me feel like, okay, neat. I don't know what the heck I'm doing at all, you know, just no HTML and css. So no, I don't know.

There's always that humbling coding question that knocks you down. Right, right. That's always. Just like always.

Yeah, yeah. And that's when I think I really started like digging in a lot more and eventually it got to the point where, you know, I was like, I am able to like build modules relatively fast. Like I can do things, I think I know what I'm doing. But I also haven't been sat next to someone who like definitely knows what they're doing. So I don't know. And there weren't any other developers on the team. Like it was just me. And I'm a self taught solo dude who like is like has this inferiority complex at this point. Right, right. And I get to the point where I'm kind of talking with like the owners a little bit. I'm like, I get the feeling that you guys don't want like a development arm to this team. I feel like y' all just want to do like SEO and stuff like that. And I feel like you're just giving me some work because I'm here and that's what you like, you just want us to work. And they were like, yeah, pretty much.

Those are the SEO hey days where it was like everybody focused on that and the development side of it wasn't as important, but it was like, don't forget to stuff those keywords in that meta tag.

Don't you forget.

Yeah.

Oh gosh, the keyword attack. How great that aged.

Miss that.

And then yeah, they were like, yeah, that's pretty much it. So I was like, okay, cool, let's come up with like offboarding plan for me. And I do a lot of swing dancing. So I like went on like a swing dancing like trip to go do like a whole bunch of dancing. And when I came back they were like, oh, we've got an interview lined up for you. You know this is a Monday. Like yeah, you got an interview tomorrow at this, this other place. Wait, wait, wait, wait.

Your, your, your company lined up an interview for you at another company?

I was just, that's what I was going to ask.

Yeah, that's not real.

Yeah, yeah.

I have never heard like that's, that's unicorn stuff right there, man. I've never heard that before ever.

I've heard of let's do your off boarding plan. There's the door.

Never.

Or let me tell you what you did wrong for the last four years.

And then, well, yeah, so looking back I have theories and this is higher picture, this is life. I have life theories on some of this and how it plays out. We can get into that in a little bit if we want to.

But.

They'Re like philosophical stinger life. Yeah, life theories brought to you by Peach. Anyway, yeah, they, they had me set up like the next day with an interview and I don't, I, I, I don't know if he's been on the show or not, but I know you all know him, John McLaren.

He'S mentioned something about you stealing his job once or twice, I think in the last 20 minutes.

But yeah, I didn't steal his job, but he had just left a company called Spin Group here in Milwaukee who if any Spin Group people are, are out there in the ether. Y' all rock. I love you. And if you're a marketing team that needs a good agency, I highly recommend getting some development work with Spin good people. Anyway, John had just left Spin Group to come work at HubSpot and I think it lined up where it was like maybe a week or two or it definitely wasn't long after he had left, which is how this like coincidental synchronistic like opportunity kind of happened. And yeah, at an interview with the owner and within that week was working at Spin Group at this like full time development job with actual like developers and engineers and like, you know, their small little powerhouse of like, you know, three, four developers and they get stuff done. So yeah, I worked there for like two years just being almost entirely like the HubSpot developer. And I tell you, just two years of doing, you know, something under some mentorship with like full time, like you learn so much, so, so much.

Speaking of that quick plug Mentorship Program, HubSpot, sign up for it if you haven't already.

How do you do that, Nick? What's. Do you have, you have anything?

Dennis, you have the URL, I believe somewhere, don't you?

Oh, buddy.

Did we post it?

Find it again? Now I'm like actually having to do things. Thanks, man.

Because what's going to happen is I'm going to have to be like, yeah, it's in the show notes I didn't do yet for like the third week in a row. I do Achilles heel. It's, I'm, I, yeah, I, it's bad, it's bad. But it's also.

Let me ask you really quick, dj, because I, I kind of had a similar thing where, you know, was the only developer at a company that I worked at, then went into an agency, then Came here. I'd say like when you said like working under people that like our teams of developers with mentorships and stuff, like it is really crazy to be thrown into that world. Almost like from going to being like the sole person who's like, yeah, I just like picked up web and just started doing it because there was a need for it. And then getting thrown into like an actual agency life, did you find it harder to like, I guess, did you find it harder going that route as opposed to doing something that I don't like being a freelancer for a little bit then going into an agency. Do you think that would have helped you? Because like, looking back, I feel like if I would have just done more freelance of random clients then went into an agency, I would have had a much better understanding and probably an easier onboarding than just, you know, throwing myself into the deep end kind of thing.

I hear what you're saying. This worked really well for me. I think that what it did for me is it like it provided onset, like validation that like, oh, like I am doing things the right way and like here are some things. There's a lot that I don't know, but I should also, I think specify that like the way that Spin group worked a little bit wasn't like they, they act as the development arm for a lot of other agencies. So it's like this small team of just developers and there was a lot of autonomy for like, you know, you're owning this project, you're running this project and the owner kind of like is like helping, helping you out. There's so much flexibility, you know, from his standpoint of like, you know, what do you want to do as an engineer? And like, I'm going to give us that work and like allow you to grow how you want to grow so that you can like go do the things you want to do. So for me, it worked out really well. I didn't feel like I was thrust into a place with a lot of like hard set rules and hard set like practices and like, you have to do it this way, you have to use this tool. It was very much like, what do you, what do you want to do? How do you want to grow? And let's get you there. So I really loved it.

BJ earlier this week when we were talking had our kickoff meeting about the upcoming developer hug on Elevate, which possibly a good segue, we were discussing with Anton how the nice thing about developing on HubSpot was the ease of onboarding. Like you can get into it pretty easily and move forward to more complex things. They're talking about incorporating React in that, how the onboarding is going to be a little bit more challenging. How do you, reflecting back, how do you think that would have affected your experience?

Are you saying that like, if I like putting myself back in the shoes, but pushing the timeline up.

Yeah, exactly.

Like as a new developer, kind of green in the engineering space in general.

So like, compared to where it was then, now put yourself into those shoes, present day. Yeah, where it's a, it's, it's a, it's a different animal. It's not in the design manager, you know, or the template builder. At this point. You're not adding a little HTML, you know, snippet into your boxes on the design anymore. You're actually doing coding on your own device and setting it up. It's, it's harder, you know, admittedly it's, it's different, right?

Yeah, yeah. So it's a, it's a double edged sword, right? Because like, I think, you know, part of the question we're asking is like, how do engineers, like, if you're just getting into like coding now, like, what do I learn? How do I like allocate my time? And like one of the cool things about HubSpot is that like you can just know HTML and CSS and get really far and the reality is that that's not going away. Right? Like you can still be starting today, no, just HTML CSS and you can still do things however you want to do them in Design Manager or pull things down locally and like push things up using the cli. Frankly, if we are just starting, like, if you are just getting into the development world, I think that that's what you should be doing. Like I think that you should be learning HTML CSS, plain old JavaScript and you should have those chops because that is what React is built on. But then I think that once you spend a little bit of time there, I think that absolutely learning some kind of JavaScript framework, whether it's Vue, you know, if you're like watching this and you're not a HubSpot developer, if it's Vue, if it's React, like if it's svelte, like just learn one of them and like really dive in. I think that if you are like an experienced like HubSpot developer, like now is the perfect time to really start like wetting your chops, wetting your whistle with, with React, because like you already, now you have a reason for it. Right. Like you are already a HubSpot developer. You don't have to learn that ecosystem anymore. But now you can see how this other really great tool that has been industry standard for like, frankly a very, very long time can now be used on the platform that you're building out to help your customers and you're seeing how you can like integrate it into your own workflow. And like, personally I have to say that like I've been building with this like new theme pipeline, although it's like not quite documented, super, super well yet because it's changing so quickly. But once you spend a bit of time in it and like get comfortable with it, like the benefits that you get from it are just like astronomically better than like building the old way. You'll be able to build things a lot faster, you'll be able to have better performance sites without trying that hard and you'll be able to have cross site scripting security baked in and a lot of these other security issues. There's just so many benefits that you get from it outside of the obvious server side rendering, stuff like that. But to like getting a little off track, but to like circle back to your question, like learning, I think it would be daunting, right? But I think that as an engineer, if, if you're like committed as a developer to want to learn like how to be a developer, how to program, this is only like spending three months, spending six months, spending the next year trying to learn how to like work with React is only going to make you a better, more well rounded engineer. Yeah, totally agree. If you're like a solo developer, it's going to open up the world for like, oh, I can take React projects now. Like yeah, yeah, because I know how to build in React. Like I can start using these other frameworks, you know. Yeah, for sure.

Also you just be a more complete HubSpot developer that, you know, you can start doing, you know, React cards, you know, app cards. So yeah, I was, I was just.

Going to say it's a perfect segue into learning both sides because the app cards and stuff are powered by React. And if you happen to be like an app developer who knows React, guess what, you can build on the CMS too. Like it's a transferable skill at that point. And I think like that's, that's, that's what I love about the fact that like we're doing React on the CMS side and in the app cards is I have always been a CMS based kind of developer and like more on the front end stuff. So now it's like I can start building these things. I can start, you know, tacking on.

The knowledge that I have and expanding my skill set.

Yeah, yeah. And I think if you've been in like the HubSpot developer ecosystem for, you know, three, I think three to five years at least, maybe even less. Like you probably have some HTML CSS and at least a little bit of JavaScript chops. And I think based off of that, like, that is enough to be able to like take the leap and kind of start sticking your toe in the REACT water land. And I think that for a lot of the experienced developers who have like vanilla JavaScript chops, like if you feel comfortable writing JavaScript, like, and have never worked with REACT before, I would say if you spend like two months to three months, a little bit of time each week just like kind of sticking your toe in, starting to build a module, see how it works, like within three months I think that you'll be at a place where you're feeling like confident and that I feel like is a very small investment, you know. And I'm not saying three months of like every day I'm sitting here like chugging away trying to learn, but it's like I'll pick it, you know, an hour or two a week, you know, and just like try to like futz around with something for a little bit. I think that within three months you'll see the benefits.

It sounds like Legion is offering to do a CMS REACT boot camp.

Yeah, so I heard that. Pretty much heard that.

Yeah, that's what I heard.

I read between those lines. I read between those lines.

I was like, I say maybe just come to the D hug next week. Maybe come to the D hug next week. It'll be our little mini boot camp.

I mean, my next question was going to be why is JavaScript so sexy? But I think you pretty much nailed it at that point.

But I mean, yeah, good. Oh, those are the. I mean it's time of debate, right? You're going to have people who hate JavaScript, you're going to have people who love it. But as a front end engineer, like JavaScript now allows me to write back end code. Like I can pretty much link wherever I want to be. That's right, yeah. So it's amazing. I think any language that you know is amazing and when you can do more with it, it's even more amazing. Yeah, absolutely.

Now with the. Because you touched on like going in and dipping your toes and like going for you know, take a couple months with as daunting as some of the stuff can be, what are some of the ways or what are some of the resources that you use to kind of keep up to date with some of the latest things going on, like, especially in JavaScript or in any other kind of area.

Yeah, so this is where I maybe, like, I'm a little bit different than other developers. I don't really know what other people are doing, but I don't have, like, a whole lot that I like, you know, refer to. I think one of the main places or one of the main resources that I have is as a newsletter called JS JavaScript Bytes By. And it's just this, like, weekly newsletter that has a lot of, like, updates in the JavaScript world. So it could be React, could be camp, could be svelte, could be some, you know, MDN docs thing. But then they always. It's kind of comical too. The guy, whoever writes it is pretty funny. And it's like Mimi. And then there's always a quiz at the bottom each week. And that, like, yours is like, just like a challenge, like a little puzzle. So it's fun to, like, solve that.

We should steal an idea.

Yeah, good idea.

And, you know, some examples might be that it's like, what's wrong with this, like, function? Why doesn't it work? Or maybe it's like, what is the, like, output of this thing supposed to be? So I guess, yeah, you could do it in like, Hubble talk or React talk, or just quiz about Dennis's life talk.

The airspeed velocity of a swallow carrying a coconut.

No, yeah, exactly. Exactly the important questions. But yeah, James, that's. That's my. My go to.

Should we all learn typescript? Is that. Is that necessary now? Oh, yeah, I know I'm bringing in the heat now. There's some ice coming along with this.

So I gotta say, old me. Old me would have been like, hell, nah, dude, Java Typescript is bunk, man. But I now think that I'm in the camp of, dude, like, people who don't like typescript. They're just people who haven't used typescript.

Yeah.

Is that the Nickelback defense? Right?

I am at a, like, I see both sides to it. Um, I think that it is simultaneously a thorn in your side, but also has saved me countless hours for sure.

It is such a thorn sometimes though, isn't it? It's like, damn it, just let it go. Come on. Let it slide.

Yeah, I feel like, so what, I do a lot of now, so I'm heavily like in the, the Cursor camp is that I will just write JavaScript and then be like, type this for me. And then it does a pretty good job doing that. So I just have to sit there in my typescript file and just ignore the red underlines for a while or keep telling Cursor to do that as the red underlines, like, bug me, you know.

May I ask so a question specifically to Cursor and like this whole new way of developing. How would that have affected your learning prior to it? If you're writing JavaScript and you're just outputting the TypeScript, are you learning TypeScript at that point?

That's interesting. I think it depends on who you are as a person. I think that. And that has to go back to what is it like to even be in college right now with ChatGPT?

Right.

It's a good answer. I think that like, personally, the way that I interface with Cursor and like Cursor chats and like AI is from a, like, furthering my understanding of something. So I might write like a function and be like, I think this looks pretty good. Like how, like, can you refactor this and make it any better and see what it does? And you know, sometimes there have been instances where I've been like, oh yeah, that's way smarter than what I wrote. And then other times you're like, ah, like, it's probably, you know, 0.0010 05, like more performant. But like, I can't read that fast, you know, like, I'm not gonna use that. So I think that if you're the kind of person who is going to use it as a, like, teacher, as a tool, as like something to help you, like, learn, I think that it will be very, very helpful for you if you're the kind of person who's like, you know, replit, write me this app that does this thing. And then blah, blah, blah, hit enter. And then like, that's it, like, cool. Like, you didn't really build anything.

I feel attacked right now because that was my story earlier.

Describing my life story. What's going on.

Yeah, I think that it's going to be harder, you know, and, and.

I.

Think that you're digging yourself in a hole if that's. If you're like going down the engineering coding path and you're going to use Cursor because it can build the whole project for you, because at the end of the day it's going to write stuff and it's going to be complicated and you're not going to know how it looks in. So, yeah, I still think that based off of my use cases with Cursor and these AI tools that are building apps and stuff like that, they still aren't really even close to the point of like being able to replace someone or replace like a well thought out engineer, someone who's worth their worth of salt. But they are good at like making developers who know how to use them significantly more efficient until their. Whatever it is that they're.

Well, what's, what's the title? Prompt Engineer. Right. Is, is what a lot of people are talking, is what they're calling it Prompt engineering. So I, I agree with you. I think like, prompt engineering is great, but I think you need to have a technical background as a developer to.

Really utilize it to its fullest potential.

Because like you said, like, it's one thing to go to AI and say, hey, make me my idea, but is it going to be as performant or is it actually doing like what you're expecting it to do? And how do you expand on that? Right? Like, you can't plan for scale if you, you don't think about that ahead of time. So.

That'S a very good point.

Let me ask you this because I'm curious with regards to, because I similarly, some of my earlier jobs were kind of that like one person on an island type of setup. Right. Scenario, if you will. And there wasn't a lot of, well, there wasn't a lot of mentorship, you know, you know, going off of that theme. So there wasn't a lot of things where, or even soundboarding. Right? It's just like, am I doing this right? Somebody just talk me talk. Don't you have to give me the answer, but talk to me about this. Let's just talk about it. Maybe I'll come up with it as I talk. But has. What are some of the. Because I imagine better, you know, more advice comes along with more people. So we'll try. We'll try. I'm trying to do it without actually saying that. So I'm glad that you got that.

It's so like, you know that you're trying really hard.

I'm trying not to. I don't know. PJ knows every, like, episode, like real estate always comes up. I used to work in real estate, but that doesn't count as me saying it. But, but no, like, has there been any, like, has there been any kind of like, advice that people have given you, like a Mentor or something along those lines. That's kind of really stuck with you over time.

Yeah, yeah, I think, you know, it's kind of a. I feel like it's a recurring theme that like people tend to want to be like jack of all trades, especially in like the engineering world.

Right?

Like you're like you. But this is the, this is honestly something that upsets me a lot is that like everyone who comes out of a boot camp is like a full stack developer. And like, dude, you can't even write, like you don't even know how the DOM works. Dude, what are you talking about? You're not full. Dude. Dude, come on. It's just Mike, I'm like, yeah, I've been doing this for I don't even know how many years and I don't even consider myself to be a full stack developer. Like, can I like write back in code? Yeah. Like do I know how to do it? Yeah, but like am I a full stack developer? No. No, absolutely not. Someone who knows back end, like someone who knows Java can write, you know, circles around me, even if I were supposed to do it in like Express, you know, using like JavaScript. Yeah, someone, someone who's a backend engineer can write circles around me. But anyway, I think that the advice that that was given to me early on was that like don't try to be a jack of all trades, you know, go into specialization, like be really good at one thing and if you become a jack of all trades, great. But like don't set out to be the best at everything because at the end of the day, especially if you're like a solo engineer, like just like barking around for like gigs, like being a jack of all trades I feel like makes you slightly less hireable to be honest, because a lot of times I feel like people aren't. Sometimes people are looking for someone who can do everything right but then you typically getting a person who can like do like 40% this, like knows 20% that, maybe 60% here. And a lot of times what makes you much more valuable at an organization is being the person who like really knows how to do everything. On HubSpot, you're like the person who knows a lot about accessibility. You're the person who knows like how to like, you know, make any design come forth on the front end, you know, you're the person who knows how to architect the best back end API that you can make. You know, like really stepping into like a focus of being like a HubSpot developer and like what it is to do that. And like just kind of like now there's all these other like branches too, right? Like you can be like a front end HubSpot engineer, you or developer. You can be like building on the cr, the CRM and like building your cards and stuff like that. And you can build a whole business off of just like being that guy. So I think that, yeah, really focusing, especially early on, I think that this is mostly advice for people just getting like into the scene or we've been around for a little bit but are looking for some traction is just to like pick something, even if it, like, even if you don't know that's the thing you want to do, right? Like pick that thing and go with it. And eventually you'll be like, I hate this, I don't want to do that, or this is absolutely the right choice and I'm glad I made it. And you can always like make these little adjustments along the way. But that at least is more direction than being like, there's three acts, there's vue, there's spout, there's all these frameworks, there's accessibility, there's, you know, just being good at css, there's filing with tailwind, there's just doing raw css, there's like all these different stacks. Like, what do I choose? Just pick one and like go with it.

That's tough, man. I mean, like when you have the imposter syndrome already, like, you just want to have familiar. Like when someone comes into me in the coffee shop and says, you know how to write a SQL, SQL query, you know, it's like, I will in five minutes because now I need to know, you know, just to keep up.

Being the jack of all trades is like a one way path to burnout because you're going to spread yourself so thin that you're, you're not like, you're eventually going to get something from everything that you've learned come at you at once. And now you have to prioritize and.

You have to shift things and you.

Have to like set them all up.

Knock them all down.

But like, that can just completely derail you.

Plus you also want to avoid that pitfall too, of like finding a place to work where they may be specifically. And again, it's not anyone's like, fault, but they may be asking for that, not knowing exactly what they need. So they kind of ask for that. Like, as I've seen ones and had interviews too, where it's been like, well, we want you to do like X, Y, And Z. And I'm thinking, okay, yeah, no, no, the SEO part I get. But then the other five things I'm like, you think one person's going to be able to do all this? Yeah, horribly. Like, you know, at 20%. Like, you, like, you're saying BJ, like, there's going to be this kind of like, percentage that you can only reach when your spread so thin. So, yeah, that too is.

Sounds like a data analysis working on landing pages to me.

Right? Yeah. Yeah. And the reality, like you guys are saying is that, like, you know, that's what ends up giving you so much stress. Right. Is because you're like, I understand 20% of what this task is. And like, now I have to like, really dive into, like, the nitty gritty on, like, how to maybe make this little thing happen that I just don't know that much about. And I think it's also liable to put you in a position where.

You.

Are less of a team player. You know, in. In the world where you become like, you know, you'd say you do that for a while and then you get brought onto a team that has, like, a bunch of people on it and like, you know, it's like HubSpot, where we have like, our little, like, you know, smaller teams that move quickly. Like, I very likely would have come up with some kind of like, you know, personality quirk that's like, oh, I'm what I refer to as a Stack Overflow developer, where I'm like, just gonna like on you for having any question. And I think that I'm like, the best person in the world, by the way. I think the best way, if you're ever gonna post on Stack Overflow, the best way to get someone to actually answer your question is to write your own question on there and then make another account and log in and answer it the wrong way. And that way people won't blast you for like, asking a stupid question, and they'll blast the person who was wrong about answering it wrong, and you'll get the right answer faster.

There you go, friends.

That is such a great tip, though, because I 100 believe that that is exactly what would happen.

Yeah, I've been talking from experience on that one. I posted on Slack Overflow maybe like two or three times. And the first, the first few times it was like me asking a question and just getting railed for, like, for like, not asking the question the right way. And I'm like, I'm just starting. Like, yeah, I don't know. I don't know what? I thought you guys were gonna help me, but you're just berating me for asking a stupid question. And then the next time I asked the question, walked in and made a stupid answer, and then the stupid answer got blasted by someone who corrected the stupid answer, and I was like, wow, that seems.

Fly traps.

Yeah.

No, that's brilliant. Yeah. Next time I go on there and I see somebody who just answers, like, reinstall windows, I'm gonna. Now, I think that's BJ doing that.

I know that name is jb, though, so. I don't know.

It could be.

But no, it's amazing, the lack of empathy that when you go outside the walls of HubSpot, that exists.

Right.

I mean, like, I. I shouldn't say I didn't. I wouldn't know that already, but, like, you kind of. Once you've. And I know this is just me, but, like, once I started working here, you know, the.

The.

The less and less I needed to. Like, there's. There's. I mean, there's. There's thousands of thousands of intelligent people that work here, so it's like going to stack overflow.

Yeah.

You still may need to do that, like, those type of things in certain aspects. But, I mean, there's a lot of intelligent people here that we deal with on a daily basis that we ask questions of when we have problems. And because this place is, like, very, very empathetic, you start to almost have amnesia where you go outside of the thing, and you're like, wow, everyone's. Everyone's just a prick. Wow. How does this work? You know, it's like. So. Yeah, that's one of those things, too. That always gets me. And I. I was one of those people. So it's not like I. I'm completely. Yeah, that. That's one of the things that shocks me kind of when having to kind of like bounce in between, like, inside of HubSpot and outside of HubSpot, so. But no, that's a really good tip. Like, that's. I'm just like, I just thinking in my head, like, well, I just. I just want to go ask something now just so I can watch it and. Yeah.

Yeah.

You're a. Swing dance.

I think.

I think Dennis is cutting out again.

Swing dance.

I think what you're saying was it was your mentor that you're like an instructor from.

No, no. I've. I've heard that advice from multiple people, but, like, main. I think the. The latest person that I've gotten it from was my. The Owner of Spin Group there. So that agency that, that I was working for.

That's Gary, right?

That's Gary.

Yeah, yeah, Gary's cool.

Here is really good. Yeah.

Is, is.

Do you have a particular piece of advice that you would like? If the, if roles were reversed and some. And you were giving someone like some sort of advice, is it along those same lines or is there one in your head in particular that you're like, I need to make sure I tell people this. I know we've talked about a couple of them, but is there any one of them that you would say that that was the one thing that you would hope. If somebody else were asked this question and they were like, oh, yeah, BJ told me this. What, what would that. What do you think that would be?

I think that my advice for people would be very different, depending on who's asking. But I think the, the generic advice that I have and this pseudo ties back into the like, life theories that I have would really just be like, follow your excitement, you know, do the things that are exciting for you. Do the things that, yeah. Are exciting for you. And I think that everything else, like, if you're honest with yourself about like, what you're excited about and what you want, like just really. Yeah. What makes you happy, what's exciting, the rest of the things will work out. So, like, I think it applies across the board, you know, so, like, you're in, you know, programming because it's paying, it pays well, you know, that's one thing. But I think that you're at the end of the day going against the grain and you're going to get burnt out and you're probably not going to be like, happy. You might be happy for a bit, that money's going to be nice, but eventually you're going to run into some problems. And I think that if you're in, you know, software, because you enjoy coding, great, that's what you should be doing then. And I think that from there, you know, if you're trying to figure out what to do, it's literally just following your excitement. And if, again, if there's so many options that you don't know what to choose from, you know, the first option typically being front end, back end, just pick one, pick one and see if it's exciting to you. And if it's not, then, you know, to go to the other one.

That's a combination. You just gotta go, yeah.

And I think that that's just your really good framework for making decisions. You know, it's Just like, if you're at a crossroads and you don't know what the best thing to do is, it's at that point where you should stop trying to figure out what the best thing to do is, and you should just pick something to do. And, like, that will be far more helpful than trying to optimize your life, because you'll get.

You'll have that choice paralysis at some point because there'll be so many times you have to just kind of. I always. That always used to happen to me when I was designing stuff, whether it be for, like, websites and stuff. I would always, oh, no, no, I can do it this way, or no, this. I want to do this design, or no, I'm going to redo this. This is better. This is bad. And it would be like, it would just never get done right. So it's just like, there's one of those things. We just kind of have to jump into it. And I kind of did the same thing. Like, like you're saying with your advice, you know, is I was like, okay, well, what. What do I want to do? I really love this. I really love that. I really love SEO and I really love. Well, maybe I'll just find something that does everything or that encompasses all of it. It was just like, yeah, looking back, I was like, yeah, that was a dumb, dumb way of thinking about that. Just really bad, right? Because then that, like you were saying that burnout, that becomes almost inevitable at a. At a certain point. So. But no, that is. I. That's just kind of. And I don't think people realize too, how monumental that kind of advice is, because everybody's. You know, when you're first starting out, no matter who you are, you know, you're always kind of, this, I'm gonna. I'm gonna turn this all on a tear, and I'm gonna. I'm gonna show everybody how this is done. I'm gonna, like, I'm gonna rock this. And it's like, all you end up doing is rocking yourself. There was this. Yeah, I'm gonna have to paraphrase it because I can't remember the quote, but it was like, you know, people that like you, you work constantly and you're trying to do all of these things, and you're burning up all of this time, and it's like nights, weekends, and all of this, like, really, really focused on this particular, like, either coding task or whatever that will go away eventually. Like, that will disappear and you will move on. The only people I was going to remember that you burnt all that time. Are your family, your friends, your loved ones and kids, like. So it's like one of those things where it's like, you really have to, like, you have to narrow down the focus because you will, like, spin your wheels and spend all that time and. Yeah. You don't want to be one of those people that look back on and be like, oh, man, I wish I had those five years back. You know, it's so.

It's.

And I believe the quote you're looking for is, nobody's going to remember you were working late except your family and kids.

Yes, that is exactly. Yes. Thank you. Thank you. I like that quote. I really do.

It's great quote.

Yeah.

Yeah. And I mean.

And I think.

I think that was focused on working hard, but, like, you're. The same tactics apply when it's like, trying to do too much at once, because then you do have to spend that extra energy and time. And it's like, you know, how many people actually succeed with that type of approach? Very little, if any. So. But no, I dj that's, like, fantastic advice. It really is. I think we're gonna have a lot.

Of YouTube shorts where we're literally. I'm just gonna make, like, a really cool intro trailer for, like, Thoughts of BJ and everything. And then just like, we'll just make excerpts of you, but you're stealing.

Just as long as you do one of those blooper reels. That's like one of us. It could be me just going. Talking about the. Like to start. Anyway. I think the other thing that just came to mind would be that if you're. And I think that a lot of people hear this, right. But if you're just getting started in, like, the developing space, be it on HubSpot or just in general, I think that the other piece of advice that I would give is like, just build stuff, like, building a lot of things, and, like, don't worry about it being built. Well, like, I mean, if you're getting paid for it, make it as good as you can. But if you're just like learning, just try to build a bunch of stuff. You know, I think one of the things that I go back to is I. I built this tool before, like, the AI train started. That was that I called Help Copilot. And it was to bridge the gap between, you know, when you're working in Design Manager, you see all of your fields in a drag and drop interface, and when you're working locally, you don't get that. So I Built basically the same thing, but as a standalone app that you could install on your computer program, you could install on Windows. It was that drag and drop interface and it like auto automatically synced and saved your files. If you're working locally, you just do it all. And the code base for that thing is just a brick of nonsense. It is so ugly and I never want to look at it again.

But it was fantastic though. I remember you shared that with us and like it was awesome. Like it was a really good app.

It worked. It worked. It got the job done. Um, but I think like just thinking back of like late nights trying to solve like problems that I would consider fairly simple right now, I did in the most complicated ways. So. But I mean like that's the progress of learning. And the reality is that like, you know, you, you see a hole, you see a gap and like you're like, I think I can build something that can fill that gap. And it might not be the best technical solution, but it will be something that you will use, that people will use and you'll learn a lot from doing it. So just building things, seeing how they turn out and then reflecting on those things like will do dividends for your growth. Right. Right now. That's fantastic.

Well, we're gonna, we're running up on time just a little bit here. So I just want to thank you for coming on and talking with us. Abhijay. This has been like, it's been fantastic and it's, it's good to hear. Like, because honestly we get a lot of journeys that are, they're very, as you put it. You said yours is very organic, right? And it was very like some of the ones we've had, like even mine, myself and others, you know, it's a little, you know, it's kind of all over the place, right. And neither is good or bad, but it's like, it's, it's, it's nice to hear a journey like this where, which I'm sure a lot of people can relate to, if not a majority of, but like that kind of self taught because I'm a little bit of that I'm kind of in the same boat with like some of the things that I've learned. So there's like a lot of respect there because it's not, it's not easy, right? Like the, it's, it's hard. And let's put this way, it's hard when you have. And at the time, like I didn't know, like I didn't even Know the term imposter syndrome, right. Like when I first started working. But it's hard to have that and then not have any outlet to even express that. Even if it's a coworker or even if it's somebody in your field. Like when you're on an island by yourself, it is just that it is very lonely. It is very, like. And like you said, you've, you know, you post something on, let's say, even stack overflow, there isn't a warm reception in a red carpet rolled out for you.

You know what I mean?

So it's like there's. I have an utmost respect for you for the, the journey that you've taken thus far and, and the way you've approached it because, like, it drowns a lot of people. You know what I mean? And it takes. There's a certain amount of strength that you have to have coming from that sort of relevant island that you're in to make that next leap forward. So I think that's just. It's fantastic. It really is.

So, yeah, yeah, thanks. Thanks for having me. It's been a lot of fun.

No, I, I love it. And yeah, I mean, it's one of those things where I think it's important for people to hear it really is because there's people out there. And then wherever you are in your, you know, developer journey, or even if it's relevant, you know, to developing, it doesn't have to be specifically like, I'm a coder. It could be I'm, you know, a program manager. Whatever it is, hearing just different stories and different things like that, I feel like kind of helps people navigate because some people are in the middle of their story and they don't even know it or they don't know how it's going to go or where it's going to go. But hearing how other people kind of overcome some of these things or just kind of, you know, paddle through the water, to use a really bad, you know, journey analogy. But, yeah, we think it's, it's fantastic. And having you on has been fantastic as well. So I just, I wanted to say thank you. It's been really awesome.

Yeah, yeah. You know, and related to what you just said though, too, like, if you're. And I'm sorry for keeping this going, but, like, if you are, like, in the middle of your journey, I think the last little bit that I would, like, share is just like, don't get hyper fixated on the fact. Don't get, like, hyper focused on what you Think your journey should be, you know, don't like, think that, like. Oh, because I started, you know. You know, I started off with a job that was, like, doing data analytics stuff. You know, if I was going to start it up, going to school for, like, accounting, if I were, like, accounting is the thing, you know, I would have just been stuck in this, like, hellscape of being, like, really sad, making a lot of money, being very sad, you know, and being open to, like, the idea that where you think you're going is the happiest you can be. Like, that's not true. Like, your brain can't even conceive of the other options that could make you uncomfortable. Conceivably more happy. Right, Right. So I think from that standpoint, you just have to be willing to, like, really feel that, like, this is exciting and if it's exciting, it'll take you to the place that you're supposed to be.

Oh, yeah, absolutely agree. And John makes a really good point too, especially nowadays. He said, accepting that life's going to change. Right. And you're going to be so mildly different just years from now. Yeah. And plus, too, like, with. With the way technology is advancing and with. With the tools that, you know, we. Not more than a couple years ago, weren't there, that are there now. Granted, like, like, we talked about, like, some of these things. It's not just going to be as plug and play as we'd like it to be, but as a tool to help guide you instead of, like, the shortcut. Yeah. I think there's now more than ever. I always tell aj, this is kind of the. At least for me at the age I'm at, this is the span of time that's just so unique coming from not having any of this, like, straight up, like, Razer Flip phone experience in that. Right. To like, now where we're talking about, like, you know, putting in blocks of code to have it be rewritten more efficiently or in some cases written in general is a huge leap. Right. I remember because I remember when my first. My first job where I ever touched tech was just. Was at Eastern when I was there. I think you were still there with. At the same time, aj but like, it was in the web department. And we're talking like, this was tables. This was like web pages and tables where it was like copying and pasting cells back and forth to try to, like, edit the. The tech department's website or whatever for Easter. So it was just like, remembering that and like, to where we're at now. As John puts. It's going to change wildly daily now. Now it's on the daily. Then it was just like, month over month. But like. Yeah, it's just one of those things where that. And then some of the advice that you've given, like, just ask anybody who.

Was an Adobe Flash developer, what was Swift. It was a swimmer.

The other thing, the Swift animation.

Right.

Remember, that was like, you could. Yeah, that was. I did that because I didn't grasp the Adobe one yet. So I was like, oh, well, Swift is a lot quicker. And you can just do like. You know, it's like almost like not drag and drop, but it was easier. So I was like, oh, yeah, I'll jump on that. But, yeah, no, absolutely. But again, I just want to say thank you for coming on. Thank you, AJ for helping out. Thank you, Dennis. He had to go sing backup vocals for Beyonce. I think he was on a hard deadline, so we had to stop. But that's okay. That's okay. And let me leave you with this little tidbit of information. English poet Alexander Pope, when once asked about GitHub, he did say, to errors human, but to green square divine. I'll leave you with that. So. And then, aj, you could take us out.

All right, see you later.