Podcast Episode 209: Episode 182: We Get To Do This

Description

Dive into how we can celebrate the amazing work taking place, along with some exciting updates you won’t want to miss.

Transcribed Content

This episode of Rockcast is brought to you by Rock partner Triumph Tech, a full service specialist partner. Rock partners provide crucial support for Spark Development Network and important services for the Rock community. Connect with Triumph Tech today at rockrms.com/partners. Welcome to RockCast. This is the podcast dedicated to the Rock community. I'm Emily Forman, and here with me are Jon Edmiston and Nick Airdo, and we are going to fill you in on what's happening with Rock right now. Right now. Right now. Take it away. Well, we got a lot to talk about. But before we jump into product, I thought, hey, this is a good time to talk about current events. And many of you think I'm talking about the election. I'm not. In fact, we're going to relabel this semi current events. Perfect. Because this one was just a little bit ago. The event I wanted to talk about is, , when we work in this technology field and end product fields, it's really encouraging to see others around you and then their successes. A couple weeks ago, SpaceX had a huge successful launch. Now I know most of you listening to the podcast know about what I'm talking about, but for those who don't, let me just give a little bit of background. So for years, SpaceX has been launching their Falcon rockets, which are very large. But in comparison, they're very large. They've in fact, I think this week launched their four hundredth launch. And these things, they just land themselves. how crazy is that? Hopefully you've all seen that. Especially when they land in pairs. That's just incredible. I mean, it's just amazing though, world that we live in. But a couple weeks ago, they have their new Starship. Now the Starship rocket is huge. It makes the Apollo 11 look just a little teeny thing. It's 39 feet tall. 40 Feet? 39 feet? I'm sorry. It's a thirty nine thirty nine story building. So three ninety feet. That's That is always 10 feet per per story. So a 39 story building gets launched into the sky. Right? But the big thing is 23 stories comes back and lands not on its own, but it lands inside of the same launch tower. This one of these two little chopsticks. They caught it with little chopsticks. Now, I'm sure most of you saw that in the news, You probably saw the clip. I'm telling you it's different though when you watch it live. You have to watch these things live, unfortunately they're very early in the morning if you live on the West Coast, but it's worth it. It is so worth it. It's just an amazing energy experience, and of the things I wanted to do is just talk about that experience, that some of you, if you just only saw the news, you might have missed, or you might have just heard a semi little clip of it. So I wanted to play a clip of if you had been there and you were listening and you weren't , we can't show you the visual, but if you were listening, what you would have heard. So let let's play that clip. We're now down to three Raptor engines. Okay. So this point, it's coming in for landing. The first ever attempt, we have successfully caught the super happy booster back at the watch tower. Okay. Landed, but keep going. Are you kidding me? Yeah. So those people cheering are the SpaceX employees. how incredible is that? Hundreds of them are just standing around just watching this thing that they built, just do an amazing thing. It's so encouraging. We need to take so much inspiration from that. I joined John in getting up early to watch those, they are unbelievable. And it's just amazing to hear that. I think there's a few things that we can learn from that. First of all, what are they cheering? They're not cheering the product, right? They're not cheering the rocket, they're cheering what the rocket is doing, the mission, the action of the rocket. So it's not about the product. They don't stand outside the factory doors and cheer when it rolls out, right? It's the fact that the product is doing what it's supposed to do. It's the action of the product. I think it's a little bit unique for them because it's a single event, right? It's one rocket doing the landing, right? It's a bigger event, I think, in that one moment, because it's all about that one moment. But also you have to think about those people. Those people are , really, really key stakeholders. They're really bought in, they're plugged in. And I think that's rare. I think at a lot of organizations and companies, there's just really not that excitement. I know when I worked for Allied Signal, I kind of felt that way. Most people were just , they clocked in clocked out. One of the most exciting moments in my first year working there was finding out that they actually had a company store, and that you could go buy stuff that had the company logo and the shirts and everything. So I'm over there, I always wondered how people had all that stuff. Even to this day, I always say I worked for Allied Signal, and then one day they bought Honeywell and kept the name. Why do I say that? Because I'm so proud of Allied Signal that I had to say, We didn't get bought, we bought them. And then we kept the And I think that's the way we need to be about our organizations and about our mission and about what we do. I think it's very special that those key stakeholders stand around and do that. Think there's not a lot of organizations that do that. Now I think there's a lot of parallels though, I think about our community, and I think we're that. We're so excited about not the product, the product is something that kinda draws us together a little bit, but it's really not about the product, it's really about what this product does. And we're very passionate about what we do as a community. And I think that's really special and different, we should celebrate that. One key metric, there's a million ways we could prove this. But one metric we could use is how much merch our community has bought from the beginning of Rock. That number is $53,000 Wow, that is amazing. Can you imagine a church management system? I mean, if we go back to what the basics of what really wanna call it what it is, it's a church management system that where the people are so excited about what we do, that we have $53,000 of merch. I mean, I don't think there's that many F1 shirts out there that people paid for, and even the people they got for free. And I think that's just crazy, that's just one metric. I mean, that's probably the worst metric to use, but I thought it was a funny metric. And it surprised me. , I went and did the little research and I was , Woah, bigger than I thought. And again, it's not about the product, right? Just the Space X launch, Starship landing was not about the product, it was about the product in motion, the product in action, the product on mission. I think that's what we get excited about. It's not about V17 or V16, it's about what the community, what you guys do with the product. You guys are building immense systems that are helping people get plugged into ministry, so that they can reach others. You're building immense systems so people don't fall through cracks, so that they're ministered to. Systems that track when people get off track, and get them back on track, which saves marriages. I mean, we know, objectively, marriages we can point to, and a thousand more, tens of thousands more that we can't point to, that did happen, that we're building. And then there's a thousand small things that we build, There's small workflows that we just threw together in an hour that helps solve the niche need. I was just talking to someone before we started the podcast, it's early in the morning, I've already had one conversation with someone telling me about something they're working on for Christmas, and how it's gonna tie needs together with people who can deliver on those needs. Just, , it's an important, amazing project, but it's a small project in the scheme of things. But this product, this technology, this community allows us to do that. So part of it's product, but part of it's just the community working together to share ideas and train, the training's key. I think the thing that is different though, is on that Starship landing, it was all about a single event, as we talked about, that all happened in one moment, right? And so it's easier to celebrate that, because you can see it all together and stand all together. Imagine if all of our ministry benefits all happened on the first moment of the conference. That'd be pretty crazy, right? If we could see all of that benefit happen in one moment, it would be crazy. But we, unfortunately, in that case, we don't have that. It's very distributed. We can't see it. But I think the impact is as big, if you could put it all together into a moment, right? And here's what I know, we know God lives outside of time, so it is all. He sees it all. Even over the course of ten years at all, He can see it all in a moment. And we also know that the spiritual realm, are they in time, are they not? They see the benefits. We know that the angels celebrate when one person gives his life to Christ. So it's hard for us to not assume that they're actually pretty happy about that too. And so I think we just need to reflect on that. In some cases, when I watch the SpaceX launch, if I'm being honest, part of me gets choked up because I'm , This is so amazing. The other part of me gets a little jealous. It's , But we don't get to do this. And I think just reflecting through that, it's , Woah, yeah. But it's the same kind of thing. It just doesn't happen in the moment it's distributed. And I think we just need to reflect on that and celebrate that and celebrate each other when we have wins. And just know that there are in the spiritual realms, people celebrating just that, and isn't that more important? Which kind of reminds me of a quote I shared on Twitter this week, which I love. CS Lewis said, My prayer is that when I die, all of hell rejoices that I'm out of the fight. I think as we as a community, I hope we have that prayer. Because you're magnifying, you're amplifying the impact of your church through just your efforts. Those of you who make those workflows in an afternoon, or those of you who work tirelessly to make a huge process, trust me, I think the evil ones will be , I can't wait till they retire. Which is why they make us discouraged and why they make our lives a little bit harder, I'm sure, right? They don't come after us because we're weak, but because we're powerful and successful in having an impact. Reflect on that too, how do you increase what you're doing so that those in hell will prefer you not to be doing what you're doing? And rejoice in the time that while we can't point at that one ship hitting the chopsticks, it's happening. And it's happening in your church, it's happening through what you do and it's happening through what thousands of other people in the community are doing. And in a lot of ways, their success is your success because of your funding, your donation, your pouring into the community through Rocket Chat or recipes or a conversation you just had, or maybe a RX session that you did. Remember the content that you gave in those RX sessions lives on. People are getting benefit every day because of what you said, they watch it, they remember back and they implement. And I guess the goal I would wanna say is reflect on the impact you're having, celebrate that, but then think through in terms of 2025. And as we talked about, Falcon was a , the Falcon rockets were amazing. They are amazing. They do crazy amounts of things, but Starship is , not as a huge level up. So let's make 2025 the year that we go to Starship level, individually as a community and as a product. I know as a product, I'm feeling really, really good about that. We've got some new talent in and it takes time to get trained and understand the mission and understand the technology and understand our processes. But we're getting that right. We're starting to see that investment start to pay dividends. Know, even our branding and our design leveling up. Can see that if you're on social media. And that's just a start. So in so many ways, I feel 2025 is going to be our starship year. I think if we can make that for all of our organizations, and for each one of us, because it starts with each one of us. And now's a great time to be thinking about that, because we have two months to prepare ourselves and to get ready and to start 2025 right now. So think of that Falcon the Starship upgrade, rejoice, celebrate, and pray the prayer that hell will be encouraged when you're out of the game. That's an incredible thought, and it is so true that our individual efforts lead up to great things, but not being able to put them in one moment basket is it's so easy to lose touch with that. It's a great encouragement. Thanks, John. Yeah. Well, Nick, tell us about where we are in this product and platform. What are we what are we doing and releasing right now that's enabling that ministry activity? We have been able to move version sixteen seven to alpha. That happened at the end of last week, the time we're recording this. And 16.7 is just huge. It's really enormous. It was part of our issue Blitzkrieg where we closed tons of bugs. So there are 72 bug fixes in that There are 14 improvements, the existing features. And then there's some what we call added things. And that's nine of those. And one of those things that was added is no small thing, it's next gen check-in. So we have a blog post coming out soon. The Alpha team has access to that blog post and they're reading about how you go about the strategy and the tactical side of testing next gen check-in. I don't know how much of that you want me to get into now. Well, mean the key is it, It's kind of in 16.7. There's a beta version in 16.7. Is not ready for you to go install in all of your kiosks. Would be a foolhardy move. Yeah. And that's clearly articulated in the post. , this is a beta feature. We're releasing it, and we have a strategy that we're outlining for you to how you might go about gently testing it, and then maybe expanding those tests to your internal staff. I think we've even talked about that here at this podcast. We're just trying to make sure we set the right tone. We don't want everybody going, It's out, let's go. They install it, and then they test on their first weekend. That would be That's terrible. Mean, we've tested it, and if you have a plain Jane type of check-in, yeah, I wouldn't I still wouldn't do it, but , it's gonna be it's gonna be fun. And I've gone further than that. I've tested all all kinds of other interesting situations, but we haven't tested everyone's interesting There's a lot of edge cases to check-in, a lot. Yeah. Plus there's a lot of things that we're kinda , well, what should it do? Because even some of the things that it does in the version one, which is what we call what it has been to date. It's really? Is that the way it should do? load balancing, you would think load balancing, the topic of load balancing would be easy. Oh, it goes one and one and one, one and one and one. It's not. , because when the mom's standing there and saying, Why did you put my triplets all in separate rooms? That doesn't make any sense. They should all be in one room. Right. A simplistic load balancing strategy doesn't make sense. Yet at the same time, I'm sure there's someone in the committee who would argue that no, that's what they wanted. So we have to make sure we have a switch or Split up the twins. Have to make sure we have switch or something, and in this case we don't, but in a lot of cases, it's 99% of churches want it this way, there's also one church who passionately believes it should be the other way, and so we have to have a configuration. And that's a perfect example of how we get into the state of why check-in's so complicated, because there are situations where people just want different things. So we do that when we have to, when it makes sense. Yeah, and I think check-in is an area of Rock where we really have tried to meet as many needs as we can, and try to hide some of those, , it doesn't get overwhelming to everybody. But so test, we would appreciate it. Let us know, we'll fix it quickly. And, hopefully in 17 dot something, we'll take the beta moniker off it and say go forth. Yep. Very exciting. Proceed with caution. Good way to put it. That's the summary. All right, Nick, tell us what else we have going on. You wanted to talk about some predictable IDs. Yeah, there's a feature we added. I think that's in sixteen:six. It might be in sixteen:seven. It's hard to keep track. It's been done for a little bit. It's a feature that a church requested and it's a setting under your security settings. It's called disable or enable predictable IDs. And what that does is it changes the way rocks, what I call, we call file handlers. There's a get image file handler, a get file, file handler, and a get avatar. And those things return data an image or an avatar or a file. And you can no longer pass in just a simple ID. You can't just pass in the number one or the number ninety nine or 722. It requires now that you pass in an ID key or the GUID to that file. So essentially you can't just kind of harvest, test what file or what image can I fetch? So when you enable that feature, it's not enabled by default. When you enable that feature, of Rock's code now no longer tries to pass an ID in to those handlers. But it's possible you have code elsewhere, somewhere that is pointing to get image and you're passing in an ID. So just be aware, be on guard when you flip that switch. If you do have your own random code out there, maybe in lava or wherever, you should really start changing those today. Because you can today, you can pass a GUID in. I think an ID key is new, but you should be passing GUIDs in to those files already. You've always been able to do GUIDs for a long, long time. So it's the best practice you probably should have been, but sometimes even we would just fall back to just IDs. Now the file types themselves have security. So if thinking, Oh gosh, does that mean they can get to my scan checks? No. No. , that would have kicked in and said, Oh, you don't have rights to it. Could you harvest everybody's avatar? Yeah, you probably could. So it's stuff that's all been labeled unsecured files you could go get, but that should have been fine anyways. We're just an additional level of security. And it's at this point optional, but we do It's kind of a legacy lava. Probably should start turning it off and turning it on and seeing what breaks and fixing that. Yeah. Makes sense. So this this is significant amount of effort that has gone into everything we've talked about so far, but that's not it. We haven't been isolating all our effort toward 16.6 and 16.7, we've been simultaneously building toward V17. John, can you tell us some of the things that we're working on in that area? Yeah, so there's a lot that we're working on. The first thing is LMS, so that's taking a little bit longer than we thought. We're trying to solve a lot with LMS. We're trying to solve a simple LMS need, and we're trying to solve a very complex LMS need. When I say complex, think of a residency program where you could have multiple semesters, you could have multiple different courses that all have different classes this, the fall class, the spring class. There's a lot of different capabilities within a class, in terms of taking assessments, a quiz, or uploading a paper that needs to be graded by the facilitator, watching a video, there's just a lot to it. And we just want to make sure that it all works really well. There's also some new architecture strategies that we're putting in play. So for instance, a student within a class is really underneath it all, a group member, and the class is a group, kinda. That's the new part, the kinda part. And so we're just testing that, making sure we understand all of the nuances to that and making sure that's all good. I mean, the level of talk that we go to, the detail of the talk that we go to, would probably be surprising how much we talk about that. And we go, what if this, what if that? So there's a lot to that. So LMS is taking a lot, we have a lot of other things adaptive messaging. There's a new whole API version, API version two, which has a lot of cool ways you can search. So that is pretty much done, we just need to kind of roll it into the branch. There's a lot of stuff. Another thing that we've been doing that's kind of fun is a lot of new blocks have been changed into, or current blocks have been changed into Obsidian. And so if you're on the Alpha team, get a list of every two weeks, which blocks need even pre Alpha testing. And so they've been helping us with that. So I think this last week we had 30 blocks that were being converted, swapped or chopped in one two week period. Now a lot of that was a pent up of development that was done a while back, and now it's been all QA ed and final testing, so now it's ready to go out. So it's amazing, and that's just a two week period. Wow. And so, a lot of progress has been done on blocks, still have a lot to do. There's lot of other features, think, with 17, the other big one that people are talking about is the new Communication Wizard. And work is being done on that. That's a very, very difficult one. The level of programming that is needed for that one quite high. The level of customization, it's going be very different in terms of a lot more power to change things. In some ways, you almost don't need communication templates anymore, you can basically create the communication template right inside there, which is I think, again, something that's really going to unlock a lot of capabilities. But a lot of thoughts needed about how that's going to work. It'd be easy almost to do what some of these other tools Mailchimp. Because they're basically building, in most cases, a very static email. You can personalize a little bit , Oh, you can put Ted's name on it. But we have to figure out how to get adaptive messaging built in. These really, really deep personalized things that are very extensible in and themselves, and now we have to make that actually work inside of another extensible tool. So you have extensibility layered on extensibility. And that's been a real trick. I think we have it figured out now. Now we just need to figure out how to get it coded and everything. But that's actively being worked. There is some talk about version 17 that we might go a little early and ship 17 without the Email Wizard, Communication Wizard. Now, when we say that, what we're basically saying is we're going to ship it early. the work on the Communication Wizard is already being done. there's developers on it, I'm working with them to make sure that design wise. So that ship is sailing pretty much full steam, I would say too, because it's not you can't just add another developer to make it go faster. Adding another developer right now would actually make it go slower. So that ship is steaming at full tilt. So it's , well, do we hold off the whole thing until that ship has reached port? Or should we send out this ship first with LMS? So if we do that, not that we're going to slow down any other feature, it's just that we're going to speed up the release. So there's some thought about that, we haven't made up our mind, we've gotten some feedback from the rockstars on that, what they think, another good plug for being a Rock star, you get a little bit more of a voice. So considering that, so there's a lot of stuff with V17. And that would essentially put the Communication Wizard into a dot release of '17, if that were the Yes, it would not be pushed to '18. As soon as it's ready, as soon as that ship is ready to go, we're going to release that one too. There is one small feature in V17 that I kind of want to talk about, because I think it's going to be very strategic to what we do, even though it's a small feature. Looking forward into 18s and 19s, what we want to do is provide more analytics for churches and tell them, How are things going? Provide more deeper insight into their ministry. There's a lot of things we could do, but we don't understand certain things about their data. We sitting all the way over here, and it's a very extensible product, we don't know what that means. When you did this, what does it mean? One of the things that we really need to know, for example, one small example, it'd be very helpful for us to know your average weekend attendance, so that we can do things show your active records versus average weekend attendance. Well, how do we know your average weekend attendance? Now you'd probably say, Well, we have a metric for that. Of course you do. We just don't know which one it is. Can't just go look and harvest one that says weekend attendance and assume that's the right one. I wish we would have thought of this in the beginning, but it's impossible to think of everything. So what we're doing is we're adding this new feature called Metric Classification. And it's just a way for you to label something, we'll give you a list of maybe 10 things that we would to know. And then you just tag it to the metric that is your metric for that. We're also shipping out of the box with those metrics already pre existing and pre configured, so that new churches will automatically have it and we're fine. Now we'll probably come up with a few more we want in the future, then they'll have to go label those too. Now it's important that you label them, but it's important that you also look at the definition of what we're looking for, because your metric has to be in a certain shape. For instance, average week in attendance, I think we wanted to see that partitioned by campus. Again, now we can go and give you those insights by campus. This data does not leave your server. We're not looking to harvest this back into Spark. This is for us that we can build tools within your instance to show you analytics for yourself. While it seems a very small thing, I would highly recommend you read that part of the documentation. And then over time, we're probably gonna start nagging you , Hey, there's a classification called average week in attendance and you haven't assigned it to something, could you do that? So that we can again help you have cool features. So small thing, be thinking about that and be looking for it in the documentation. Another thing that we've been working on too is working with people in the community on indexes. So that's a common thing. It's often the case that your SQL Server will recommend indexes for you. Now realize when it tells you that SQL Server is a liar. Not in an evil sense, just in an ignorant I don't I'm sensing evil. I feel the darkness in this one. It's just trying to do its best. And so here's what I'd say, not all of its suggestions are good suggestions. And not all of its suggestions, it will even use. It's often the case in my experience, I've actually implemented those indexes and then it doesn't use them. It's just trying to help a little bit. Now it's not always wrong, it's not always evil. So sometimes that's right. So here's our recommendation, this is a best practice. Don't implement those indexes. If you see them, look at them, consider them, consider what maybe the system is trying to do. And if it makes sense, if you think, Hey, I think this could be helpful, send it to us. We would love to look at well considered ones, and we can't look at thousands of them, and make the product better. Because are there indexes that could help improve Rock? Absolutely, we're not perfect. And the way you use Rock is different than the church next door. And those small differences in how you use it can make big differences about how the database goes and retrieves data. So we had a really great conversation and interaction with the church recently about this. They recognized that their instance and some of their resources had found, Hey, we really think these indexes would be helpful. And so we worked together and we reviewed them. Now they had done a lot of hard work. They did not just go get those recommendations and just send them to us. They did a lot of hard work, rigorous work. Yeah, what they sent us, I think they sent us six of them, but they were only proposing five. And we did all five, and they were great. Now some of them helped in cases that was really helping a plugin. So it was a plugin that was relying on some foreign key stuff, but it was a very commonly used plugin, and if you weren't using that one plugin that they were, it's very common that it was around financial transactions. And so, yeah, we could see a lot of plugins would do that. So that's not really a core thing, but it made a lot of sense, and so we put it in. Now, here's why this was a good thing, is that they came to us, they said, These are the recommendations, what do you think? Said, Yes, we put them into the core product and they get them that way. If they had just put those in themselves, perhaps we would have made the same index or an index that did something similar, that we would actually have slowed down their system. Because every index comes with a cost, and sometimes a steep cost. So you do not want to be going willy nilly putting indexes in, we wanna keep them very well managed and concise. And so work with us. We're not defensive about it. Sometimes we might say, Yeah, that one we don't really feel, we don't understand why that would make actually anything different. We've also done this across many different instances. So we have some stuff we're trying to work on right now. And also to realize the observability is gonna help us get more data over time. But I would say if you care about those indexes, work with us. And then not only will you solve it for you and not damage yourself in the future, but you're also doing the community a service too. So that church who came to us with those five, six, guess what? Every single church is going to benefit from their rigor and from their hard work. And that's just way it should be with the Rock community. That's the Rock way. That is. Yeah. So do not though, put in your own indexes. Work with us. And there's even some strategies we can work with you for communicating back and forth where you could possibly do it Temporarily. Yeah, and then we will, you need to undo it when, but we have a communication process that we can help you with We'll tell you what So that's the best practice that we'd really people implement. If you've already done that, you should probably go back and inquiry and figure out which ones you've done and start that process. Good. All right, it is time for some community updates and we have quite a bit going on. We announced at the conference this year that we were finally rolling out a new lava class. We've been really excited. Boy, if what goes into creating a new class, a training class, it's a it's incredible amount of work. And we're so happy to be able to roll this out. I can tell you there's been a lot of work on the content itself, of course, and the way you present it, even the schedule and how you do it, how many days it takes, what that looks for it, , a diversified multi time zone kind of schedule that allows people to not have to take it in the middle of the night and be able to eat lunch. The exercises and the servers required, there's just so much involved in all of that, and not to mention the processes behind it. So it has taken us a while to get here, but we're here. The first class is coming up here in a couple of weeks and it's completely sold out. So there was a great response from that when we announced it at the conference. The next session is open and does still have plenty of availability. So if you haven't signed up for it yet, it's in first quarter, I think in the January next year. Highly recommend that jumping on it soon because I think as soon as people clear the planning and budgeting and the things they're doing right now, they're going to be jumping on that. So grab those seeds. We saw them go quickly this last time around. We also have a fun new chip lava sauce that has hit the promo store. So if you're wondering what temperature Chip likes his food, you can soon find out. There is some hot lava sauce in the store. Between that and other merchandise, don't forget to to consider that for your staff gifts this year. Mhmm. White elephant maybe? Perhaps it could be a white Family Christmas stocking gifts. We have some chip plushes that are a big seller for the kids this time of year. We also have been working on our branding a little bit and polishing some things up. So you'll find some new Rock logo stickers. So check those out. They're very nice. We're we're really excited about that. But don't forget the promo shop this time of year. And we have one more announcement that we're pretty excited about. Oh, is that the new office? That's it. Finally. I know. Yeah. So all the projects we've been working on, another big project has been the move. And I cannot describe how much effort that's been. Did not expect I thought that was gonna be a big deal, but I didn't think it was gonna take this much work. So yeah, we're moving next Friday. That's it. Tomorrow, at the recording of this. So that's a big deal, and we're super excited. Here's the biggest thing we have to say, this is a blessing from God. Every time I'm over there, as much as I'm frustrated with a half a million things, it's , God, why did you give us this? We don't deserve this. The owner has done amazing things for us. He's been a great owner. And we just really feel We see God working through that. And this level of innovation that we're going to be able to do in that new space is pretty crazy. And we're not building this for us. We're building this really, I mean, it sounds weird, but we're building it for the community. We're trying to build a space where technologists who care about kingdom mind and things can come together, work, whether it's daily or once a year. We want to have space where we can have host people. There's even other nonprofits in the valley that we want to have them come use our training spaces and other things. So this is not something for us, it's an investment that we're putting in for the entire church to have an innovation space to work on technology that impacts Kingdom Mind and things. And we really see it that way. I think it's going to improve what our team can do, it's going to give us an environment that just Sometimes your environment can't help but impact your mood, your thinking. It's also a bit of a recruitment tool, a little bit. So that helps. Sometimes people are very kind when they come to our current office, this is really nice. And I'm , I don't say anything, I'm just , in my head, I'm , You're very kind. We've done the best with what we've had. And God's provided here. That's were just over the moon, ? True. When we think of where we came from. But we really just feel in so many ways, God's opened doors for this. I mean, literally, there's times that we're , Okay, this isn't gonna go through, this deal is not gonna go through. It was the other owners , No, of course, it's still gonna go through. I don't care about that. , I'll make it work. So we're really excited. So be praying for that. We'll be doing, if you're local, we'll be doing an open house at some point. And then we'll be doing little walkthrough, maybe a video just to kind of show and have you guys help see what's available if you wanna come use it, or just see what your funding has helped. Yeah. We're very excited about this. And as John, as you've mentioned, it's very obviously a gift from God. And I don't get choked up about a lot of things, but walking into that office, I consistently get choked up and thinking , I don't know that we would have seen or projected this. And God's cleared a lot of mountains for this to be the case. We're just very grateful. Yeah. Over time, I'll just put a little short plug for this, over time that building will be powered by Rock. So in our hobby, free time, nighttime, weekends, we're putting a lot of automation in. Yep. It will be all Rock powered at some point. Very exciting. Wow. We have crammed so many updates into one short podcast episode. Thanks so much for tuning in. You don't want to miss this kind of content. So make sure you subscribe wherever you get your podcasts. So you aren't late to the next post when it comes. Thanks so much for your support as a community. We appreciate you, value your insights, and are always open to your ideas for future podcast episodes. So please reach out and let us know. Thanks for joining us. Do a church that loves the idea of using Rock but hasn't taken that leap yet? With managed hosting, churches of any size can get access to Rock's amazing technology, hassle free. With just one click, Rock's managed hosting removes the roadblocks that might stop a church from switching to Rock by making the process simple. Churches get the ease of a SaaS church management system without losing any of Rock's powerful features. Are you ready to take the next step or share with another local church? Visit rockrms.com/hosting today.