Skip to main content

Being Inventive for the Right Reason

As I continue going through Hebrews, I came across this line.

"Let's see how inventive we can be in encouraging love and helping out" Hebrews 10.22-25 (The Message)

What struck me is that he didn't say, "Let's see how inventive we can be to convert people" or even "Let's see how inventive we can be to get the word of Jesus out." There's more of a missional focus where we need to encourage others to love one another, and we need to help out, in unique and inventive ways.

Through being inventive and doing things differently from everyone else, with no agenda besides expressing our love for others, people will talk. We can spread His word through our actions. If the church is having a hard time brining in new people, I think it's a good sign that we aren't focusing on the right thing. We may have the best Worship service in the world, or even the best children's program. But unless we are spending out days out in the community, working with people directly, we'll never reach those who need Christ most.

Seriously, those who need Christ aren't going to search through the newspaper to find our church. They won't even know why they should pick ours over someone else's. If we do advertise in the paper, it needs to focus on the hurting person who isn't a Christian, not on informing other Christians that we are "Episcopalian" and our service times. Why should we want to attract other Christians? There are tons of other churches for that.

This is part of why I like some of the billboards people have been talking about. From the "Satan Hates Life" ads to "Church Doesn't Suck" (there was another one, but I can't seem to find it).

If every member of our church was chartered to spend one day a week helping the poor, the hurting and the lost, we'd be able to build relationships and tell them about the change Christ has made in our lives. We can then talk to them about church and Christ. We can then guide them into helping others, sharing unconditional love with them and get them to help out too.




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