TRASCRIZIONE 🔗
WEBVTT
00:00:00.719 --> 00:00:04.879
Hello everyone and welcome back to another episode of Code and the Coding Coders Who Code It.
00:00:04.959 --> 00:00:09.359
I'm your host, Drew Bragg, and I'm joined today by a repeat coding coder, Jeremy Smith.
00:00:09.519 --> 00:00:15.279
Jeremy, anyone who hasn't listened to your last episode or is unfamiliar with you, please do a quick introduction.
00:00:15.599 --> 00:00:16.640
Hey Drew, yeah.
00:00:16.879 --> 00:00:17.920
Thanks for having me back.
00:00:18.079 --> 00:00:19.280
I'm Jeremy Smith.
00:00:19.359 --> 00:00:22.239
I am a product-focused Rails developer.
00:00:22.480 --> 00:00:32.240
I run a tiny one-person Rails studio called Hybrid, and I do the Indie Rails podcast with my friend Jess.
00:00:33.520 --> 00:00:48.079
And this is sort of new, but I'm going to be taking over facilitating the Ruby Consultants quarterly call with Ruby Central, which I want to get more people involved in this that are in the consulting space.
00:00:48.320 --> 00:00:50.640
So going to be helping out there.
00:00:51.039 --> 00:00:57.119
And I am a once in future conference organizer with Blue Ridge Ruby in Asheville, North Carolina.
00:00:57.359 --> 00:00:58.079
Yes, yes.
00:00:58.320 --> 00:00:59.039
Excited for that.
00:00:59.200 --> 00:01:01.840
And we're going to get into all of that in our show.
00:01:02.000 --> 00:01:06.480
The way this is going to work is I'm going to ask Jeremy three questions, ask him what he's working on.
00:01:06.640 --> 00:01:08.319
Doesn't actually have to be work work.
00:01:08.400 --> 00:01:12.079
It can totally be like, hey, I'm putting on a conference style work.
00:01:12.319 --> 00:01:20.480
What kind of blockers he has, and what's something cool, new, or interesting that he's learned, discovered, built, could be tools, could be books, could be anything.
00:01:20.640 --> 00:01:22.480
Doesn't have to be coding related.
00:01:22.799 --> 00:01:31.840
So we were going to talk about Blue Ridge on your what are you working on, but I first want to talk about the call that you're going to be running with Ruby Central.
00:01:32.000 --> 00:01:33.439
Talk a little bit about that.
00:01:33.599 --> 00:01:34.640
What's the call like?
00:01:34.799 --> 00:01:36.079
Who's supposed to be there?
00:01:36.239 --> 00:01:37.040
Things like that.
00:01:37.359 --> 00:01:56.319
Yeah, the reason I mentioned it, I keep trying to mention it wherever I can because this is sort of a little known kind of quarterly meetup on Zoom for agencies and consultants, freelancers, anybody in kind of Ruby and Rails that provides services.
00:01:56.879 --> 00:02:03.760
And so it'll be agency owners or people within agencies coming on the call.
00:02:03.920 --> 00:02:06.400
It'll be independent contractors coming on the call.
00:02:06.560 --> 00:02:14.080
And we're talking about all the things related to our service work inside of the Ruby Rails ecosystem.
00:02:14.319 --> 00:02:19.759
You can get a lot of information about sort of the industry in general.
00:02:19.919 --> 00:02:25.759
But if you want to know Ruby specific stuff, this is like one of the best places to go to kind of share what's going on.
00:02:26.000 --> 00:02:28.159
What are we seeing in the Ruby space right now?
00:02:28.319 --> 00:02:32.159
Where are people finding success with leads?
00:02:32.479 --> 00:02:37.759
What are the challenges people are facing right now in the market, in our particular market?
00:02:38.000 --> 00:02:42.159
There's really just nowhere else to get that than this call.
00:02:42.400 --> 00:02:54.479
And quarterly ends up being a pretty decent cadence, I think, for kind of sticking your head up and kind of talking around to other folks in the same area about what's going on.
00:02:54.719 --> 00:02:56.400
And that's been really helpful.
00:02:56.479 --> 00:03:01.759
And it's been really nice because we all have our business struggles.
00:03:02.000 --> 00:03:08.719
And when you're able to raise, you know, an issue in that group and have multiple people say, Yeah, we have the same thing.
00:03:08.879 --> 00:03:10.319
Yes, we're going through that as well.
00:03:10.400 --> 00:03:11.680
Yes, we've also seen that.
00:03:11.840 --> 00:03:12.879
It's really helpful.
00:03:13.039 --> 00:03:13.919
It's really nice.
00:03:14.080 --> 00:03:18.639
And maybe in some senses it would be like we're competitors, maybe, but not really.
00:03:18.800 --> 00:03:24.319
And it feels more like a bunch of people rooting for each other since we're all doing the same kind of work.
00:03:24.479 --> 00:03:26.560
So typical Ruby community stuff.
00:03:26.879 --> 00:03:27.439
Yeah, yeah.
00:03:27.520 --> 00:03:28.159
I love to see it.
00:03:28.319 --> 00:03:37.520
You know, I don't know if you know what other communities and languages have this kind of thing, but it feels very much Ruby to me.
00:03:37.840 --> 00:03:38.319
For sure.
00:03:38.479 --> 00:03:39.199
Sounds like it.
00:03:39.360 --> 00:03:40.319
That's awesome.
00:03:40.639 --> 00:03:41.840
Congrats, I think.
00:03:42.240 --> 00:03:42.479
Yeah.
00:03:42.719 --> 00:03:43.039
I don't know.
00:03:43.360 --> 00:03:43.599
Yeah.
00:03:43.840 --> 00:03:49.439
I think for a while they were trying to decide like there wasn't really a person to go to to facilitate it.
00:03:49.680 --> 00:03:55.439
And maybe the people that originally suggested starting it didn't know what to do with it or left.
00:03:55.520 --> 00:03:57.520
And then they were like, what are we doing with this thing?
00:03:57.680 --> 00:03:59.360
And I keep saying, Oh, I'm loving this.
00:03:59.439 --> 00:04:00.240
This is good for me.
00:04:00.479 --> 00:04:01.680
Like, I want more of this.
00:04:01.840 --> 00:04:02.960
I want more people to come.
00:04:03.120 --> 00:04:15.840
So what we were actually going to talk about on the what are you working on was your back to helping to run, organize, do all the things, make the magic happen that is Blue Ridge Ruby.
00:04:16.240 -->
Load full transcript
00:04:26.000
So for anyone who doesn't know about Blue Ridge Ruby, hasn't been to one in the past, doesn't see all of your posts about it, recently talk a little bit about Blue Ridge Ruby.
00:04:26.160 --> 00:04:26.800
Yeah.
00:04:27.279 --> 00:04:34.720
Back in 2022, this post-pandemic, I started going to a lot of Ruby and Rails conferences.
00:04:34.959 --> 00:04:47.439
And it was a big shift for me in investing more in being involved in the community and in showing up in those places where people are meeting together in person.
00:04:47.600 --> 00:04:50.319
And that had a huge impact on me that year.
00:04:50.480 --> 00:04:54.079
And toward the end of the year, I thought, man, I'd love to put on a conference of my own.
00:04:54.160 --> 00:04:55.439
That's that would be amazing.
00:04:55.600 --> 00:05:02.959
I was really nervous to try to pull that off on my own, but knew a guy in Asheville who reached out and said, Hey, I'll help you.
00:05:03.120 --> 00:05:05.839
And that turned out to be Mark, one of my co-organizers.
00:05:06.079 --> 00:05:12.480
And so the two of us kicked off Blue Ridge Ruby in Asheville in 2023.
00:05:13.040 --> 00:05:22.079
And it was one of the scariest things that I did, and also one of the things I'm most happy about.
00:05:22.959 --> 00:05:43.680
It's hard to explain why it had such an impact on me, but when you get over 100 people together and create an experience where they're all contributing to it together and having a great time, it was just amazing.
00:05:43.759 --> 00:05:50.399
It was an amazing experience, amazing feeling to have like maybe created the container for something really good to happen.
00:05:50.720 --> 00:05:54.560
And I keep telling people it reminds me of that parable of stone soup.
00:05:54.639 --> 00:05:56.720
I don't know if you've ever heard this parable before.
00:05:56.879 --> 00:05:57.199
Okay.
00:05:57.600 --> 00:06:02.639
So when I was a kid, we had this book, and it's like the story of stone soup.
00:06:02.720 --> 00:06:10.480
And this guy who is really hungry goes to a town and he's begging for food, but nobody wants to give him anything.
00:06:10.639 --> 00:06:19.360
So he gets this idea and he finds an old pot and he fills it with water and he starts a fire and he starts cooking and people start walking by and they're saying, What are you making?
00:06:19.600 --> 00:06:21.759
And he said, Well, I've making stone soup.
00:06:21.839 --> 00:06:24.319
He has a stone in the pot and the water is cooking.
00:06:24.480 --> 00:06:25.920
And they're like, Oh, that's interesting.
00:06:26.079 --> 00:06:30.639
And he's like, Yeah, well, it would be really good if what this really needs is some carrots.
00:06:30.879 --> 00:06:33.680
And so someone's like, Oh, I got some carrots back at home.
00:06:33.839 --> 00:06:36.160
So they run out, get the carrots, bring them back.
00:06:36.240 --> 00:06:37.279
They put those in the pot.
00:06:37.439 --> 00:06:38.639
Oh, this is smelling really good.
00:06:38.879 --> 00:06:41.279
Some other people come by, they're like, Oh, what are you making?
00:06:41.519 --> 00:06:42.720
I'm making stone soup.
00:06:42.879 --> 00:06:45.279
Yeah, yeah, it would really be good if I added some potatoes.
00:06:45.439 --> 00:06:48.240
So, oh, we got some potatoes that run, get the potatoes, come back.
00:06:48.399 --> 00:06:49.439
And this goes on and on.
00:06:49.519 --> 00:06:52.160
You got the onions and then the meat or whatever.
00:06:52.240 --> 00:06:54.560
And eventually he's got like a whole stew.
00:06:54.879 --> 00:06:58.480
And at the end, it feeds him and everybody else.
00:06:58.800 --> 00:07:01.120
And there's a savvy to that.
00:07:01.279 --> 00:07:08.800
And uh something I love about that is that this guy didn't like contribute really anything except the container.
00:07:08.959 --> 00:07:22.319
Like everybody else brought the things, the things that actually made it nourishing, but he had the concept and he set the vision for it and invited people into what became this amazing stew.
00:07:22.560 --> 00:07:43.839
And so I think about that with lots of things, but particularly with conferences, because it's inviting lots of different people to contribute the things that they have, whether it's speakers or sponsors, volunteers, scholars, just people that are friends coming, bring somebody maybe new into the industry, and everybody's contributing their piece.
00:07:43.920 --> 00:07:48.240
And then all together, it like makes this really wonderful, like nourishing thing.
00:07:48.480 --> 00:07:50.160
But somebody has to make the container.
00:07:50.319 --> 00:07:56.000
Someone just has to be like, put this pot down, throw some stones and water in it, and say, ooh, this smells really good.
00:07:56.160 --> 00:07:57.519
You know what this needs?
00:07:58.240 --> 00:07:59.839
And it's kind of magical.
00:08:00.160 --> 00:08:00.480
Yeah.
00:08:00.639 --> 00:08:02.720
The first Blue Ridge was awesome.
00:08:02.879 --> 00:08:05.439
Still one of my favorite conferences that I've been to.
00:08:05.519 --> 00:08:07.279
It had a special energy to it.
00:08:07.439 --> 00:08:11.519
I've been to a lot of conferences that have a similar energy.
00:08:11.680 --> 00:08:15.600
And I feel like the consistency there is twofold.
00:08:15.680 --> 00:08:23.519
It's an organizer who really cares about putting on a great conference, and it's a small conference.
00:08:23.920 --> 00:08:29.759
No shade for Rails World or RubyCon for a big conference.
00:08:29.839 --> 00:08:36.720
Those are special in their own way, but there's something about those smaller where you get to meet everybody, talk to everybody.
00:08:37.039 --> 00:08:48.080
Especially Blue Ridge was the first one that I had gone to where you had that open lunch concept where instead of like you're sitting in this giant hall and there's some food there and you stand in line for it, and then you sit at a table with maybe eight people.
00:08:48.240 --> 00:08:58.000
If you're lucky, you go out into the city you're at and meet with giant groups, and like you can't walk past a restaurant without being like, hey, look, there's some Rubyists in there.
00:08:58.080 --> 00:08:59.120
And that was so cool.
00:08:59.279 --> 00:09:06.080
And yeah, Blue Ridge was great, and I'm super excited to see you back at it, organizing it and getting it going.
00:09:06.320 --> 00:09:08.000
The new space looks super cool.
00:09:08.159 --> 00:09:09.759
The original space was awesome.
00:09:10.000 --> 00:09:12.799
The new one looks like it can hold a few more people.
00:10:34.350 --> 00:10:35.309
It is smaller.
00:10:35.549 --> 00:10:39.149
It's old, 207 people seated.
00:10:39.789 --> 00:10:44.429
The previous space, I think it was maybe around 300, 350, I want to say.
00:10:44.669 --> 00:10:45.870
And I loved that space.
00:10:46.029 --> 00:10:49.069
The theater we were in originally was just gorgeous.
00:10:49.230 --> 00:10:50.189
I fell in love with it.
00:10:50.269 --> 00:10:53.709
They do weddings there because it's just like a beautiful space.
00:10:54.189 --> 00:11:00.669
But there were accessibility issues with that building that I didn't feel comfortable using it again.
00:11:00.829 --> 00:11:04.909
And so I decided to do a search for something else.
00:11:05.230 --> 00:11:07.870
And the WaiMai Cultural Center came up.
00:11:08.029 --> 00:11:10.429
It was actually just recently renovated.
00:11:10.589 --> 00:11:12.669
They've done a really nice job with the space.
00:11:12.750 --> 00:11:13.629
I think it's going to be great.
00:11:13.709 --> 00:11:15.789
And it has a lot of unique history to it.
00:11:15.870 --> 00:11:17.549
So I'm excited about that.
00:11:17.709 --> 00:11:27.069
They also have like a street level space that is somewhat separate from the auditorium that I'm planning to set up for like hangout space.
00:11:27.309 --> 00:11:28.909
And so I'm pretty excited about that.
00:11:28.990 --> 00:11:30.269
I think it's going to come out well.
00:11:30.509 --> 00:11:34.269
It may be that this ends up being like a long-term space for us.
00:11:34.509 --> 00:11:38.110
We'll see because the venue ends up being like just so challenging.
00:11:38.189 --> 00:11:47.309
Like you're trying to design everything else around the spaces that you have, and it determines your capacity and so many other things.
00:11:47.469 --> 00:11:51.789
So if it works out well, we may end up using them in the future.
00:11:52.269 --> 00:11:56.909
Also, venue is one of the biggest costs.
00:11:57.789 --> 00:12:07.309
I think video production might be the biggest, but then venue is like usually right after that, or they might be tied for first or something.
00:12:07.549 --> 00:12:09.149
So that's significant.
00:12:09.309 --> 00:12:12.269
And at least this year, it's pretty reasonable.
00:12:12.669 --> 00:12:13.870
So I'm happy about that.
00:12:14.029 --> 00:12:16.669
And I'm hoping I want to see if I can pack it out.
00:12:16.829 --> 00:12:20.509
If I can get 207 people seated in that space, I think it'd be great.
00:12:20.669 --> 00:12:22.509
So that's what I'm hoping for.
00:12:22.829 --> 00:12:32.269
And that was really the first thing was figuring out space because you can't do anything else until you know the time and place for something.
00:12:32.509 --> 00:12:35.949
You can't invite sponsors because you've got nothing to go on.
00:12:36.110 --> 00:12:39.230
You can't sell tickets because people don't know when it even is.
00:12:39.389 --> 00:12:41.709
You got to tell me, give me some dates here.
00:12:41.789 --> 00:12:43.709
You know, like there's so many other things.
00:12:43.789 --> 00:12:46.750
So it all hangs on that as the first piece.
00:12:46.909 --> 00:12:50.990
So getting that nailed down in, I think it was end of November was great.
00:12:51.069 --> 00:12:53.069
And then that really got us rolling.
00:12:53.389 --> 00:12:56.189
CFPs are open or open soon.
00:12:56.509 --> 00:12:58.669
They're open until February 3rd.
00:12:59.629 --> 00:13:04.829
We are a Ruby conference, so not necessarily a Rails conference.
00:13:05.069 --> 00:13:07.469
Blue Ridge is more broadly Ruby.
00:13:07.709 --> 00:13:19.629
Probably have some one or two talks related to Rails, and most people there will be probably working in Rails day to day, but the focus is Ruby, but really pretty general within Ruby.
00:13:19.870 --> 00:13:24.269
Really want to have a broad mix of topics and speakers.
00:13:24.990 --> 00:13:34.829
Yesterday I released a video where I talked about our CFP process and my sort of general advice on doing talk submissions.
00:13:35.230 --> 00:13:37.709
And it ended up being like 30 minutes.
00:13:37.789 --> 00:13:39.709
I didn't need to go on and on.
00:13:39.789 --> 00:13:41.629
I didn't realize I had so much to say about it.
00:13:41.789 --> 00:13:50.029
Actually, what who it was, it was Adrian Marinhee was like, hey, you need to make more videos as you like work on Blue Ridge just to share what you're doing.
00:13:50.110 --> 00:13:52.990
So I was like, okay, I'll start a behind the scenes kind of thing.
00:13:53.069 --> 00:14:01.949
And my first one was like the CFP process and my advice for people with sending talks to either our conference or other conferences, other Ruby conferences.
00:14:02.189 --> 00:14:04.269
And so I'm hoping that's helpful.
00:14:04.350 --> 00:14:08.750
And for folks that are interested, please, this is the time to be writing talk proposals.
00:14:08.829 --> 00:14:10.750
There's so many CFPs open right now.
00:14:10.909 --> 00:14:14.509
A few of them, RBQ conf is closing.
00:14:14.589 --> 00:14:15.870
He extended it one more day.
00:14:15.949 --> 00:14:17.309
I think it's closing tomorrow.
00:14:17.789 --> 00:14:19.230
That'll be January 8th.
00:14:19.389 --> 00:14:21.149
By the time this goes out, that'll be closed.
00:14:21.389 --> 00:14:22.110
That would be closed.
00:14:22.350 --> 00:14:29.230
There are some at the end of January, I
want to say, but check Rubyevents.org and there's a CFP page and you can see all the upcoming ones.
00:14:29.309 --> 00:14:32.589
But right now is the time to get talks out there.
00:14:34.429 --> 00:14:42.189
Biggest advice I have for people when it comes to CFPs is like don't wait for the acceptance to start fleshing out the talk too.
00:14:42.350 --> 00:14:47.709
Like I used to be very much team, submit the CFP and then write the talk if you're accepted.
00:14:47.870 --> 00:14:52.189
But like usually you're accepted and it's like you have so little time.
00:14:52.669 --> 00:15:11.389
It feels like a lot of time, but yeah, get out to go do like version one at a meetup virtually or in your town or something to get some reps in, especially if you're new to speaking, like it's completely different when you're actually in front of people giving the talk.
00:15:11.629 --> 00:15:16.110
Get the CFPs submitted and work on the talk.
00:15:16.669 --> 00:15:18.269
I always time track everything.
00:15:18.350 --> 00:15:22.189
So it usually takes me around 50 hours to put a talk together.
00:15:22.750 --> 00:15:29.389
And if that's my one thing I'm doing during that period, I can probably throw 10 hours a week at something.
00:15:29.469 --> 00:15:33.309
So I'm like five weeks is my minimum to put a talk together.
00:15:33.389 --> 00:15:35.069
But even that is kind of pushing it.
00:15:35.149 --> 00:15:42.029
So I'd rather have two months to get a talk together and feel like I was gonna do a good job when I came time to give it.
00:15:42.990 --> 00:15:48.189
So no tracks per se for Blue Ridge Ruby, just a single Ruby in general.
00:15:48.589 --> 00:15:51.389
Single track and no themes this year.
00:15:51.789 --> 00:15:54.189
Kind of like just having it kind of open like that.
00:15:54.350 --> 00:15:56.750
And we have 10 talk slots.
00:15:57.309 --> 00:16:04.509
So it's gonna be a challenge for us to really whittle that down and create a program that has something for everybody.
00:16:04.909 --> 00:16:07.389
But that is part of the fun trying to figure that out.
00:16:08.350 --> 00:16:11.309
Going through CFPs is a daunting task.
00:16:11.709 --> 00:16:12.269
It really is.
00:16:12.509 --> 00:16:24.429
Like it's practically like a week of work the week that it drops because people submit their proposals and then you have to hit the ground running because you need to get an announcement out probably the next week.
00:16:24.669 --> 00:17:24.230
So that week after February 3rd or that week, it's gonna be a ton of work, just reading lots of proposals and making lots of decisions, and then sending lots of messages to people, giving them updates on where their proposal stands.
00:17:24.710 --> 00:17:26.950
I'm sure you're gonna get a ton of good ones.
00:17:27.190 --> 00:17:36.470
I remember doing the CFPs for the last Rails Conf, and it was just like, I want to see so many of these talks, and we have so few slots to put them in.
00:17:36.630 --> 00:17:47.029
And it was like we had to give some no's where I just wanted to be like, can we write them like a very detailed, like your talk sounds freaking awesome, but we don't have enough space for everyone's talk.
00:17:47.110 --> 00:17:48.230
We're so sorry.
00:17:48.470 --> 00:17:55.670
It was just like, man, I hope please, please submit it to like everywhere else and let me know where accepted because I want to see this talk.
00:17:55.910 --> 00:18:00.230
That was part of my advice actually in the video I just made, which is like, this is a numbers game.
00:18:00.390 --> 00:18:05.030
And so submit more talk proposals and submit to more conferences.
00:18:05.270 --> 00:18:10.470
So many times, it's not that we would never use your proposal if it's a no.
00:18:10.630 --> 00:18:12.950
It's like, wow, we had so many good ones.
00:18:13.110 --> 00:18:16.950
I would love to see this the next year, or I'd love to see this in another conference.
00:18:17.190 --> 00:18:19.750
Maybe it needs a few tweaks and it would be great.
00:18:19.990 --> 00:18:22.550
But it's rarely like, nah, this is no good.
00:18:22.710 --> 00:18:24.550
You know, it's almost never that.
00:18:24.870 --> 00:18:30.710
When people can, if you put a few hours into a talk proposal, get it out to as many conferences as you can.
00:18:31.670 --> 00:18:32.470
Meetups too.
00:18:32.630 --> 00:18:35.110
Meetups are always looking for people to do speakers.
00:18:35.350 --> 00:18:40.790
You have an idea for a CFP, but maybe you don't know how to make it a 30-minute, 45-minute talk.
00:18:41.030 --> 00:18:45.110
Start with that 10-minute talk that you give at a meetup.
00:18:45.190 --> 00:18:48.310
And then as people field questions, you build your talk from there.
00:18:48.390 --> 00:18:53.190
And then when you feel like you have 30 minutes of content, you submit it to a conference.
00:18:53.510 --> 00:19:01.750
So there's a lot of stages to getting to be able to talk, talk about whatever you want other people to learn.
00:19:02.230 --> 00:19:10.150
But yeah, that's cool that you're doing the behind the scenes videos on everything going on with Blue Ridge, because it's still a mystery to me.
00:19:10.310 --> 00:19:15.670
Like, even getting involved with some of the ones in the past, I'm still like, oh, I would have never thought about that.
00:19:15.830 --> 00:19:17.510
It makes total sense now that I know it.
00:19:17.590 --> 00:19:19.750
But there are a lot of things like that.
00:19:20.070 --> 00:19:32.710
So even things like, all right, just this morning, I'm looking through Asheville trying to find like cool or interesting like foods that are made in the town.
00:19:33.030 --> 00:19:38.150
Part of what I think is great about regional conferences is that you get a flavor for this place that you're visiting.
00:19:38.310 --> 00:19:40.310
And Asheville has a really cool culture.
00:19:40.550 --> 00:19:41.990
It's pretty granola.
00:19:42.150 --> 00:19:45.750
There's a lot of like outdoorsy people, a
lot of hippie people.
00:19:46.710 --> 00:19:49.990
And so I was like, found this really good pizza.
00:19:50.310 --> 00:19:52.470
Yeah, mountain towns have good pizza.
00:19:52.550 --> 00:19:57.750
I don't know what this is, but I found like this guy that makes artisanal pickles.
00:19:58.310 --> 00:20:01.270
And I was like, hey, maybe I should do like a pickle bar, you know.
00:20:01.510 --> 00:20:03.510
So I'm just like looking at random things like that.
00:20:03.670 --> 00:20:04.790
Like, why are you doing this?
00:20:04.950 --> 00:20:09.910
Well, I want to give the experience of please don't quote me on the pickle bar.
00:20:09.990 --> 00:20:10.870
I don't know if I'm gonna do that.
00:20:10.950 --> 00:20:16.070
But it's just like I'm looking at these things like listen, if I get to Blue Ridge and there's no pickle bar, I'm gonna be pissed.
00:20:16.230 --> 00:20:17.190
I know, right?
00:20:17.590 --> 00:20:22.950
But sometimes, like, okay, you have like a sponsor who's like, hey, um, would love to be involved somehow.
00:20:23.190 --> 00:20:25.430
Are there any special opportunities that we could work out?
00:20:25.510 --> 00:20:28.310
And then I'm thinking, like, well, what could we do that would be interesting?
00:20:28.470 --> 00:20:34.070
What would be unique that you haven't seen in another conference that people would talk about later?
00:20:34.230 --> 00:20:35.990
They would be like, Oh, this is amazing.
00:20:36.150 --> 00:20:40.070
The first year we did the ice cream sandwich truck that came after the conference.
00:20:40.310 --> 00:20:40.870
That was super cool.
00:20:41.030 --> 00:20:41.590
I love that.
00:20:41.670 --> 00:20:42.310
That was so great.
00:20:42.390 --> 00:20:44.230
I mean, I didn't get to go down and do it.
00:20:44.390 --> 00:20:55.030
I was busy like cleaning up after the conference, but I did get to look, peek down from the third story window at everybody down below, you know, getting their ice cream sandwiches, and that was pretty awesome.
00:20:55.430 --> 00:21:03.030
So just like cool things like that helps an event stand out in your mind from every other event that you go to.
00:21:03.190 --> 00:21:05.350
Oh, that was the one where we did blah, blah, blah.
00:21:05.590 --> 00:21:06.470
That matters.
00:21:06.710 --> 00:21:14.070
And when we can do that along with sponsors who are looking for something unique to contribute to, I think that can be great.
00:21:14.310 --> 00:21:29.350
So I ended up on all these random rabbit trails, you know, trying to figure out like what would be interesting, what would be cool, and then these research projects that you never would have expected you'd be doing just because trying to create these unique experiences.
00:21:29.670 --> 00:21:31.910
Is that like a bit of a blocker?
00:21:32.550 --> 00:21:45.750
You live close enough that you're familiar with the area, and then you're like, how do I give someone a taste of this area that I know well in almost a familiar way?
00:21:45.830 --> 00:21:58.070
Like, I feel like if I'm very familiar with something, it's almost hard to give people an intro to it where I feel like you're getting the vibe of the thing that I'm trying to show you without being overwhelmed.
00:21:58.230 --> 00:22:00.630
Because if I'm very familiar, I'm like, I know all the things.
00:22:00.870 --> 00:22:03.110
I think the fact that I live that idea.
00:22:03.350 --> 00:22:04.550
I think the fact that I live an hour away.
00:22:04.950 --> 00:22:16.230
Way helps actually in this case because I know the stuff that people would want to go to Asheville for rather than living there and being like, oh, I'm so over this thing because all the tourists come here for that.
00:22:16.550 --> 00:22:18.310
So I think that absolutely happens.
00:22:18.470 --> 00:22:23.110
You get like blind to what's unique about the place that you live.
00:22:23.350 --> 00:22:28.790
But people that come to your town, fly or drive, spend the weekend in your town.
00:22:28.870 --> 00:22:33.910
And Asheville is a very popular holiday destination, weekend destination, that kind of thing.
00:22:34.150 --> 00:22:35.910
They're coming for particular things.
00:22:35.990 --> 00:22:44.870
They're coming for the Blue Ridge Parkway, for the hiking, for you know, all the outdoor activities, for the microbreweries, for the food scene, for the music scene.
00:22:45.110 --> 00:22:57.110
There's a certain sort of granola, hippie aesthetic that's there that is the outside flavor of Asheville.
00:22:57.430 --> 00:22:59.590
Well, that's really only one part of Asheville.
00:22:59.670 --> 00:23:02.630
There's tons of other things, you know, that aren't hippie granola.
00:23:02.790 --> 00:23:04.390
That's the reality of every place.
00:23:04.630 --> 00:23:13.990
But when people associate a place in their minds, they kind of want that experience, the sort of first pass experience of that place.
00:23:14.070 --> 00:23:19.110
And I think like Detroit Railscoff did a good job of playing up Detroit, for example.
00:23:19.270 --> 00:23:26.710
But people that are from Detroit might be annoyed, you know, like at some point, like, I don't want more Detroit-style pizza or any references to Motown anymore.
00:23:26.790 --> 00:23:28.470
You know, like, yes, I get it.
00:23:28.550 --> 00:23:30.390
Like, it's cliche now for us.
00:23:30.630 --> 00:23:34.630
But for the yeah, for them, you gotta give them the cliche.
00:23:34.790 --> 00:23:37.510
You know, you gotta give them the thing that they have the association with.
00:23:37.750 --> 00:23:42.790
Yeah, when everybody came to RailsConf in Philly, like you had to go get a cheesesteak.
00:23:43.030 --> 00:23:43.350
Oh, right.
00:23:43.430 --> 00:23:43.990
Yeah, absolutely.
00:23:44.230 --> 00:23:51.110
You don't come to Philadelphia and not get a cheesesteak unless you live here and you've had so many cheesesteaks you don't want to open it one ever again.
00:23:51.350 --> 00:23:55.190
Um, but that only
happens if you don't go to Shays.
00:23:55.750 --> 00:24:02.950
So, what kind of blockers do you have, either work-wise or related to the conference that you want to talk about?
00:24:03.350 --> 00:24:21.110
This is kind of a different direction, but Blue Ridge ended up being the thing that unblocked me to for one of my blockers, which is I've come to realize more and more that I'm the kind of person that always needs something going on the side, pretty much all the time.
00:24:21.270 --> 00:24:30.310
Either I'm deciding on the next weird thing that I'm gonna do on the side, or I'm doing it, or I'm like recovering from it and getting ready to do the next one.
00:24:30.550 --> 00:24:32.550
And it's kind of like endless for me.
00:24:32.710 --> 00:24:43.270
Like, and in the past, I used to feel bad about it, like guilty that I always need something to make life chaotic or stressing myself out.
00:24:43.510 --> 00:24:47.910
I've come to accept that it's just like part of my nature that I always need some project.
00:24:48.070 --> 00:24:54.310
And the last time I was on Code Encoders, it was when I was building Liminal, and that was my big thing.
00:24:54.390 --> 00:24:57.110
And this was like a little over a year ago.
00:24:57.430 --> 00:25:19.990
And that was a really fun project, and it didn't quite materialize the way I had hoped, but I did have a lot of fun building it and had a lot of great connections to people who were interested in how I was going about development, my product choices, and all the stuff that I was sharing about it.
00:25:20.230 --> 00:25:33.190
That was actually one of the big takeaways from building this app was a lot of the people that were most interested in hearing from me wasn't necessarily about my fresh take on old school forums.
00:25:33.350 --> 00:25:39.430
It was how I was thinking about building products and how I was building with Rails.
00:25:39.830 --> 00:25:58.550
And after that project, it sort of dawned on me that that was like who was already paying attention to me, other Rails developers and product focused people, and that I really enjoyed making videos and content for them.
00:25:58.710 --> 00:26:13.430
And so this past year, I changed some things around in the spring to kind of open up some time so I could work on a new project related to content that I was hoping to really get off the ground in 2025.
00:26:13.670 --> 00:26:18.390
And for a number of personal reasons, I wasn't able to pull that off.
00:26:18.870 --> 00:26:20.950
And it was really frustrating me.
00:26:21.350 --> 00:26:38.070
It was a combination of like needing a good amount of time and energy to put in this new venture, but also realizing like I didn't know if I had what it took to pull it off because there was no sort of upper bounds on the time it might take.
00:26:38.390 --> 00:26:51.590
And for me, like if I go too long without having this other side thing like that I'm working toward, it gets kind of depressing, or like I sort of
lose motivation.
00:26:51.750 --> 00:26:53.910
I kind of need a thing that I'm going for.
00:26:54.150 --> 00:26:56.310
The thing is, like, I still love my day-to-day work.
00:26:56.470 --> 00:27:00.470
I love working with my clients, I love building products, I love using Rails every day.
00:27:00.790 --> 00:27:11.430
But there's something about having some discretionary time that I put toward some bigger goal, some other thing that I have like complete control over.
00:27:11.750 --> 00:27:20.150
Maybe not complete, but a lot of control over that always makes me feel alive, feel excited, energized, all that.
00:27:20.390 --> 00:27:37.670
And so this other project that I was hoping to pull off, content-wise, because of the time commitments and because of also the changes with AI, I started to feel like will people like be as interested in Ruby and Rails related content now?
00:27:37.990 --> 00:27:39.830
And I started seeing people talk about that.
00:27:39.990 --> 00:27:55.830
Like Nate Burkapec had said something yeah, a while back about this that maybe no one's gonna even care to buy like dev-related content, or you know, if we can just ask LLMs for everything, like maybe it doesn't matter anymore.
00:27:55.990 --> 00:27:58.230
So I've been like concerned about that.
00:27:58.870 --> 00:28:10.230
So I needed something that was like exciting to look forward to, something to put this extra energy into, but that had like a clear outcome and a upper bounds to it.
00:28:10.390 --> 00:28:13.350
And that brought me back around to Blue Ridge.
00:28:13.590 --> 00:28:15.190
And that's really kind of where I landed.
00:28:15.350 --> 00:28:24.070
Blue Ridge ended up being a way to unblock myself on having sort of a next thing to work on that was exciting to look forward to.
00:28:24.310 --> 00:28:32.870
And I don't know why I need something stressful to keep me like excited, but there's some element of risk.
00:28:33.110 --> 00:28:34.390
I need something risky.
00:28:34.550 --> 00:28:35.990
I can't risk my client work.
00:28:36.070 --> 00:28:47.750
I can't risk my day-to-day work, but I need something that feels like risky, where there's some chance of not succeeding that gets me excited and feels like an adventure.
00:28:47.990 --> 00:28:49.910
I guess maybe that's the way to say it.
00:28:50.230 --> 00:29:01.030
And with this other project, it was too risky, maybe for where it was too much unknown, and I needed something slightly less risky to go after now.
00:29:01.270 --> 00:29:12.310
And with a conference, there's not like a real big blocker, it's just lots of details, just lots of details and lots of effort.
00:29:12.470 --> 00:29:15.430
But it's doable and there's a limit to it.
00:29:15.670 --> 00:29:19.110
By May 2nd, when the conference is over, it's pretty much done.
00:29:19.270 --> 00:29:24.870
Not entirely because video production is still being done, but basically done at that point.
00:29:25.030 --> 00:29:26.630
And so there is an end.
00:29:26.870 --> 00:29:29.110
And there's a moment in time for it.
00:29:29.350 --> 00:29:29.750
Yeah.
00:29:29.910 --> 00:29:36.470
And I also know because I time track things, that took me 250 hours of in 2023 to put on the conference.
00:29:36.630 --> 00:29:38.550
And I think I can probably do it in less.
00:29:38.630 --> 00:29:42.790
I'm aiming toward 200 hours between now and April 30th.
00:29:42.950 --> 00:29:48.710
So I think that also lets me know like I've got a reasonable idea of how much time I'm putting into this.
00:29:48.870 --> 00:29:51.430
And yeah, it's a lot of time, but it's doable.
00:29:51.590 --> 00:29:53.030
I can make this happen.
00:29:53.270 --> 00:29:58.390
But it's still that enough risk that feels like adventurous to me.
00:29:58.870 --> 00:29:59.830
That makes sense.
00:29:59.990 --> 00:30:05.350
That's a cool way to unblock yourself going and running a conference.
00:30:05.750 --> 00:30:09.990
Not, I think, one of the ways that someone's ever mentioned they unblocked themselves before.
00:30:10.150 --> 00:30:12.870
Like, I was feeling blocked, so I ran a conference.
00:30:13.190 --> 00:30:14.470
But I like it.
00:30:14.790 --> 00:30:19.510
You're very self-aware too, of like, I need something going on.
00:30:19.670 --> 00:30:30.870
I need, I hate being stressed by something, but at the same time, if I'm not a little stressed about it, there's a good chance that I'm not actively working towards it.
00:30:31.110 --> 00:30:39.830
Even when it comes to like programming books, hey, you can do these steps, and I like I get really engaged for the first few chapters, and I'm like, there's no risk here.
00:30:39.910 --> 00:30:44.790
Like, if I just put the book back on the shelf, no one knows, no one cares.
00:30:45.350 --> 00:30:47.430
Yeah, there's gotta be a little bit of stress.
00:30:47.590 --> 00:30:53.430
There's gotta be a little bit of fight or flight feeling for me to be like, all right, I gotta fucking do this thing.
00:30:53.590 --> 00:30:56.070
I gotta like, you know, works, got deadlines, works.
00:30:56.230 --> 00:31:00.790
If I don't do it, my project partner's gonna call me out, you know, my boss is gonna call me out.
00:31:01.110 --> 00:31:03.510
Okay, that helps me get my work done.
00:31:03.990 --> 00:31:10.150
I still enjoy what I do, which is why I do it, but the little bit of stress helps.
00:31:10.470 --> 00:31:12.790
That took me a really long time to figure out.
00:31:12.950 --> 00:31:18.310
I feel like I was like in my mid-30s when I was finally like, I need stress or I don't function.
00:31:18.630 --> 00:31:19.750
This is annoying.
00:31:19.990 --> 00:31:22.390
And I like my bulk rights.
00:31:23.030 --> 00:31:28.870
There's a fine line between the right amount of stress and too much, I think.
00:31:29.030 --> 00:31:31.350
And sometimes we go overboard.
00:31:31.510 --> 00:31:36.950
But I think especially when you can pick the thing that you're gonna be stressed about, it makes a big difference.
00:31:37.190 --> 00:31:44.550
There are plenty of things in my life that are super stressful that I did not pick, or I picked them so long ago that I don't even remember.
00:31:45.190 --> 00:31:50.310
But when I can pick a project like this and know, okay, I'm gonna be stressed about this.
00:31:50.470 --> 00:31:55.030
There are gonna be periods where I'm gonna be losing my mind.
00:31:55.350 --> 00:31:58.150
I'm so stressful, you know, I'm so stressed about this thing.
00:31:58.390 --> 00:32:07.270
But in general, it's gonna be a good stress because there is an upper limit to how much effort and energy and time I can put into this thing.
00:32:07.350 --> 00:32:12.070
There is a deadline, it will end, it won't go on in perpetuity.
00:32:12.310 --> 00:32:17.030
And at the end, there's like a real good outcome that I've seen before.
00:32:17.270 --> 00:32:26.630
And it may not be the same, and I could fail, and something could go wrong, but probably if I work hard enough and pay attention to the details, I'll be able to pull it off.
00:32:26.790 --> 00:32:29.750
Probably it's gonna turn out, and I'm gonna be happy I did it.
00:32:29.910 --> 00:32:34.550
And I may not be able to pull it off the next year, but I commit to this one at a time, you know.
00:32:34.630 --> 00:32:39.830
Like I think some people expect that with conferences that should sort of be like endless.
00:32:39.910 --> 00:32:41.590
You can always expect the next one.
00:32:41.750 --> 00:32:43.670
It's just on repeat or something.
00:32:43.830 --> 00:32:51.990
And I've come to realize that the people that can pull that off, that is pretty amazing and also pretty rare.
00:32:52.390 --> 00:33:00.630
And that really each time organizers commit to doing a conference again, it's a monumental effort for them.
00:33:01.190 --> 00:33:13.590
And taking it one at a time and making the commitment this time and the excitement for that, and not ever feeling the obligation to have to continue something forever.
00:33:13.830 --> 00:33:27.590
I don't know how you feel with a podcast, but I commit to a podcast, and there's like a somewhat of a schedule grind that you get into that means you're always on the hook in some ways for putting content out there.
00:33:27.990 --> 00:33:32.710
And I think you can't quite do that same kind of thing with a conference, or maybe you shouldn't.
00:33:32.790 --> 00:33:34.470
And maybe you shouldn't with podcasting either.
00:33:34.550 --> 00:33:35.110
I don't know.
00:33:35.350 --> 00:33:41.910
But at least on my side with Indie Rails, it does feel more doable, I guess, to say, all right, yeah, I can stay on the hook for this.
00:33:42.150 --> 00:33:46.310
Yeah, I have zero pressure in my podcast.
00:33:46.950 --> 00:33:50.790
If you haven't noticed, I think the last episode came out in November.
00:33:50.870 --> 00:33:53.750
I took all of December off because I was losing my mind at work.
00:33:53.910 --> 00:33:58.070
And like the first missed episode, I was like,
oh my God, like I can't miss another one.
00:33:58.230 --> 00:33:59.030
This is horrible.
00:33:59.110 --> 00:34:01.990
Like, people are expecting a new episode.
00:34:02.150 --> 00:34:04.710
And then I was like, but I'm stressed out.
00:34:04.870 --> 00:34:07.590
I won't give a good episode because I'm stressed out.
00:34:07.670 --> 00:34:09.590
And I'm like, I don't want to be doing this right now.
00:34:09.750 --> 00:34:13.110
I have so much work to get done before winter break starts, yada, yada.
00:34:13.269 --> 00:34:14.789
Like, no, you know what?
00:34:14.950 --> 00:34:18.470
No, I podcast mostly, there's a split.
00:34:18.550 --> 00:34:21.030
It's mostly for me because I enjoy talking to people.
00:34:21.110 --> 00:34:25.990
And then I just record the conversation and put it out, and that's my contribution to the community.
00:34:26.630 --> 00:34:28.950
But like, I don't owe that to anybody.
00:34:29.269 --> 00:34:46.789
I do want to get that's one of my goals for 2026, is to be a little bit more consistent about getting episodes out or at least planning my breaks, where I say, hey, there won't be a next episode on its normal cadence.
00:34:46.869 --> 00:34:51.670
The next episode will be X date because I'm taking a break rather than just disappearing off the face of the earth.
00:34:51.909 --> 00:34:53.430
But things happen.
00:34:53.670 --> 00:34:55.750
Totally, absolutely happen.
00:34:55.990 --> 00:35:09.269
I think it sounds like you've got a healthy relationship to what you're doing here too, which the thing that I think is dangerous about these kinds of things that we do is that you end up feeling resentful if you are on the hook.
00:35:09.590 --> 00:35:13.030
There can be a good way to feel like on the hook to deliver something.
00:35:13.190 --> 00:35:21.590
And if it's perpetual, you can hit a point where you feel like I'm just not in this anymore, but people still want it and I must do it or something.
00:35:21.670 --> 00:35:26.309
And that's, I think, a danger that I face that I have to watch out for.
00:35:26.550 --> 00:35:32.789
Because I can overextend myself because I want to be able to deliver the thing people want or something like that.
00:35:32.950 --> 00:35:42.150
And so I think it's really important, especially with those long-term recurring things that we're putting out to notice that when it's happening.
00:35:43.030 --> 00:35:45.349
The last question is always my favorite.
00:35:45.590 --> 00:35:54.550
It's what's something cool, new, or interesting, learned, built, discovered, doesn't have to be coding related, totally can be, can be coding adjacent.
00:35:54.869 --> 00:35:58.150
What do you have for cool, new, or interesting?
00:35:58.550 --> 00:36:00.389
Yeah, I was thinking about this.
00:36:00.630 --> 00:36:09.110
And if you had told me two years ago that I would be using LLMs a ton, I would have said, yeah, that makes sense.
00:36:09.349 --> 00:36:16.309
But if you told me two years ago that I would be talking to my computer as much as I am right now, that I would have been really surprised by.
00:36:16.389 --> 00:36:19.590
And so I've been using Whisperflow, and I know people are using that.
00:36:19.670 --> 00:36:22.150
And there are a few other tools people are using.
00:36:23.190 --> 00:36:25.269
I feel like Monologues one, I think.
00:36:25.429 --> 00:36:27.190
Yeah, monologue's a pretty popular one.
00:36:27.509 --> 00:36:28.309
From every.
00:36:28.389 --> 00:36:33.829
And yeah, so that's been like a real game changer, I guess, in some ways.
00:36:33.989 --> 00:36:44.789
Like I finally decided to pay for a subscription to that because I tried a few different tools and it felt like Whisperflow was it just fit me best, or whatever.
00:36:44.869 --> 00:37:08.070
And it's really weird because I want to say probably around 2018 or 2019, long before I was podcasting, or it was like a period of my life where I was doing tons of Rails development work, but I rarely had any conversations with my clients other than emails or yeah, mainly just email.
00:37:08.630 --> 00:37:13.909
I wasn't podcasting, I wasn't talking to, I didn't really have a lot of Ruby or Rails friends.
00:37:14.230 --> 00:37:25.509
And so I noticed when I started to do more content type stuff and podcasting that there was a period where it felt like I didn't even know how to talk.
00:37:25.670 --> 00:37:36.630
Like I don't even know if I can explain it, but I didn't know how to talk because I spent so much time either thinking or just typing or just writing, but not just like off the cuff speaking.
00:37:36.949 --> 00:37:47.909
And maybe because of that, I'm much more comfortable now talking to my computer when it comes to like, okay, Claude, here's what's going on, here's the thing I'm working on.
00:37:48.070 --> 00:37:49.590
I need to be able to do this.
00:37:49.909 --> 00:37:58.630
And so, like, that's been so weird to make that shift from writing, writing specs out to like just speaking.
00:37:58.869 --> 00:38:11.590
I think the the thing that's amazing is how it can use the context to know when I'm talking about a class or a module or a method, or get pretty close on a lot of those things.
00:38:11.909 --> 00:38:22.389
Because that seemed like the thing that would never work about it is you're referencing so many class names or method names, and you'd have to just go back and fix all of those.
00:38:22.789 --> 00:38:29.909
But it gets it right enough that it doesn't block me too much or doesn't block the flow.
00:38:30.150 --> 00:38:31.509
That's been really cool.
00:38:31.750 --> 00:38:33.989
Yeah, so I'm using that quite a bit.
00:38:34.150 --> 00:38:42.150
And then I've discovered that I am also using it more in my note-taking app.
00:38:42.389 --> 00:38:53.670
So now that I've got it, now that I'm like talking to my computer more, talking to Cloud Code, I'm also just talking into Bear, my Markdown note-taking app.
00:38:54.150 --> 00:39:06.630
As I'm working on any
given project, I'm often summarizing for myself, like, okay, at this point, I've got this part done and I'm struggling to decide how to approach this next piece.
00:39:06.789 --> 00:39:10.230
And I'm just like saying this out loud and putting this in this.
00:39:10.389 --> 00:39:16.710
I usually have one big note for every major project or feature that I'm building.
00:39:17.029 --> 00:39:22.949
And so this note can get really long, but it summarizes everything that I've been working on.
00:39:23.029 --> 00:39:28.869
And I can go back by day and figure out, oh, this is what I was working on in previous days or whatever.
00:39:29.110 --> 00:39:34.469
And now I'm just like doing these summaries now with Whisperflow as well.
00:39:34.789 --> 00:39:37.029
And that also is really helpful.
00:39:37.269 --> 00:39:41.269
But it's such a dramatic shift from what I was doing five years ago.
00:39:41.590 --> 00:39:47.029
Yeah, AI definitely flipped our jobs in so many ways on their head.
00:39:47.110 --> 00:39:58.869
Like, I still feel like if you boil down when I first started programming professionally and I had to explain what I did, I feel like that explanation isn't too different anymore.
00:39:59.029 --> 00:40:00.309
Like I'm still problem solving.
00:40:00.389 --> 00:40:12.789
I'm still like taking a complex feature and I'm breaking it down into like executable bits and like then developing an architecture and yada yada for the code itself.
00:40:13.190 --> 00:40:17.750
The biggest shift has been like I type the code a lot less.
00:40:17.989 --> 00:40:22.550
In some ways, it's like I went from using a manual hammer to like a nail gun.
00:40:22.789 --> 00:40:28.230
You still have to know how to build a house correctly, or the nail gun's not going to do you any good.
00:40:28.389 --> 00:40:37.349
Like I feel like AI, if you don't use AI well, garbage in, garbage out, you get crap code from it, and you're just like, this is useless.
00:40:37.509 --> 00:40:38.309
You suck.
00:40:38.389 --> 00:40:40.789
Um then it goes, you're absolutely right.
00:40:42.309 --> 00:40:51.909
But yeah, like learning how to use those tools is the way that we get to continue to do what our jobs were, but it is so different.
00:40:52.550 --> 00:40:55.989
Yeah, I do miss writing straight out writing code.
00:40:56.070 --> 00:40:58.230
I just feel like I don't do it anymore.
00:40:58.789 --> 00:41:08.789
I do like to tweak something, I'm like, I'm not gonna use an LLM to like tweak this method or something, but like I really don't have to write out syntax much anymore.
00:41:09.029 --> 00:41:13.989
I have to like read the code that AI wrote and make sure it's not, yeah.
00:41:14.070 --> 00:41:17.670
I've called it out, been like, this is overly complex.
00:41:17.829 --> 00:41:28.710
And it's like, you're absolutely right, too complex, and like we trim it down, but yeah, writing code, it always was way less of my job than I thought it would be when I was in school.
00:41:28.949 --> 00:41:32.150
And it's like borderline non-existent now.
00:41:32.309 --> 00:41:33.509
It's crazy.
00:41:34.150 --> 00:41:47.509
I think there are some cases maybe where I'm writing there's a part of a client app or a way their architecture is that is overly complex and has a lot of indirection.
00:41:47.989 --> 00:41:52.630
And I was trying to reimagine what it would look like if I simplified it.
00:41:52.869 --> 00:42:03.029
It was easier for me to just try to take a fresh sheet of paper and do that myself for one class and then try to explain all of that.
00:42:03.349 --> 00:42:04.550
Maybe I guess I could try it to.
00:42:04.949 --> 00:42:08.070
Other way as well and tell Cloud Code exactly what I was thinking.
00:42:08.230 --> 00:42:10.949
But I felt like I needed to feel it myself.
00:42:11.909 --> 00:42:15.029
I wouldn't be able to get to the architecture by looking at the rest of the app.
00:42:15.429 --> 00:42:22.230
One thing that's Cloud's great at is looking at everything else in your app and building the same way.
00:42:22.389 --> 00:42:25.670
But if you're not happy with the way it's built, what do you do?
00:42:26.070 --> 00:42:35.590
You could certainly do refactoring, but it seems like there's a like a tendency toward reverting toward whatever is in the code base as it currently stands.
00:42:35.750 --> 00:42:40.389
And if you want a new pattern, you might have to be pressing harder to make that happen.
00:42:40.710 --> 00:42:44.070
But yeah, a lot of it is just talking.
00:42:44.230 --> 00:42:54.150
And then, you know, like yesterday saying, hey, I need you to add a validation to ensure that the started at timestamp is in the future.
00:42:54.389 --> 00:42:56.230
And then it wanted to do a custom validation.
00:42:56.309 --> 00:42:58.230
I'm like, well, you can use a comparison.
00:42:58.389 --> 00:43:00.710
You know, there's a built-in validate comparison.
00:43:00.789 --> 00:43:01.829
You don't have to do this.
00:43:02.070 --> 00:43:04.309
So it was trying to do custom validations a bunch.
00:43:04.389 --> 00:43:06.070
And I'm like, nah, that's not the way I want.
00:43:06.150 --> 00:43:07.750
I know there's another way to do this.
00:43:07.989 --> 00:43:12.550
And it's But if you didn't know that, if you didn't know that, you would just accept whatever the AI spit out.
00:43:12.630 --> 00:43:14.710
And that's where that ends up being the job.
00:43:14.869 --> 00:43:16.389
You can't give the horse its head.
00:43:16.550 --> 00:43:21.989
Like I'm always thinking about this being like, all right, we used to have like hand-drawn carts, and now we have horses.
00:43:22.070 --> 00:43:31.190
We figured out how to hook horses up to our carts, but that means now I've got to hold the reins and I've got to learn not to give this horse like its head to go wherever it wants to go.
00:43:31.349 --> 00:43:32.949
No, we're not going off into the forest.
00:43:33.110 --> 00:43:34.550
You've got to stay on the road.
00:43:34.789 -->
00:43:36.070
We're going this way.
00:43:36.309 --> 00:43:38.389
No, we can't stop at the stream to drink right now.
00:43:38.469 --> 00:43:40.070
You need to keep going or whatever it is.
00:43:40.150 --> 00:43:46.550
You know, like we gotta maintain it's not under our own power anymore, but you're still directing.
00:43:46.710 --> 00:43:49.670
And you can't just give it its head and let it go wherever it wants.
00:43:49.829 --> 00:43:52.710
It needs to Yeah, you still have to know your shit.
00:43:52.949 --> 00:44:05.429
If you know nothing about programming, about web development, about how HTTP works, you can talk to an LLM and maybe get some good information, but LLMs hallucinate.
00:44:05.590 --> 00:44:06.789
These tools aren't perfect.
00:44:06.869 --> 00:44:13.989
Like you just said, like it was trying to do custom validation, which is a totally valid solution in some cases.
00:44:14.150 --> 00:44:15.989
But in that case, like there was a better solution.
00:44:16.070 --> 00:44:21.829
That's where it's like when you were talking about are people gonna want dev content now that we're using LLMs and stuff?
00:44:21.909 --> 00:44:29.269
And I would argue yes, the smart people will, because like you still have to know how to do this stuff.
00:44:29.509 --> 00:44:33.750
Sure, you can build a whole SaaS project in a week now with LLMs.
00:44:33.909 --> 00:44:35.909
Can you maintain it for five years?
00:44:36.550 --> 00:44:40.070
Maybe you just let AI just do its thing all the time.
00:44:40.230 --> 00:44:42.070
It won't matter if it's maintainable.
00:44:42.389 --> 00:44:44.630
Maybe we'll see in five years.
00:44:44.949 --> 00:44:48.949
There's a group of people that say that, and I'm definitely not there yet.
00:44:49.349 --> 00:45:02.469
No, I think that it's still super important to like enforce boundaries with architecture, with the code it writes, with the manner in which consistency is done.
00:45:02.630 --> 00:45:13.750
I think Ruby on Rails, having the convention over configuration, makes it really good for AIs to write Rails code because there are these guardrails.
00:45:14.469 --> 00:45:15.909
You do it this way.
00:45:16.150 --> 00:45:24.630
And as long as you know what you're doing or what it should at least look like or feel like, you can use AI to get stuff out very quickly.
00:45:24.789 --> 00:45:29.269
You just have to make sure that you're not just blindly going, yep, do whatever you want.
00:45:29.349 --> 00:45:31.029
Yep, do whatever you want, yep, do whatever you want.
00:45:31.110 --> 00:45:31.829
Here's a PR.
00:45:31.989 --> 00:45:35.429
And then we'll have a different AI agent review that PR and then merge it.
00:45:35.509 --> 00:45:38.389
And we'll never actually look at the code and hope to God it works.
00:45:38.630 --> 00:45:39.429
Come on now.
00:45:39.590 --> 00:45:40.309
I don't know.
00:45:40.630 --> 00:45:43.269
AI changes so quickly, I could be very wrong.
00:45:43.349 --> 00:45:55.429
And in like a year, we
could be having a completely different conversation about our jobs, but it just feels like the best code that AI is writing is the code that's very much guided along.
00:45:56.150 --> 00:45:57.590
That's in my experience.
00:45:57.750 --> 00:45:58.070
Yeah.
00:45:58.230 --> 00:45:58.550
Yeah.
00:45:58.710 --> 00:45:59.750
That's where I'm at.
00:45:59.909 --> 00:46:07.269
I think I was blown away this summer when I had a couple friends of mine that I'm in a group chat with that were like, you gotta try cloud code.
00:46:07.429 --> 00:46:09.110
And I was like, all right, I'll try it.
00:46:09.190 --> 00:46:11.829
And then it was like, oh, okay, okay.
00:46:12.070 --> 00:46:16.710
And then it was like periods in the fall where I was like, oh man, I don't know what's gonna happen here.
00:46:16.789 --> 00:46:17.509
Man, I don't know.
00:46:17.670 --> 00:46:21.349
And I think at the end of the year, I was finally like, all right, I'm happy with this.
00:46:21.509 --> 00:46:23.509
I think this is a net positive.
00:46:23.909 --> 00:46:26.949
I don't want to go back the previous way.
00:46:27.110 --> 00:46:39.029
There are some things that were really nice about that, but I'll tell you, there are days where I'm like, where in the past, if I was hitting a mental exhaustion and I was just like, I can't get my brain to go there.
00:46:39.190 --> 00:46:40.150
I can't think.
00:46:40.469 --> 00:46:43.029
Now I can just keep talking.
00:46:43.269 --> 00:46:45.349
All right, I don't know the best way to do this.
00:46:45.590 --> 00:46:48.789
Instead, I'd be like thinking about like, how do I solve this problem?
00:46:48.949 --> 00:46:50.789
Or I don't, I'm stuck.
00:46:51.029 --> 00:46:55.429
Now I can just talk my way out of it or say, like, give me a solution.
00:46:55.590 --> 00:46:57.190
And then I can say, no, not that.
00:46:57.349 --> 00:46:57.909
That's not it.
00:46:58.070 --> 00:46:58.710
That's not it.
00:46:58.869 --> 00:47:04.550
It's much easier to be in that mode, you know, like the edit mode than in the raw creation mode.
00:47:04.710 --> 00:47:08.150
It takes a certain level of energy or a certain kind of focus.
00:47:08.469 --> 00:47:11.429
And if there are times I don't have that, there are.
00:47:11.590 --> 00:47:12.789
There are times that I don't have that.
00:47:12.949 --> 00:47:17.509
And in the past, I would have just pushed through and probably not been very productive.
00:47:17.670 --> 00:47:20.550
And now I can just say, like, all right, have at it.
00:47:20.630 --> 00:47:24.469
I'm just explaining it, and then I'll tell you why I don't like your idea.
00:47:24.550 --> 00:47:26.630
But it'll probably get me unblocked.
00:47:26.869 --> 00:47:27.190
Yeah.
00:47:27.429 --> 00:47:37.190
Something I used to do was like write everything a few different ways because I didn't know exactly how I wanted it laid out, or like I get halfway through and be like, oh, you know what?
00:47:37.269 --> 00:47:38.550
I made the wrong decision in the beginning.
00:47:38.630 --> 00:47:39.829
Let me start from scratch.
00:47:39.989 --> 00:47:42.469
Like I try not to tie myself to my code too much.
00:47:42.550 --> 00:47:52.710
That way I gave the best version of it after seeing a couple of different solutions for bigger things, obviously, but like so much easier with AI to just be like, let's write it this way.
00:47:52.869 --> 00:47:55.590
Okay, stash that or just completely get rid of it.
00:47:55.829 --> 00:47:57.110
New context.
00:47:57.429 --> 00:48:03.909
Same goal, same feature, different prompt, different way of explaining what I want and see what that looks like.
00:48:04.070 --> 00:48:10.869
Sometimes just running the prompt twice, that kind of experimentation helps too.
00:48:10.949 --> 00:48:18.070
Cause then, like you can tell Claude to like remember things it learned by like updating its own file.
00:48:18.230 --> 00:48:19.590
That's really helpful too.
00:48:19.670 --> 00:48:24.789
Where it's like, we went through all these iterations, and this is the solution, and here's why this works.
00:48:24.949 --> 00:48:29.110
Now update your memory so that next time I ask you, we don't have to go through nine iterations.
00:48:29.190 --> 00:48:31.590
Like, it's sort of like working with a junior at times.
00:48:31.750 --> 00:48:35.989
I'm leveling you up, but it needs those guardrails, and you are the guardrails.
00:48:36.710 --> 00:48:41.029
There's a nice part about that, what you were saying, like being able to do it multiple ways.
00:48:41.269 --> 00:48:53.670
There's this idea of the diverge, converge phases of any project, and diverge is where you're trying to produce a bunch of concepts for something.
00:48:53.829 --> 00:49:04.070
Like you're building a feature, and maybe you have a first concept of what that feature is going to look like, how it's going to function, but your first idea for it might not be the best one.
00:49:04.230 --> 00:49:05.429
Same with implementation.
00:49:05.590 --> 00:49:08.630
Your first idea for how you might implement it might not be the best one.
00:49:08.789 --> 00:49:11.750
So diverge is like, let's try a bunch of options.
00:49:11.829 --> 00:49:15.670
And then once we see them, we can converge back to the final.
00:49:16.309 --> 00:49:17.750
But that can be an expensive thing.
00:49:17.909 --> 00:49:20.309
So people often do it in design phases.
00:49:20.469 --> 00:49:22.469
Like for visual design, you might do this.
00:49:22.630 --> 00:49:25.190
All right, we're rebranding our site or our app or whatever.
00:49:25.269 --> 00:49:28.309
We're going to do try three different flavors or whatever.
00:49:28.630 --> 00:49:32.710
You might also do that architecturally or with a feature now.
00:49:32.789 --> 00:49:38.949
And it's much less expensive to do the diverge stage now because you can just throw an LLM at it.
00:49:39.110 --> 00:49:46.389
Even if you did one of them yourself, you could let LLMs do two more at very low cost and very low time
commitment.
00:49:46.630 --> 00:49:49.429
And then converge once you've got like those laid out.
00:49:49.590 --> 00:49:51.110
Like, actually, that's the one we want.
00:49:51.190 --> 00:49:53.190
Or it's going to be a combination of A and B.
00:49:53.349 --> 00:49:57.750
Then you've probably done better than if you just tried one thing itself.
00:49:57.989 --> 00:49:59.829
Sometimes you know, but sometimes you don't.
00:49:59.909 --> 00:50:02.230
And it's really helpful to see the options.
00:50:02.550 --> 00:50:02.869
Yep.
00:50:03.029 --> 00:50:03.989
It's a nail gun.
00:50:04.070 --> 00:50:05.909
You still got to know how to build the house.
00:50:06.150 --> 00:50:09.750
The nail gun just helps you do it faster once you know what you're doing.
00:50:10.230 --> 00:50:14.150
That may be a naive way of looking at AI.
00:50:14.230 --> 00:50:18.309
Maybe I'm not being bullish enough on it, but it's that's been my experience.
00:50:18.389 --> 00:50:21.909
Like I've definitely adopted it more.
00:50:22.070 --> 00:50:23.750
We started using it at work.
00:50:23.829 --> 00:50:32.949
Like we spent all of November like really trying it, really making sure that we were using it in our projects, even if it slowed us down to like get used to it.
00:50:33.269 --> 00:50:38.630
Like a concerted effort that helped me a lot be more comfortable with it and see the advantages of it.
00:50:38.710 --> 00:50:41.750
But it also helped me realize like it is just a tool.
00:50:42.389 --> 00:50:50.070
It's probably the same way people like who were programming with punch cards, and then we had a compiler, were like, it's stupid.
00:50:50.230 --> 00:50:51.349
It could never replace us.
00:50:51.429 --> 00:50:52.630
And then like they learn how to use it.
00:50:52.710 --> 00:50:54.389
And they're like, oh, I still have a job here.
00:50:54.469 --> 00:50:55.349
I still have a role here.
00:50:55.429 --> 00:50:56.949
I still have a purpose here.
00:50:57.349 --> 00:50:58.389
I guide the thing.
00:50:58.550 --> 00:51:00.869
The compiler just helps us do it faster.
00:51:01.190 --> 00:51:01.590
Zip.
00:51:01.829 --> 00:51:02.389
That's it.
00:51:02.949 --> 00:51:05.590
Those are at least my crazy ass thoughts.
00:51:05.829 --> 00:51:06.710
That's my feeling.
00:51:06.789 --> 00:51:10.949
Like, I in the middle of the summer, I thought, like, how disruptive is this?
00:51:11.110 --> 00:51:11.989
I don't know.
00:51:12.230 --> 00:51:17.029
I think at this point, yes, it's very disruptive, but I still have work.
00:51:17.429 --> 00:51:19.590
This is making me work more productive.
00:51:19.829 --> 00:51:25.590
And it was harder to learn programming in general than learn how to use cloud code.
00:51:26.309 --> 00:51:27.670
I've picked these things up.
00:51:27.829 --> 00:51:32.150
And you know, I may not be the best at it, but I've already adopted them into my workflow.
00:51:32.309 --> 00:51:35.670
My workflow has changed dramatically, but I'm still doing my job.
00:51:35.909 -->
00:51:37.590
And I'm happy about that.
00:51:37.909 --> 00:51:40.389
For Blue Ridge, are you still looking for volunteers?
00:51:40.630 --> 00:51:41.269
I forgot to ask that.
00:51:41.429 --> 00:51:41.509
Yeah.
00:51:42.469 --> 00:51:51.029
Um thing that's important with volunteers is figuring out like all the sort of roles that you need filled.
00:51:51.190 --> 00:52:00.789
Because often you can have a lot of people that are interested, but you need to kind of know ahead of time like, here are the things that need to be done that I can sort of hand off to volunteers.
00:52:00.949 --> 00:52:02.869
I do need to sit down and plan those out.
00:52:02.949 --> 00:52:05.110
But yes, I'm looking for volunteers.
00:52:05.429 --> 00:52:06.789
We're still looking for sponsors.
00:52:06.949 --> 00:52:09.509
Obviously, CFP's open, so the speakers.
00:52:10.070 --> 00:52:12.150
Yeah, so all of it's wide open.
00:52:12.309 --> 00:52:25.509
I will be probably doing like a volunteer kickoff meeting in the next couple weeks to just say hello to everybody that wants to help and sort of divvy out some responsibilities.
00:52:25.670 --> 00:52:31.349
And some of those will happen prior to the conference, and then there'll be the ones that are like specific to the conference.
00:52:31.429 --> 00:52:35.110
Because if you're helping with registration, that's like a thing that you do during the conference.
00:52:35.269 --> 00:52:39.110
But you know, there might be other things that that we need sort of earlier on.
00:52:39.190 --> 00:52:41.509
So depending on what people have time for.
00:52:41.829 --> 00:52:42.469
Okay, cool.
00:52:42.630 --> 00:52:51.029
So if you're interested in speaking, volunteering, or sponsoring Blue Ridge Ruby, get in contact with you, or is there a Blue Ridge Ruby Direct?
00:52:51.429 --> 00:52:55.590
Yeah, team at Blue RidgeRuby.com is great if you're interested in volunteering.
00:52:55.829 --> 00:53:02.630
If you are interested in sponsoring, we have a sponsors page and contact information there, and the CFP is on the site as well.
00:53:02.710 --> 00:53:03.750
So all of this there.
00:53:03.989 --> 00:53:05.110
Yeah, cool, man.
00:53:05.349 --> 00:53:08.949
Anything else before we wrap it up that you want to talk about?
00:53:09.429 --> 00:53:10.789
I think we think that's it.
00:53:10.869 --> 00:53:10.949
Yeah.
00:53:11.349 --> 00:53:11.509
Cool.
00:53:11.989 --> 00:53:13.509
Looking forward to Blue Ridge Ruby.
00:53:13.590 --> 00:53:14.389
It's a great conference.
00:53:14.550 --> 00:53:17.829
Asheville's an awesome place to host something like that.
00:53:18.070 --> 00:53:21.670
And the extracurriculars at the end are always good.
00:53:21.989 --> 00:53:24.070
So definitely looking forward to that.
00:53:24.230 --> 00:53:27.670
And appreciate you coming back on the show and talking about it.
00:53:27.829 --> 00:53:30.789
And I'll definitely see you in April.
00:53:31.029 --> 00:53:34.949
Yeah, so Blue RidgeRuby.com, right, is the site.
00:53:35.110 --> 00:53:39.349
You're on Blue Sky and X and all the places.
00:53:39.670 --> 00:53:41.269
Ruby Social and LinkedIn.
00:53:41.429 --> 00:53:41.590
Yeah.
00:53:41.750 --> 00:53:44.710
And now when I do LinkedIn, we're doing the socials.
00:53:45.029 --> 00:53:45.110
Yeah.
00:53:45.509 --> 00:53:45.590
Okay.
00:53:46.070 --> 00:53:46.309
Yeah.
00:53:46.789 --> 00:53:48.550
Everywhere on the socials.
00:53:48.869 --> 00:53:49.349
Awesome.
00:53:49.509 --> 00:53:51.269
Well, folks, I'll see you in the next one.
00:53:51.349 --> 00:53:52.949
Jeremy, thanks again for coming on.
00:53:53.190 --> 00:53:55.029
We're looking forward to having you on again.
00:53:55.349 --> 00:53:55.989
I appreciate it.
00:53:56.070 --> 00:53:56.469
Yeah.
00:53:56.630 --> 00:53:58.309
Look forward to seeing you soon.
00:53:58.869 --> 00:53:59.349
Bye.