The system worked great, and like all good systems was forgotten and people just learned to trust that we just had really accurate caller id. This was a problem for some people because they were in the habit of calling into the office to do occasional prank calls. The most famous of these was on a new ministry assistant’s first day, when one of the members of the church called in pretending to be Louie Giglio and asked for Chris Tomlin’s cell phone number. (For those not steeped in Christian culture, Chris Tomlin used to be the worship leader at the Stone and he is fairly famous, Louie Giglio is also fairly famous and is close with Tomlin). This flustered the new worker, and Matt Carter got on the line to see why Louie needed Tomlin’s number, at which point the ruse unraveled.

The system was called into question one day when the office manager received a phone call from one ‘Christ, Jesus’, which for some reason they immediately thought was me playing a prank. I was offended, not because that kind of goofing around was beneath me, but rather because I wish I had thought of it.

As it turns out, several months after rolling out caller ID, we introduced a new web application for people to sign up for small groups, and one of the steps was for people to enter their contact information into the system. One young adult small group leader thought it would be hilarious to have Jesus in his group, so he signed him up; Jesus Christ, address: 2000 Salvation Drive, Jerusalem, TX 12345, phone: (000) 000-0000. That last part caused the issue, as there are some auto-dialers that send 000-000-0000 as their caller id, and our spiffy caller id system overrides the default message and tells the office that Our Lord and Savior is calling.

Unfortunately it’s going to be years before the little guy looks anything less than pathetic compared to the rest of this forest in which I live. Luckily, I know a little bit about television sci-fi and my sisters gave me a delightful present for Christmas, so I hung a lantern on it.

Lantern hanging off my small oak

Last week I was thinking/discussing with some people how there is a market for a router running custom firmware that monitors/restricts internet usage and has a user friendly web interface for a monthly fee. Guess Cisco was thinking and discussing that too.

At least it was just in the idea phase.

Snow on my car and house

Austin got snow before Seattle did this year. (So did Houston and New Orleans) Now we just need another few days above 70 before Christmas and I’ll be happy.

The craziest thing about this project is I wasn’t planning on doing it in the first place. I just had so much leftover wood that I couldn’t not do it. (yes, TWSS) I wanted to have that point at the edge of the living room be the boundary between public and private and have a wood to carpet boundary, but I guess since the guest bathroom is public this makes more sense. Of course, I still have extra flooring and no more floor to cover, but I think I’ll live.

Oh and here’s a side-by-side before and after:

Turns out calling timeIntervalSinceNow on a date in the past gives you a negative number. And as now gets later and later it gets more and more negative. So, it will never be more than 300, and our app never lets users refresh the data. Thank God, I never wrote that number out to disk, so if you shut down the app and reopen it, the app will successfully load new results.

In other news I hate rich client apps. If this were a web app, or I had done what I planned on doing earlier and putting the timeout inside of the file, I could fix it. There’s basically no way I can fix it at this point. If anybody using the app reads this. I am sorry. My bad.

http://www.statesman.com/news/content/gen/ap/TX_Texas_Earthquake.html?imw=Y&plckCurrentPage=0&sid=sitelife.statesman.com.

As with all good interview questions this one is best done in C. Imagine a singly-linked list who’s data is a pointer to another node in the list or is null. So you’ve got something like:

struct Node {
	Node* next;
	Node* data;
}

Write a function that when passed a linked list makes a deep copy. By which I mean that if you had the following

the function would return:

Well, a pointer to D, but you knew that already. Writing any function that successfully implements the problem description is passing, but the bonus points come when you do it without using any additional memory (with the obvious exception of the new Nodes that need to be created). To be considered all answers must be in linear time (multiple iterations of the list are acceptable, but it should be a constant number of times, but you knew that when I said linear time)

• OS X (Leopard)
• Windows (XP)
• Linux (Ubuntu Silly Something)

Programming Languages used in the last two weeks:

• Java
• Objective-C (iPhone)
• Python (dinky little script for Austin Stone, but still)
• PHP (ASCC again)
• Ruby
• VB.NET (sorta, was used while conducting an interview)

I don’t know what the cost in depth is when trying to stay current in a number of different technologies, but it does make me keenly aware of which technology space I’m in. Objective-C ticks me off when I need to manage my own memory (especially when there’s so little of it). Java when I deal with hashtables or delegates which are so wonderful in other languages. PHP when I have to look at it. VB when I think about arrays.

I need to get some time in on C# here before too long. I’ve heard there’s a 800 character long regular expression that can convert Java 1.4 into C# 2.0 and vice versa, but there’s stuff like LINQ that I’d like to get my hands on.