Sunday, May 30, 2010

Considerations...

I've decided to go to Haiti.  Tickets are purchased, along with the in country fees (tuition), insurances, and many items from the list of take alongs.  Hoping to visit the Travel Clinic on Tuesday.  Need to be packed and ready to go by Wed evening.


Although it has been several months now since the quake, the infrastructure to support the assistance provided by those coming in to help is not really in place yet.  We'll believe we'll be working on some piece of that while we are there.


We think we'll be helping to finish space on the 2nd floor of the HQ building, construct part of a bunkhouse, or perhaps work on an orphanage.  Or - maybe something else entirely.  We've been coached to remain flexible once we get there...

We leave early this Friday morning.  We're trying to take along some of the things they need there to leave behind.  Here's a page that lists some of those kinds of things - some are mundane - some are pretty specific.

http://www.efca.org/reachglobal/reachglobal-ministries/efca-touchglobal/efca-touchglobal-crisis-response/urgent-needs/-18

The infrastructure problem means it's difficult to get the things they need just to keep things moving and improving.  Scroll down the page a bit to see the extensive list of specific needs they have.

- Peace, Todd

Sunday, May 23, 2010

Haiti...

I'm considering going on a missions trip to Haiti for a week to help with some building.  In two weeks.  Considering.

But - passport is in order - and Laura is supportive.  So I'm going to continue looking into it and thinking about it...

Stay tuned to see if this goes forward - or just turns out to be a good idea that doesn't pan out.

Would love to hear your thoughts.  Plusses and minuses of going forward with something like this?

- Peace, Todd

Wednesday, November 21, 2007

Sweet 'Taters v Yams: What's the Story Morning Glory?

So this is the time of year when traditional holiday food items make their way to the collective front of the national culinary lobe. And - if you are like most people - when the category of sweet potatoes finds its way into conversation for any length of time, there follows a general sense of confusion about what is a yam, what is a sweet potato, whether they are related, and where to get them in the event that you prefer one over the other...

It turns out that - in the United States - actual yams are not that common. Instead, what you ARE likely to see in the produce section of your local grocery store are two varieties of sweet potato - a white or pale yellow variety labeled correctly as sweet potatoes and a second orange, sweeter variety confusingly labeled as yams for obscure historical reasons.

Sweet potatoes, as it happens, are a variety of Morning Glory. Actual yams are the bulb or tuber of a vine that grows natively in more tropical climates such as South America and Africa, and can grow to be quite large (several feet in length and over 100 pounds).

Here's a more scholarly breakdown of the differences, in case you are interested:

http://www.ces.ncsu.edu/depts/hort/hil/hil-23-a.html

Monday, October 01, 2007

Lore of Yore - Switchboards and Stacker Teams

Spent the past week in Chicago working, and then, for a variety of reasons, stayed for part (most) of the weekend before returning home Sunday afternoon/evening.

Before driving back to Ames from Des Moines, though, I stopped to see Mom and Dad and Grandma out at Grandma's place in Pleasant Hill. While there, we had several interesting discussions hearkening back to days of yore...

(insert time travel music and don special effects glasses that make your vision go all wavy and fade from color to black and white)

We were talking about computers (well - Dad and I were) and we kept saying the word Software - and so Grandma asked what that was. I tried explaining that anything you run on your computer - like the programs that we use to show her pictures or videos - is software. "So it isn't really soft then?" To explain why it's called software, it seemed like a good idea to explain what hardware is. And then that software is this flexible, relatively easy to change thing that allows us to get a computer to behave in different ways without swapping out its physical parts or redesigning the way it's put together (like they did in the way olden days - back in the 50's) .

But alas - it just didn't seem like I was getting through. Then I remembered that Grandma used to work as a switchboard operator for the phone company back in Onaga before she got married to Grandpa Falk - back in the days when you had to plug wires into sockets to connect one person with another person. I told her that the switchboard was a kind of hardware that she would "re-assemble" to get it to behave differently (by changing which person's phone line was connected with which other person's phone line). And that today, all that is handled by software (although I'm not entirely certain all switching equipment is solid state as opposed to having something mechanical going on inside, even if it is actually automated).

Grandma looked like she might possibly have made a little headway with that (and maybe she really did) and then she started talking about how she used to earn $30 per month working for the phone company (which I'd heard before - some of you may have too), and - get this - how they used to listen in on people's calls when they were bored (they actually had to check the line periodically to see if it was still in use). Most of the time they'd check and people would still be on the line talking about very uninteresting things. Occasionally they'd be a bit more interesting - talking about money or some guy had called some girl or woman he wasn't supposed to be talking to (cause he had a wife or girlfriend already). I guess it could get a little dull hanging out at the phone company some nights when Grandma was working, and so listening just a little longer when the conversation on the line wasn't completely boring livened things up or perhaps just made the time pass a little faster. They were definitely not supposed to do it, though, and would have been fired if the wrong person found out.

The $30 per month reminded Dad that he and his brother used to make $1 a day driving a stacker team for their uncles. That was how they earned enough money to buy their first bike - for a staggering sum of $40 at that time. This would have been when Dad was about 10 or so. He and Leon (but not Leroy - too young) were so excited when the bike came that they didn't wait for Grandpa to help them put it together - they just did it themselves. And in their excitement, they didn't get all the fasteners on tightly (and maybe even had a few parts left over?). So when they were trying to ride the bike, it was pretty wobbly with the tires flopping and rubbing against the forks and fenders.

They used to take the bike and ride it out to Hwy 16 - all the way around the square mile for a total of four miles - on the sand roads they had at the time. Sand roads, as you might imagine, were challenging to ride a bike on. Plus, they had these big sand ridges along the sides from being graded frequently to even out the traffic induced ruts and ridges in the road. Ridges too big to just ride your bike over to get out of the way when cars came down the road. At least, not without wiping out most of the time. So they would have to stop the bike and pull it off the road when a car or truck came by.

When Dad was 15 or so (Sophomore in High School), they put plumbing in at home there in Duluth. He and Leon were busy digging the pit for a septic tank. This was the same time Hwy 16 was turned into an oiled road. They were pretty excited about riding the bike on a nice smooth oiled road after years of riding on sand roads. In fact, they were so excited about it that when sister Laurel took off on the bike (presumably while they were digging the hole for the septic tank) and got to be the first one to ride it on the oiled road, it made the boys pretty mad!

Going back to the the bit about driving stacker teams - it turns out Grandma used to drive a stacker team for Grandpa and Great Uncle Oscar, too. We had a discussion about "traces" and "trees" and other components of the hardware used to attach the horses to the wagons. The traces hung down pretty close to the ground and sometimes the horses would step outside their traces or get them tangled between their legs and Grandpa or Oscar would have to come deal with that because the horses scared Grandma.

Dad talked about how at the end of the day, the horses, knowing it was time to go home, and very ready to get there, could be a little hard to control once they were free of the thing they'd been hauling around all day. Especially hard to control for a young dad and his even younger brother, attempting to keep the horses from dragging them across fields made slick by the prairie hay leavings that didn't make it into the piles they'd been there "stacking" all day....

(You can turn off that goofy music and remove those cool effects glasses now if you want. Actually - you don't look half bad in the glasses. Very chic.)

It was starting to get late for Mom and Dad and Grandma - and Mom and Dad were about to leave, and I hadn't been home in almost a week. So it seemed like a good time to wrap up the visit and the time traveling discussions and I headed back to Ames...

- Peace, Todd

Wednesday, August 08, 2007

I, Geo-Cacher

I finally did it. This morning I figured out where the cache near home is stashed (End of the Road Reincarnated). I had some guidance from an experienced geo-cacher (Kevin Lodge - I guess he'd be my cousin-in-law?) and that definitely helped me zero in on the more likely spots.

So while trekking through the little wooded area on the way to HyVee this morning, armed with the advice of an experienced cacher, I found the cache I've been looking for since January. Ok - honestly, I haven't been searching high and low every day since then. I've only made a concerted effort to find it maybe 5 times since then. But still, it felt good to finally figure it out.

Then, later this afternoon, I went and found another one in the Ann Munn Woods about 4 tenths of a mile from home (Chipmunk Hideaway). This one was not as challenging to locate and, unlike the other one, it's big enough to contain lots of little goodies deposited by past visitors who've stopped and swapped their swag for swag in the cache.

You might notice a little image on the right side of this page now. It indicates my progress as measured by number of caches I've found and number I've placed. Hopefully those numbers will begin go climb steadily and continue to do so on a regular basis.

Sunday, August 05, 2007

Almost Geo-caching...

I've been talking (and talking and talking) about geo-caching for a long time now - at least since last fall when I got a Garmin GPS as a service award from my company (15 years). I've even occasionally hailed it as the key to my new fitness and hiking program. It's a good idea, I say, because it mixes exercising with technology - and there's a mapping and tracking component that I can leverage to show where I've been (or see where I'm going) on google maps or within google earth, all of which appeal to the part of me that wants to sit in front of the computer all day and never go anywhere. Well, finally, today I went and did enough walking around to feel as though I can legitimately say I've given it an honest attempt.

There are maybe a half dozen or so geo-caches within walking distance of my house, mostly concealed within or near the edge of nearby wooded areas. In fact, there is one very close to my house - within 1/10th of a mile - that I tried to find this winter. I don't really count that as getting started because 1) I haven't found it yet and 2) it's so close it would be like having someone hide one in your backyard. My take on geo-caching is that you can't legitimately say you've been geo-caching until two things happen: 1) you need to do some hiking to get to the cache hiding area, and 2) you need to actually find the cache once you get there. By those standards, I have not yet "geo-cached". Not to my way of thinking anyways. But at least I can say I've done the hiking part now with the express purpose of finding a cache. So I'm about halfway there...

Today I tried the one near my house again, and I also tried one about 4/10ths of a mile from my house in the Ann Munn Woods/Emma McCarthy Lee Park Woods (you have to walk farther than .4 miles to get there though). Didn't find either one of them. Yet. The one near my house is a micro cache (not entirely sure what that means yet - but they tell you to take your own pencil to write on the log), and the other one was a multi-stage cache, which means you find the first cache and it leads you to another, and so on and so on. This was a two stage cache, but I didn't even find the first one, so no joy there either.

I'm thinking I should try a few that aren't quite as challenging to find once you get to the location first. Just my dumb luck that the first two I tried don't quite fit that description. I probably didn't pick the best day to start looking, either. Walking through the stifling woods on a 90 degree day with ample humidity, bugs flying around, spider webs getting in my hair and on my skin, nettles poking my legs and making me itch - all that tends to interfere with my threshold of patience for looking around once I get where I think I'm supposed to be.

Anyway, it did get me out of the house walking around - maybe a mile or a mile and a half total - so all in all, I'm going to consider it a successful first outing, since I DID get the walking/hiking exercise and in reality, all the techno-geekery is just a ruse to get me out there walking around in the first place, albeit an effective ruse for a techno-geeker like myself...

Tuesday, July 24, 2007

Car Shopping 3 - Cost Decisions

(Note: This was originally part of the first post on Car Shopping - but I decided to break it out as a separate entry)

Making It Into a Cost Decision

The question I really need to answer, then, is "At what point does it make sense to put that money into a new car, instead of using it to extend the life of an older car?" The simple answer goes something like, "Well, at the point where the annual cost of the older car exceeds the annual cost of a new car." But here's the catch: How do you determine the annual cost of a new car? Is it the amount of money you lay out for the car in one year, including loan payments? What if I take out a 3 year loan or a 5 year loan? Or what if I pay cash for the car up front? How do I normalize the annual cost of owning the new car so that comparing it to the annual cost of owning the old car makes sense? It turns out that the simple answer wasn't that helpful until I did a bit more thinking about.

Of course, there are other annual costs that typically increase or decrease for a new vehicle, like insurance (goes up), fuel (goes down), washings (theoretically the same, but I bet I wash a new car more often, so increases), oil changes (same), license renewal (goes up), etc. These can all be quantified and expressed reasonably as annual costs (just go look up your most recent insurance bills and credit card statements). But how do I come up with the annual cost associated with the "value" of the car itself?

I've given this some thought, and I think it goes something like this: A more valid way to get an annual “value cost” for a car would be to take the amount you Pay for the vehicle (P), subtract the amount you get when you Sell the vehicle (S), and divide that by the number of Years you keep the vehicle (Y), or (P-S)/Y. What this tells you is how much of the vehicle's “lost value” you used up each year you owned it, where that “used up value” is the difference between what you pay for it and what you sell it for in the end. If you never sell it and just run it into the ground, then you effectively sell it for zero. But you tend to own a vehicle like that for a LONG time, and we’ll see later why owning a vehicle longer can be a good thing.

Applying that formula, here’s an example based on my ’98 Subaru Forester: it cost me around $20,000 when I bought it in February of '98. I've owned it for 9 years and a little over 5 months (let's just say 10 years to make the math easy, though). If I were to sell it on the open market right now, I might get $4,000 for it. ($20K-$4K)/10years = $1,600/year in "annual value cost" (or “depreciation”). That's pretty straightforward, and for my old car the numbers are relatively easy to come by. How do you compute this for a car you are thinking about buying when you don't know 1) how long you'll be keeping it (Y from the equation above) or 2) how much you'll sell it for if you ever do (S from the equation)?

Depreciation is NOT a 4 Letter Word

What you do is you essentially guess. But thanks to modern science, you can make a fairly educated guess. I’m using what they call a “depreciation calculator”. Depreciation, which I referred to moments ago, is the "used-up" value of the vehicle at any given time (that difference between what you paid for it some years ago and what you could sell it for at some later time. Today, for instance.). It turns out that this idea of "used-up" value comes up quite often in the world of finance, and they forecast depreciation for lots of things all the time (not just cars). But since we are talking about cars specifically, I looked for and found this handy calculator online, which for purposes of the comparison I'm making, seems as valid as any OTHER way of guessing at a car’s future value. (In reality, this is a somewhat better than average guess, since it's based on the way that cars have lost value in the past. Given the number of cars that have already been and gone, this means the guess is based upon a pretty significant sample size, and consequently, this guess ends up being pretty darn good.)

So now we know the value of the new car we are buying (let’s call that $25,000), and we can guess how long we plan to keep the car. If you’re not sure, it’s reasonable to use the length of time you kept your LAST car (10 years in my case). We can plug both of these into the calculator to get an estimate of the depreciated value of the new car 10 years out, which turns out to be around $4,700, a loss in value or depreciation of $20,300 (I’m rounding a bit because I like the math to be as easy as possible). In other words, the calculator is guessing that a $25,000 car purchased today would sell for $4,700 in 10 years, losing $20,300 in value, or, if you divide by the 10 years, at an annual value cost of $2,030. Just to be crystal clear, lets go back and plug the numbers into that formula from above, and you’ll see that you get ($25,000-$4,700)/10Years = $20,300/10Years = $2,030/year of lost value.

Of course, there’s nothing stopping me from checking to see what would happen if I kept the car only 5 years (or any number of years). What you’ll see if you do that is that the estimate of the annualized used up value of the vehicle (or deprecation) is about $2880 for a 5 year old car. You’ll notice that’s quite a bit higher than it was at 10 years. If you calculated this for each year 1-10, and then compared those numbers (by plotting them on a graph as I have above, for example), you would notice an interesting trend: the longer you keep the car, the lower that annualized loss of value gets (the orange line on the graph). What this means is that a newer car bleeds more dollars in value per year (the red line indicates the $'s in value lost per year as computed using the calculator) than an older car, and that as the car gets older, it loses a smaller number of dollars in value each year (pretty much – in actuality, if you look closely at the red line, you'll see that year 4 loses slightly more cash value than year 3. I’m not sure why. Perhaps it’s because this is when most cars outlive their factory warranties?).

Back to Why We Are Here

While all that is riveting, all I really wanted to know was whether it’s more or less expensive for me to keep my ’98 Forester than to buy a new car. And from what we discussed earlier, there are some other annual numbers I’m going to need to make a good comparison.

So lets review. Here’s a table that captures the list of annual costs for my ’98 Forester and some fictionalized $20,000, $25,000 and $30,000 vehicles (you will probably have to click on this image or open it in a new window to make it large enough to read easily):

First, let me tell you exactly what I'm comparing. I'm comparing the annual cost of keeping my Forester for another year to the annual cost of buying and owning a new $20K, $25K or $30K vehicle that I plan on keeping for 5 years.

Note that although there is a line (line 10) for Maintenance (repairs that older cars typically need and that the owner has to pay for, but that newer cars typically don't need or that are at least covered by the warranty), I've set that line to zero for my '98 Forester. This allows me to use the Savings amounts shown on the bottom line of the chart as a guide telling me the maximum maintenance costs I could pay in the next year on my Forester before it's costing me more to keep my old car than it would to own a newer car. IE - look at cell C13. What this tells me is that if I pay more than $1577 in maintenance on the Forester this year, it will have cost me more on an annual basis than it would have cost me to own a new $20,000 vehicle I plan to keep for 5 years. Remember what happens if you keep a car longer, though. If I recomputed this chart assuming that I'd be keeping my new vehicle for 10 years, the "maintenance break point values" would be lower - making it more likely that trading in the Forester for a new vehicle would make sense financially.

That's all for this installment. Apologies if you don't enjoy math or finances and if you felt like this turned into that. But if you DO enjoy that sort of thing, well then - you're welcome!