Skip to main content

Vision Practicality

Connected I was talking to my friend Mason last night after watching Transformers (definitely worth seeing in the theater) and we somehow got to talking about my previous post about Visions of the Empty Church.  I'm not even sure he realizes it or not, but one of Mason's great gifts is the ability to take a purpose or vision and come up with practical solutions to make it a reality.

We began the conversation about how there's no way to really make money from my previous thoughts on bringing technology to churches.  He then proceeded to come up with a couple of ways to make the service succeed.  Among the ideas were:

  • Providing advice/reviews of products for free for people to implement such as Drupl, MOSS, Google docs, etc.  (I wonder is this could be done as a blog)
  • Offer organized collaboration to connect churches and let them communicate online to discuss items, possibly in forums or some other collaboration software.
  • Come in and give technical advice for a fee (this is the only thing which would make money)

It may not make a billion dollars, but I wonder if it needs to.  Personally I'm fine making nothing so long as we find some way to connect churches with each-other and with those seeking God.

Most things, once I write them down, move happily out of my head.  For some reason this thing isn't following suit.  I guess we'll see where it all goes.

Peace,
+Tom

Comments

Post a Comment

Popular posts from this blog

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 d...
6 comments
Read more

Using an Array of Objects in C++

 I've been programming for years (over 35 at this point, which is crazy  to think about). My career right now is much more Software Architecture, and much less Software Developer, but I still get some time to write out GraphQL APIs in TypeScript, Vue 3 UIs, GitLab pipelines, and just generally making "big" decisions and helping make them a reality. It's nice every now and then to come across different articles and ideas that get me to remember life in college when I was using C++. Who would have thought C++ was the "hot new thing" right now (though I suppose it's more like Rust and Go, both great languages as well). One of the things I find frustrating with most technical posts is where they focus on the "how do I build an app" and not so much on "how do I do this one slightly useful thing". I figured I'd throw one together what was front of mind, using user attributes for permissions (i.e., Attribute Based Access Control - ABAC) ...
Post a Comment
Read more

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...
8 comments
Read more