Podcast Episode 116: Episode 89: Life After COVID-19

Description

Join Jon, Emily and Nick as they walk through some upcoming features coming your way and the impact of these new features for life after Coronavirus.

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, the podcast where we take you behind the scenes with Spark Development Network as we're growing and building Rock RMS. I'm Emily Forman and today we have Jon Edmiston and Nick Airdo and we will be discussing what's new right now with Rock and in the current interesting work situations that we're all in right now. Welcome. Nick, can you kick us off with an update on where we are in our Rock versions? Sure, absolutely. We are getting close to move version 10.3 to Alpha testing. There's just a few more things that we're trying to sneak in to that release. We've also added the connection campaign feature into ten three Core so everyone will get it. And then there's 65 plus issues that have been addressed in 10.3 And so we're really it's probably gonna be next week at some point that it will go to alpha. And then see how long that takes, alpha beta, couple weeks, and then should be in everybody's hands pretty soon here. Great, there's a lot of interest in that for sure. Now we've been talking a lot about what's coming with V11, but there's been a little bit of a typical Rock world movement in that area, so fill us in on that. Well, could talk about that a little bit. I'm gonna pass the baton to John at some point though. So yeah, V11, you mean in terms of what we thought we were gonna do in V11? Right. When's it coming? What's included? Right. So because of of the circumstances that in the situation we're all dealing with, we're really trying to put some bigger features into the next release of Rock but we can't do that in 10/2003. There's certain technology limitations we have. So in order to make what we call model changes, we have to issue a major release. So every there are a number of things that we thought we were gonna have in v11 that we're gonna push out a little bit in order to get some new I don't know if I'm supposed to say anything about what the features are. John, am I allowed to mention anything? Yeah. Don't think there are any secrets. Okay. Well, with version 11, we're really looking to do some additional check-in options And I'm gonna really turn that over to to John to talk about those sorts of features. Yeah. So we do have a lot of features coming around check-in and Nick exactly was 100% on, they are going to require some model changes to do well. In a sense, it's a little bit frustrating because we had these visions of where we really wanted to go with check-in, kind of a check-in two point zero strategy that we've been working on for probably about a year in terms of ideating over how should that look. And think the frustrating part is now it's hurry up and implement that. And I to have things in the crock pot. I don't think true innovation just comes naturally in a blink of an eye for big, huge features. I think when that happens, you usually get it rolled out and then realize, Oh, there's a few better ways to do that. So we're kind of being forced to go a little bit faster. We are going have to do it in a gradual state. So we can't give everything that we've dreamt up over the last year in a matter of a few weeks. But we do want to give some of the preliminary things. A little bit of that is going be dependent on how much funding we have and how much time we have. Obviously, with more time, we can use more of the core funding to pay for things that. But if we need immediate drastic shift in priorities, sometimes that has to come with funding. So I know, Emily, you've been working with a lot of churches talking through that and that's going well. But irregardless, there's a lot of changes to our roadmap because of COVID-nineteen that are going to require model changes. We hate to do that, but at the same time, it seems kind of silly to be sitting back worrying about a feature e signatures when the whole world is trying to figure out how to redo check-in when we come back. So from a prioritization perspective, the priorities have drastically shifted and we just need to respond to that. It would be silly not to. That said, a lot the features that we said were gonna be in the V11 that will probably be pushed, next time, to V12, there's a lot of work in that that it's already done. For instance, we've been working as a team to redesign the person profile page. Those mock ups, high fidelity, we actually even have them started in mark up, are done. And that page is awesome. I can't wait to show that to people. It's really amazing. It's not a quick spit polish. It is a complete redesign, refactor, and it is really awesome. And people, I think, are really going to it. That's obviously going to have to be We don't have time in the next few weeks to implement that the correct way. So there's a lot of of cool features in that have already been started but won't be able to make it into into v 11. So And then there are features that are basically done that will you'll get those sooner document types and documents for people. Yep. There's new storage providers for the asset manager system. If really want to see what's going be in V11, just go out to the pre alpha site. Yeah, there's a lot of little things in there too that weren't technically on the roadmap at the time, but as we see things, as we work with clients, we've added features especially around data views. You can start to see how they're being used, which ones are slow. I'd call those almost little micro features, but it's actually they're really helpful. There's a ton of those already in Pre Alpha, which will be in V11. So I'm really excited about that because some of the times we work on these features and it's , oh gosh, no one's gonna be able to see this for another six months. Even some of them have been talked about in the architecture videos, about page timings being really nicely formatted at the bottom of the page. That's in, of course, V11 and it's super helpful. I'm using that all the time. So there's a lot of good stuff in V11. That's great. And I that we're able to pivot so quickly to address some of the needs that we're seeing coming from the community. This isn't the first thing that we've done that on. So we've been trying to work with churches as they've been going through the process of what do we do with this COVID-nineteen situation, which goes back a couple of months now even and we've been working on a lot of things, we've pushed out quite a bit of content that's helpful, we've pulled together a live panel that we did pretty early on and John, we're still in the middle of working and rolling out some additional options. We've been talking you mentioned with the churches about contactless check-in. I've had some great conversations, there's a lot of interest out there. So if you happen to be listening to this, I know this is gonna publish pretty soon. If you listen quickly after publishing and you're interested in knowing more about that, funding it and helping move it forward, let us know. But we've been working on other projects as well. Can you fill us in on a couple of the other options that we've done as future responses to COVID? Yeah, so of course the big one that we've been working on in the beginning of COVID situation was the connection campaigns. Of course, we got that done pretty quick, but Nick and team have been adding a few more features to that, doing some bug fixes for that. So that work has continued and hasn't stopped. And that's just a great feature. I've heard so many people say, We're going to keep doing this even after the world's back to normal. And that will happen. Eventually, we'll get all back to normal. But it's great to hear that, that through this terrible situation, that we've learned new things that are going to help connect people long term. So, continue to work on that, obviously. We've come up with a quick ticketing system for churches who may need to limit the size of their services. It's a small engagement with Sparkability Group where we can get that installed for you. I would label this as a very simple yet effective solution. Sometimes in these situations, we don't need to go in, create models, and make amazing, huge features for something simple. Sometimes we just need to have something quick easy, and that's how I label this. It's a simple approach to getting exactly what you need. That's an option if you guys have a ticketing thing. If you go out to our coronavirus page on the Rock site, you can see all this and you can see how to get in contact with that. Obviously, a digital strategy, as we've talked several times in the past, is the most important thing you can have right now. And we're trying to find more and more ways we can add to that digital strategy. And so TV apps is one of those. So we have a quick solution to be able to provide Roku and Fire TV apps for your organization. Getting your services online is one thing, but now the next step is to make it easy and friction free for your audience to actually watch those. And I know my family and I appreciate watching it on the TV versus a laptop. And so having these TV apps is is really important. Now, to date, we have Roku and Fire TV, but we've actually been doing R and D and prototyping on Apple TV also. I think from a platform, I'm not trying to get into platform wars, but just my assessment of that is the Apple TV has amazing capabilities, a very rich interface. Roku and Fire TV are very cheap interfaces. And obviously they work, but the Apple interface has so much more possibilities, but that takes more time too. But we are researching that and that's something that we definitely want to move into in the future. But for today, we can do Roku and Apple TV apps for you if that's something you need. The next feature which is really exciting is Church Online Platform Check-in. So Church Online, especially in the v4, but although it should work in v3 too, has the ability to pop up and insert moments into the feed. Moments is a v4 feature, but v3 has somewhat similar capabilities. And so in that pop up, we're providing a block that will be on your Rock server that'll allow the person to say, Hey, who are they? And who else is watching with them? So it really kind of helps you take digital attendance on that platform. And so Nick and team have been working very hard on getting this out, getting it polished up and ready. And that will be in v3. So this is one of the features that's pushing a little bit harder to get v3 out. But it's a really cool feature, and I think it can be used way beyond just Church Online platform. But that's one that we're doing the final QA check on. And it's ready and it's a pretty cool feature. And as we work through that, we're finding other ideas that we can build into Rock in terms of We all know when people are logged in and how powerful that experience is, but sometimes the person's not logged in, we can pretty much infer who they are or have them tell us in a way that we wouldn't trust to go show you their giving, but it's good enough for saying, Hey, that's me who's watching this. And we're building that kind of technology into Rock, kind of a light authentication. We don't trust who you are enough to show you your giving, but we trust that it's you in terms of saying that you showed up for this event. So we're working to add that in more and more places, which is kind of exciting. And then, of course, contactless check-in, which we're still trying to figure out. That's a huge, huge one. And it kind of depends on funding. But again, Nick and I have been spending a lot of time deep, deep in the bowels of the check-in code, just seeing how else we could extend this to do more things, limit having to touch monitors. But even beyond that, how do we make it more options to do the check-in where we can take into account more physical things , could you just walk up to a room and just check-in yourself right there on your phone? So we're not going to drive to the endpoint on that in version 11, but we're certainly going to have a lot of features there to extend that if the project goes forward. I mean, that's still kind of an if. So those are the big things for COVID. Of course, there's a lot of little things, but we've definitely been busy. I can tell you that. That's right. We did not run out of things to do recently. Another thing that's interesting is we had a scheduled master class for April, which had been on the calendar for a while before COVID-nineteen hit and we had to make the choice of whether to cancel it or whether to turn it into an online master class, which is not a format that we've used before. And we kind of polled a few people in the community and determined that the online format would be great. Some people found, especially at the beginning of all of this, that they had a little more time on their hands while they were sorting out what do we do now and so we were able to pivot the masterclass and turn that one instance into an online format and we had lots of people who were able to sign up that hadn't been able to come to a masterclass before because some of the travel costs had been a little outside their budget. So that was good, it was a very full class and got rave reviews and as soon as it was complete, we heard from additional people in the community that said, Oh I wish I'd seen that that was happening, I'd really to attend an online master class. So we actually added another one to the calendar for mid June this year to try and help meet those needs as well. Now whether or not this is an ongoing format once we come out of COVID-nineteen and return to more normal, that may not be the way that we go but for right now it's an excellent opportunity to take advantage of a master class format that doesn't involve travel and that registration is open on our website right now. We had actually quite a bit of interest coming in just even yesterday with registrations and things. So I don't think we've hit our ten minuteimum limit on that yet but we have been very responsive there and we're hearing a lot of So if that's interesting to you, up soon so we know there is enough interest to hold that second class. But that's been another way that we've kind of changed some things up to try and meet current needs. , we're also getting a lot of questions about the big question, what's going on with RX twenty twenty this year? And the big answer is that's a great question. So what we have to do is we have to weigh in balance what's going on environmentally and what the state's regulations are in Arizona, which is the host location along with what are people wanting to do. And the interesting dynamic here is, while we've been kind of waiting to hear some things from the state and it's kind of paused our registration promotions obviously, we're also hearing from a lot of people in the community that they really want this event to move forward. So we're trying to move in that delicate balance and meet all the needs and all the requirements and just figure out what that will look . So all we can say right now is that we are very actively working on figuring this out and we should know more within the next couple of weeks. So we'll make sure that it's impossible to miss when we are able to announce that. So do know that we're working on it and there are just a lot of variables right now. Yeah, I'd say it's the one thing that's kind of been hitting me a lot lately is that as the community gets bigger, one of the things that we have to expect less and less is that we're all gonna be on the same page. So while some people are looking forward to being there and are excited about being there and really wanna be physical, at the same time there's a lot who don't. And it's not even with Rx, it's just with anything. Even with how a feature should work or whether we should do A or B, there's so many strong feelings in opposite directions that makes it more and more difficult to keep trucking. So I think basically what we have to have is strong opinions loosely held. So while we might have an opinion, that's great. We all deserve and should have one. We also have to be cognizant that what's best for the whole. And sometimes even when we're talking about features, our first thought should not be what's best for me and my church, but what's best for the whole community. And then making sure that that's in sync with, of course, local needs to your church. But so many times I see people only considering their own needs and not the needs of the whole thing, which is difficult. Mean, at the end of the day, we're kind of, we're all in the middle, right? , we're not probably going to use the feature in the way that we're wanting it. So when you're in the middle and you're watching both sides, , , throw opinions across, it's interesting perspective. Definitely. And it is a challenge to negotiate all of that. So we've been on our team navigating a lot of similar challenges to what churches have been doing, in addition to trying to meet the needs that are widespread and varied. We're also trying to go through the same things that churches are doing, hey, all of my staff is now working remotely. Now we were kind of set up well, about 50% of our staff was remote. So we had the right technologies, we had the right processes in place, we didn't have to figure that out last minute but there is a definite change in work patterns, I would say and even expectations when you work a % remotely and I imagine that's something that's kind of a universal experience right now and it's something that we've had to put a lot of thought consideration and changing messaging around as we try and work through this. John, you had a really interesting word picture that you shared with our staff about a week ago at a staff meeting And I think that that's just something that everybody could benefit from hearing about. Yeah, so it's not particularly specific to the COVID situation, but just in general to the type of work we do. And of course, think COVID maybe magnifies the importance of it though, is that everything that we work on right now is very difficult and technical and in a sense fragile. There's so many moving parts. Everybody in the community is working with new technologies. We're forced to scale things in ways that we typically don't have to worry about. Everything's going digital. Everything's new. And it's a little bit though we work in this egg factory. And so we have to be very careful. The things that we work with are fragile, they're delicate. And now my word picture, I guess, was, Hey guys, we work in an egg factory, but we treat it we work in a rubber ball factory. Is that we're throwing these things across the room to each other without concern that these are very fragile things and easily broken. So that we need to be having good handoffs with someone covering As you hand someone the egg, maybe someone else is , You have your other hand underneath it in case it drops. Or you don't leave the egg out on the counter, at the edge of the counter, which is if we're not careful, if we're just thinking again about what we're doing and not considering how that's going to impact other people, it can be dangerous. And we just need to make sure that we have good coverage, that we treat these things fragile, fragile things, that we communicate really well. Hey, need to give you the egg. Here's the egg. You got it. Good. Okay, let's go. Instead of throwing it across from saying, Hey, egg incoming. And then you turn away and walk. And I think remotely, and when you're in person, can do that a little bit better because that person's maybe walking by you in the hallway and you can say, Oh, by the way, here, you have to make it more intentional to say, Reach out and just over communicate. Right. I think when you're in person, you don't have to be as conscientious about the structure around that happening. And so it just kind of can happen a little bit in some of the normal work patterns and running into each other and quick hallway huddles. So you may not have ever put a lot of thought into what those handoffs are but in the remote setting, when you have complex things you're doing and teams that work together with roles that intersect and on major projects, is very challenging and one of the things we've also been talking about a little bit is how maybe we didn't have a process around what that handoff would look when you have to be extra careful with it from a remote standpoint, but we've had the vision there. So we need to dig into why are we doing the things that we're doing and yes, the structure and processes that we have currently are there to support that but if we just get into the habit of push the button in front of me, then great, you're technically fulfilling your little function of the process but it doesn't really work well unless you're also thinking, why is this going the way that it's going? Why am I doing the thing that I'm doing? Who's coming next after me in the next part of the process? And if you're not thinking about that, I think that's the danger of where you start, process is critical to what you do, but if you just get in the habit of I check my box, I check my box and not thinking about the whole overall structure, you're not really able to be flexible or to cope with changing environments and that goes beyond coronavirus situations because just in the marketplace things change, right? Our, whatever it is that we're working on today won't be the thing that we work on next year and so if we're not able to be flexible and really apply a why to our processes, over time that's just kind of a death march for an organization. And usually it's a very slow movement, but I think that quickly pivoting to an all remote situation kind of exacerbates that. You're moving faster in one direction or another. So it's really critical to think about and engage some conversation on. So not that we've run out of things to do and we've tried to focus a lot on now but we're also still talking about the future and the future with ROQ is really important. We never want to move away from being a really innovative product. We're meeting needs innovatively right now in the COVID-nineteen situation but we're also planning for how to meet needs innovatively going forward. John, can you tell us a little bit about some of the things that we're working on in R and D and some of the different stages of future projects? Yeah, sure, definitely. I mean, I just want to reiterate that we always work hard. We always have worked hard for years. I don't think we've ever worked this hard. No. We're literally at the end of the week. I cannot believe that. I feel the week has just snapped by. I feel it's Monday afternoon right now. Yeah. And we have concerns too for your health, John. Oh, well. Concerns for my health are greatly over Well, you push yourself and , I've never seen you and this organization move and it pushes hard, so. Yeah. Well, it's I think what we're called to do and what's needed. So some of the stuff that we are working on right now that I think is really interesting, first off is mobile. That's not gone anywhere. We've been continuing to push hard on mobile. But in the last probably four or five weeks, we've been pushing extra hard. I think as we look at the version one, we're getting very close to being able to do some alpha testing on version one. But we have the problem that we have in everything in Rock, which is a little bit scope creep. Oh, but we need to add this. We need to add that. And so there's this really hard tension in a one point product because you're trying to make it what you want it to be versus what it needs to be just to get the minimal viable product. And so I think we've pushed a little too far in some areas and we've gotten too many features that are beyond minimal viable and then there's some other things that we still need to get in there that, okay, that has to be in there. So I think we have that final small punch list of things. There's a couple other features that we are adding just because we want to make as many people as we can mobile app engineers as possible. And could you do this through a harder way in the shelf today? Yes. But we want to make it super easy. I keep dreaming of some of you guys, I literally think of you guys individually thinking, oh, this person's gonna love this. I wanna make that person be able to do this. Could they do it this other way? Yeah, probably, but I just think that's gonna be way too much, too hard to consider or to think about. I know your time is super valuable so it's not you have twelve hours to learn this one little thing. We can just simplify that document and make it a copy paste and now you're doing it, it just makes my day to think about you guys being able to do that. So we're adding some of those features now. And then we'll get into alpha testing and then we'll get Emily, you've worked really hard to get a lineup of initial churches that we're working with to get apps out, and those have been prioritized in order of minimal needs. So those who have the smaller needs that we can hit first, we want to do that. I know you've talked with and I've talked with some churches who want these mobile apps really badly, then they give us and our first question is, Show us your minimal viable product that you need for an app. And they hand it back, and it's every feature known to man. It's the kitchen sink. And I get that. These features are important, but that means that you're gonna have to wait longer. And literally there's no app that does that. There's no app. If you want that now, you're gonna have it custom written anyways. And you're gonna pay a fortune for that. So we're trying to work with the churches first who say, Hey, here's what I want, the kitchen sink, but here's what I'm willing to go with with version one, and it's something more in line with what we can hit. And so we got a few of those lined up in varying levels of starting. So, of course, that's been taking a lot of time and energy, but it's coming well. It's it's really neat, and it's kind of fun how you can stitch this all up, and it's it's really not that hard. So Can I just say that making something that not that hard is really hard? So the hard work is not that it isn't done, it's deferred, it's it's done upfront. So that down the line it doesn't have to be. That kind of architecture is amazing. Yeah, it's definitely, it's fun when you watch these videos on demos of how to do new technology and they're so simplistic because it's always build your first page in your app. It's , Oh, that's nice. You just get to pour concrete around this one page. It just does this. And our first page is , what's got to be extensible? You got to be able to drop anything you want. So it's so simplistic, some of these apps that people write, because it's hard coded to do just that. page one does this. Our page one is , okay, what virtual page is that in Rock and what does that content have? What's the security on that? , what's the personalization for that? It's much, much different. This extensibility, everything is kind of a, so extensible is very, very hard. I think when people see how easy it is to do what they can do, they will hopefully get an idea of how complicated it was behind the scenes to make all that happen. Right. Hopefully. And then, , when you do that, Nick, you said, how easy it is to do this, but then a lot of it's, we've given you a loaded gun. You've got to do it correctly. You've got to make sure it's performant. And, , I've been talking about it in the architecture series, which I highly recommend you check out if you haven't, that our culture now talks about everybody's an engineer. And that's fine, but that's a lot of responsibility. You can't just call yourself an engineer without learning the right way to do it. And we're with you on that. We're partnering with you on that to make sure that we train you and give you the knowledge. But then after that, it's up to you to then take that forward and do it the right way. Another thing that we've been looking at that's an extension of that exact concept is CDNs. So, we've been working with a lot of clients over the last several months and looking and helping them tune their websites. And in doing that, it's been really fascinating to see that, A, we haven't done a great job educating people on how to configure their sites to perform well. So, a lot of the architecture videos are exactly coming out of the lessons learned. But then also there's some new technologies that we can do to help churches scale. So I would kind of explain CDNs, kind of if you're looking at a tank, you can have active or passive armor. The passive armor is, Oh gosh, my tank is going to get hit by things, in this case load, from your server, it would be that. So I better thicken up the armor. I better put more armor on so as I get hit, I'm still okay. And that's what we've been doing to date, is we've been kind of adding more armor plating to people's sites through configuration to let it scale more. But now we need to also there's technologies out there that's called more an active armor that says, Hey, don't even let the best shell to defend is the one that didn't hit you. Right? So we can put these shielding around your server to say, Hey, a lot of this traffic, your server doesn't even need to worry about. Let somebody else worry about that. It doesn't change. There's a ton of work your Rock server's doing that it simply doesn't need to do. Serving up images, serving up CSS files that change maybe once a month. Let the ActiveArmor protect you from that, and that's the CDN. Now to do this, we have to be able to give hints out to that ActiveArmor about what stuff should we not have to worry about and what stuff can it do. So we need to kind of give it hints to say, Hey, Cache, on this file, you take care of that. And so we're going in and we're adding There's a lot of that today, so it's not there's none of that today in Rock. But we're seeing other opportunities where we could say, Well, if we could just hint to the CDN that we don't need to really take care of this every request, you go ahead and take care of it for the next hour and then come back and ask me if anything's changed in an hour. I know one client we worked with had written some applications that were seeing the Rock API. And they were getting about a million hits a day on their Rock server, which is pretty good. I mean, that's a lot. But 80% of those hits were from their API from their app, which is okay. Nothing wrong with that. But a lot of those requests, actually, a vast majority of those requests were the same requests getting the same data back. So, you're kind of spending more money on infrastructure than you need to in that case. So now we're looking at that going, Okay, well, you probably should write the caching into your app. Don't keep asking for it on our side. The best cache is the cache that's closest to the need. So it probably is better to have it inside your app. But we could also build into the Rock API the ability for you to go in there and say, Hey, these requests are probably gonna be the same, so just cache them for an hour at the CDN. And so again, that's adding active shielding so that instead of being called maybe 10,000 times a day, that one API, it's only called three times a day. And the Rock server would very much appreciate that vacation. And your CPU bill Yeah. Will appreciate it. Yeah. And these CDNs, I mean, that's what they're built to do, that content's stored at the edge, so it's very close to your clients. So what we learned through that, what I love about that is we learned that, okay, where do we need to educate more? And so we've been working on that. There's a new caching video that's probably one of the longest architecture videos that explains a lot of the stuff about how Rock does caching, and it takes the lessons learned that we've seen from the real world and applies that. So by working with hands on with the clients, learn what we need to educate on. We learn what tools are working really well in Rock and how do we configure that to meet those needs. But we also get to see, Oh, yeah, I see that. Building the cache into your app is hard. That's probably where it should be. But what we could do is we could add some more features to kind of do the middle ground. So I think it's really good for the clients, obviously. We always said we want to work in people's trenches, and that's where we learn the most, and we love that. So I think it's a really good partnership and being able to work with some of the other clients and we really appreciate it. John, you've mentioned the architecture video series that we've been putting out a couple of times and if people haven't run across that, I just want to point out that they can find that on our Rock You page. In those videos, there are quite a few out to date and there are probably more that will be coming and that's a great place to start to make sure that your foundation is set up well. You can build whatever custom house you want but if your foundation's a little bit off, it is not going to be a good plan. So the architecture series is definitely one that's been, it's valuable anytime, but as many people's performance took a bit of a hit when they went online, I think people are starting to realize just how critical it is to make sure they get those pieces right. So just wanna let people know they can head to the Rock You page from the community site and find those videos there. Yeah. And we, I said, we have many more. I have a list I keep open all the time where I'm adding little thoughts as I work with others. That's a tip I'd have, I'd give to everybody is always have a little notepad or some little app open where you're keeping notes. Because we all, every day, we're all learning and getting all these tips, and they just kind of filter out the back. The way I I kind I always work in word picture, sorry, is I used to watch this show called Gold Rush, and it's about these guys who knew nothing about how to mine gold, but they go out into the Alaskan frontier and mine gold. One of the things that would always happen is they wouldn't set up their little sluice box, which is where the water runs through. And the water has to run at the right angle at the right speed so that the gold can settle into the little riffles the miner's moss so they can be caught. Right? If you don't have it right, the gold floods out the back of the sluice box and just goes out down the river again. And it's so important that we catch these gold nuggets. And every day, all of you, whether it or not, are being inundated with gold nuggets. If you just let them go out the back, you didn't learn them. So it's all about capturing them. And you may not have time to filter or do what you need to do with it right now, but just get it on a little text list and capture it for the for the future. That's what all the stuff that we talk about in the architecture videos are just little teeny nuggets that we're just collecting, and and then we melt them down and make, , jewelry out of it that everybody can have. But you all have the same thing. It's it's not that we're unique or different. Capture those nuggets and share them with others on your staff and the community, family, whatever. Oh, that's a great tip and actually a really good word picture. No need to apologize. We'll run with you on that one. I've got another list too that I'm working on for respectability. It's a hundred point inspection. So , you have a, if you own a car, you take your car in, right? To get it inspected every so often, or you probably should. So as we find little things that, , we see maybe done incorrectly or things that could be of concern, I've been writing them down so that we can do that. That's upcoming service from Sparkability. We'll be able to do a hundred point inspection on your Rock instance, once a year or whatever you you you feel you feel is deemed appropriate. And and some of those tools we'll build into Rock just to kinda help report, , things that maybe aren't are kinda off kilter. Or bring visibility to hidden things that you should be aware of. Yep. We certainly learn every day. Mean, I've already today just show some of our dirty laundry. Right before this podcast. This podcast was the first thing of the day, right? So I come into my office, home office here, and I'm , okay, well I'll go through my email and I'm , oh crud. Every so often we get two emails from Rock at the exact same time. And so we one of the things too behind the scenes, we a lot of us on the leadership team here, we get an email every day with whose birthday it is that day in our community. And then we take that and then we write personal emails or Slacks or chats to people. Occasionally, we get two of those at the same time. When that happens, we know that there's two Rock instances running. And so usually that means that one of our developers or one of us, sometimes it's us, is running a local copy of our database and we haven't run the clean script across it. When the jobs are running at 8AM, when the email goes out, our local machines are sending it out. Turns out In our defense, that hasn't happened to us in quite a while. We try to not let that happen. Yeah, yeah, right. Yeah, okay. But it has happened. In the past it has happened and I've been guilty of it too, so I mean. But now I have been guilty of it more than once. And so now I'm very, very, very cautious about it. And so I got the two emails and so then I was off trying to figure out, okay, where is this? And it turns out we had moved our site from Liquid Web to Azure. And I had turned off the at the Liquid Web site in a way, , I I put it so that the app offline was was up, so the Rock wasn't running. Well, in our deployment process this week, someone hit deploy and it deployed to the old server, which took the app line off and Then we had two Rack servers running. Yep. So, I mean, we do the same stuff. So as we talk about people who do things not the right way, we're still learning. we're all in the same boat. there's no judgment. But the best thing we can do is help each other with the lessons learned. So I did turn off the service now. It's never coming back. And after lunch, it will be deleted, that old VM, which I can't I've been looking so forward to deleting that for years because Liquid Web has been gouging us the last Expensive. Yeah, last few months. They just raised their prices. And we started with them, gosh, in 2011. So back then it was great, cheap, reliable, but now I'm so looking forward to hitting that delete button. Thanks for sharing the end of the story. I was waiting anxiously for that. For what? The delete or the Yeah. That you got it all handled. It's good. Well, it's one of those things. As you go through your day, that's not what I expected. It was a little bit frustrating because I'm , have all these emails I need to go through and add some stuff that I had sent to myself last night to sort out and get into my file system and that hasn't happened. Yes. So for good reason, it hasn't happened because we have not yet run out of things to do here at Spark, which I think this podcast probably supports. But we know that a lot of churches are working through the same things. We're excited to see what happens as churches kind of open up and start going back and we appreciate working with them through their lessons learned because we can learn from that too. So as you're learning things, if there's anything that's valuable to the community or would be valuable to us, let us hear about it too. Well, for joining us today for Rockcast. We are so grateful for this community and we've seen, I mean, we know how great this community is, but it's always fun to see it shine. And in the middle of COVID-nineteen, I think we've seen the community come to light, really working together on a lot of things and solving problems in great ways. It's just a real pleasure to be a part of it. Thanks for tuning in today and we'll catch you next time. Do a church that loves the sure we're to we're going blocks 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.