Skip to main content

Ready, Set, Go!

I just returned from a discernment retreat in Richmond, Virginia. The purpose of the retreat was for people who are thinking about going into ministry full time to understand the process of the Episcopal Church to figure out where God is really calling each of us. It was an incredibly informative weekend with a great balance between information about the process and getting able to experience some of the practices I'll be using as I go through the process.

For example, we spent Saturday morning getting a whole bunch of paper and walking through exactly what the different options are and how you go through the process to be a lay leader, deacon or a priest (the presentation included what each of those means, thank goodness). Then the afternoon was all about silence and beginning to get our minds in line with individual prayer with God to hear his calling (essentially what He wants us to do) for us. Sunday was more information about what to do over the next few months, followed up with a group discussion where we have some problem and an interesting way to find clarification and a solution. Essentially we have our problem, tell the group, and then the group can only ask questions to help me clarify what I'm thinking and what god's saying. It's pretty hard not to give advice.

All in all though, it was an amazing weekend, and I even missed huge technical problems at church, though my wife says if I'd been around they never would have happened. She's so supportive… Except she really bases it on superstition and not my own technical skill.

And now that it's over I've not got a title. I'm a seeker (unfortunately not one of those cool ones who fly around trying to catch snitches). I've officially heard the gun fire and I can work with our church community what God has planned for the rest of my life. I left that retreat with the incredibly strong sense of…





Anonymous said…
Very Cool, Good Luck!!
Did you see mcGreevy where you were at?
Cindy said…
Pretty interesting. Are you on a path now, or is it just for information and you are thinking about what to do next?

I hope you waved at us when you travelled down 95. :)

Popular posts from this blog

Advantages and Disadvantages of Using Microsoft Access

I've answered this question in some form or another far more times than I care to count.  Most often it's a question of "why do I need a fancy Web application when I can just build this myself in two days in Access.  I mean, the data's already in Excel."  So I figured I'd post out what I threw together, I know I've missed some points. Overview Microsoft Access is an ideal solution for relatively small datasets and a limited number of users. From the Microsoft Web site: “As a desktop database, Access is well suited for small, departmental applications. These applications may start as one user’s project. For example, an employee realizes that productivity can be increased if a paper-based process is automated with an Access application. Other users in the department recognize that they can take advantage of the application if additional features are added. As more features are added, more employees run the application. As time goes by, more and more Access

Beryllium Spheres

I'm sitting here at home watching The Shadow , easily one of the best movies made based on one of the best old time radio shows.  I hadn't picked up on this earlier, but the weapon used to destroy the city is none other than the same power source used to power the NSEA Protector in Galaxy Quest . I never knew Beryllium was so cool.  Now I want a sphere of my own. Anyone know of other places Beryllium Spheres are mentioned? Peace, +Tom

Red-Gate SQL Compare

Every now and then I come across a program that becomes so ingrained in my daily work that I hardly know how I'd get by without it.  I'll probably break down a couple over the next few days, but for database work, I have never found anything as good as Red Gate's SQL Compare and SQL Data Compare .  Essentially these tools let you compare two SQL Server databases (all objects, users, permissions, functions, diagrams, anything) and update changes to whichever database you want.  This is amazingly useful for deploying database changes to a test or production environment (do it to production with ridiculous care, even though it will generate a SQL Script for you and run all updates in one transaction), and making sure everything is synchronized. For releases we can just generate the compare script, confirm that the changes match the updates we want to go out, and store it all in one place with the release details.  This is true for both the structure and the data, to