A New Adventure

For the last 13 years I’ve had the opportunity to work for an amazing church, Christ’s Church of the Valley (CCV). Over those years I’ve worked with talented people on some incredible projects. Many of those projects involved developing applications with David Turner.

As of today our most recent development project, the Rock Relationship Management System, is taking us on a new journey. We are stepping out of our roles on staff to become independent consultants in a new venture called Mine Cart Studio. Our first project will be the continued rollout of Rock at CCV through October. After that time we will expand our focus to consult with other churches that require implementation services and custom development.

You can read more about out next steps on the Spark blog. In the meantime, both David and I would highly value your prayers as we make this transition. If there is anything we can do to help you please drop us a line.

RockRMS 1.0 Released


Wow, it’s been a while since my last post! We’ve been incredibly busy working on Rock. Literally… not sure when was the last time my eye’s weren’t stinging… but… as of two weeks ago we released Rock 1.0!!! Below are a couple of links to help you understand what Rock is…

You might be asking what’s next… Trust us we’re only getting started. There’s still a ton to do. Check our road map for the details of the start of what’s next (there’s so much more that hasn’t been added to the roadmap yet). Be sure to follow the Rock blog to keep up with what’s new…

Covet Your Milliseconds

What is a nanosecond? Or more importantly, why does it matter? Developers spend milliseconds (1000000 nanoseconds) like the government spends money. The cost is slooow software. Speed is a primary feature of the Rock ChMS, we covet each millisecond. This video helps put it all into perspective. Note: Keep in mind when she compares a nanosecond to a microsecond a millisecond is 1000 microseconds.

An example of our dedication to speed is Rock’s differed transaction capability. In any web application there is work that needs to be done, but doesn’t require the user to hang around to wait. We built a transaction queue that can take these transactions and process them after the page has been sent to the user. A quick example… we’re building in basic page analytics into the CMS portion of the app. A way to track how many times a page has been loaded. If we were to write this into the database during the normal lifecycle of a page we could expect it to take 12ms. Adding it to the differed transaction queue only takes .15ms (you will be able to turn off analytics all together if you’d like).