South Bend Software Craftsmanship w/Ross

Hi, I’m Mike. I’m sitting down here with Ross and David from South Bend Software craftsmanship User Group. We’re just going to talk a little bit about the user group that they run. So can you just tell us a little bit about what you guys do with the South Bend User Group? Obviously it’s in South Bend, but can you give a little bit more details? Sure. So I’ll start with a little bit of history. We used to have a dinette user group that was dying and we decided that we needed to make a language agnostic, a technology agnostic, and we had a couple people going up to Chicago to their Software craftsmanship user group and we liked what we saw and we connected with some of the people there to get ideas and assistance and we just started the group in South Bend. We meet once every two months and a typical meeting is a speaker talks for a little while and then we just have an open discussion afterwards with the speaker. Right. So if I had to give advice for the smaller cities like South Bend, reach out to the software craftsmanship community in a big city near you because Chicago has been instrumental in helping us. They’ve been sending out speakers like Uncle Bob and people from Teva Groupon and A-Flights interested in helping us out as well. So definitely look for help, there’s plenty of people in the community that are willing to help. Yeah. So like you said you go on a kind of semi monthly cycle. Why don’t you guys go out there and give advice to the smaller cities like South Bend? There’s plenty of people in the community that are willing to help. Yeah. So like you said you go on a kind of semi monthly cycle. Yeah. So why don’t you guys go semi monthly versus doing a monthly schedule that seems to be kind of a common pattern? I think part of it is like Russ mentioned, we were talking earlier just for the workload. Yeah. But I think that our goal would be to do it more often and we’re moving towards having weekly meetings to begin moving to the Ruby world and I imagine our goal would be to do at least once a month with a whole team to do one of these speakers or something like that. So I’m curious, like you explicitly said Ruby. What is it about? Why do you gravitate towards Ruby versus just any other Python or? So our town is primarily .NET so it’s just introducing diversity and different schools of thought and Ruby has kind of a community mindset anyway and so just to bring, find those who do know Ruby that we’re not connecting with, bring those into our group would also increase our sense of community as well. I think for, the Microsoft guys are used to having a Microsoft-ish kind of community. Right. And we’d be able to move. It’s harder to find the same sort of thing with PHP or Python or not as close-knit but we want to move out of a compiled language, I did anyway, move the team out of a compiled language into a dynamic language and just see what would happen there and Ruby’s, you move into another place where there’s already a home, there’s a house there built. Oh yeah, so it’s, it’s, you have kind of a preconceived notion of the community that comes from. Yeah. You have an established Microsoft developer base and you’re looking at, well, where else could we go from that and looking at the Ruby community which has been really active, what were you saying, that, that seems to be kind of appealing like an easier transition because you kind of have an idea of where you’re going to, not kind of. A bunch of atoms. Yeah. Yeah. Yeah, I’d like to stress that, that the Software craftsmanship group is technology agnostic. Right. We still have speaking, our speakers talk about, you know, Software craftsmanship. Right. We still have, you know, soft skills or, or higher level, you know, themes. Yeah. So, but we also need to have the people get used to getting together and pair program and stuff like that and so we’re using Ruby since it’s a new language as an avenue to do that. So we’re going to teach people Ruby, get them together and do contests together, learn how to do TDD and stuff like that. So it’s, that’s just the focus we’re taking. And you know, we, we did have a little brief conversation before and we talked about how, you know, South Bend. You’re kind of a, it’s a, it’s more of a residential community where people are commuting to and from South Bend. So you have a little bit of a challenge dealing with trying to get people in, in the evenings or in the early mornings. You know, like what is your attendance of like when you’re trying to do an evening meeting? Does it usually seem to be over, overly impacted by the fact that people are commuting to South Bend? Sure, since we meet once every two months, our meeting attendance is usually 30 or so, which isn’t bad. But for the more collaborative building type meetings that we have, like a Coden Coffee, which Coden Coffee is usually in the morning, which we have trouble getting people to come out. So for this Ruby exercise, we’re going to, we’re going to partake in here. We’re going to do it during lunches. So we’ll just meet at a, at a kind of a common place consistently once a week. And we think we’ll get a lot better attendance at lunchtime. Yeah. Yeah. Lunch is, having a family myself, I could, I can attest to those midday breaks are a little bit easier to, to accommodate the schedule. Yeah. Okay. Well, you guys have a website. We’ll be posting that along with the, the LinkedIn, well, what is the website? Just. Actually we have a LinkedIn group. Oh, you have a LinkedIn group? Okay. Yeah. But we are evaluating different methods. Okay. Is it a public group that we’ll be able to link to? Yes. Okay, great. All right. very much, Ross and David. Appreciate you sitting down with me. Take care.