Random bits of randomness, with an ever-present hint of technology.

God be with you?

God be with you.

A rather commonplace saying in our society, it is meant to convey good will, good wishes - and perhaps a prayerful request that our eternal, omnipresent, omniscient God join you in your endeavor.  While praying that God would bless our endeavors, and those of our friends, is a privilege held by those with a personal relationship with Him, have you ever stopped to consider the meaning of this?

Our God has promised to never leave us, or forsake us. He is always with us, always watching, and always caring. Does the statement God be with you imply a lack of trust? We are taught the power of praying scripture over our lives, and this is a great example of prayerfully repeating what God has promised.

Go With God

How often do we fail to inquire of God His will for our lives? It is a daily, hourly, real-time, repetitive occurence for me to fail to ask God for guidance in my life.  He has a perfect and holy will for our lives that requires only one thing, for us to follow it.  While aspects of God’s will are out of our control, it is God’s will for us to bless those we encounter in our daily walk.

Is there any difference to saying “God be with you” to saying “Go with God”? I would suggest that one is prayerfully requesting God’s promised presence in our life, while the other is an imperative to look to God for promised guidance in our daily walks with Him.  Promised guidance that when followed will align us with God’s perfect will and the blessings He has planned for our lives.

So, my prayer to day is that I would Go With God and find His will for my life.

Check it.

Check it.


By the Light of the Moon

About six weeks ago, against better judgement I agreed to help a family friend out with a “small” mobile application that his company had outsourced to India for development. To cut to the chase, the point of all that follows is to trust your gut.  As evidence I present two items, the first is this post, the second is a much more scientific approach as described by the WSJ.

The first indication that this was a bad idea came when I was given the set of documentation that existed for the product.  This “set” included a single Visio document with an artists rendition of what the final product would like like along with rough scenarios detailing usage of each screen.  The second piece of documentation was the email within which the Visio was included.  The email read, and I quote “I want it to work like this.”  I would soon learn that my project would be considered succesful when the product “worked like this.”

Gut comment number 1: He can’t give you good requirements, don’t take the project.

The second indication of good things to come occurred upon receipt of the code base.  After unzipping the zip file, I discovered that the C# project was full of .vb files.

Gut comment number 2: He said this was written in C# and it is VB (is that even considered a real language???), Don’t Take The Project.

The third indication of even better things to come was the response received after notifying said family friend of two things, the code was written in VB, and there were 2 comments in the entire solution.  The response to the question, can you send me the technical documentation was “I already sent it to you, that was the Visio.” (!#$!#@$%)

Gut comment number 3: There is no technical documentation showing how this thing works in a macro, or micro sense.  DON’T TAKE THE PROJECT.

These type of incidents have continued for the last six weeks, and have continued through this wonderful weekend.  The culmination of all the hours I had invested in improving this product came on Thursday evening.  Upon requesting the mobile device for testing, the pseudo-project manager arrived at my house with said device in tow.  Soon he was showing me how to recreate the “bugs” (how do you have a bug without requirements, sorry I digress) and other various improvements (not documented of course other than on a post-it note.  Sorry, I digressed again!) that he would like made.  I said no problem, and proceeded to make said bug fixes and software improvements as he sat on the floor in my office and tested each fix as I made it.  In addition to this, he did it while on speaker phone with the developer working on the back end application.  All this was done between the hours of 8 PM and 11 PM, during which time my 13 month old child (whose room is less than 5 feet away ) was attempting to sleep.  It was on the third time that he was awakened, and with quite an angry glare from me that the pseudo-project manager said, “Oh, I didn’t realize he was sleeping.  My kids don’t go to sleep until we do.” (!@#$%!%%^!!!)

Gut comment number 637: Never again fail to listen to me! And you should probably punch that guy in the face for making such an asinine comment at 10:30 PM while you are working on his non-documented, VB coded, poorly architected, really really really really crappy application.

First Post!

Welcome to Odd Blog, the blog seeped in randomness with a drop of technology. For my first post on Odd Blog, I would like to point out an article that has inspired me to keep Firefox limited to 5 open tabs rather than 3 windows with 10 tabs each. The New Atlantis has posted quite an interesting article on the Myth of Multitasking. My favorite quote from the article is this: When people do their work only in the “interstices of their mind-wandering,” with crumbs of attention rationed out among many competing tasks, their culture may gain in information, but it will surely weaken in wisdom.

If only I knew the definition of the word interstices, I would probably cut down my tab count to 3 and close Outlook while I was at it. Alas, limiting myself to 5 tabs did not allow me to open a 6th tab to google the definition of the word, so I will leave it to you the commentor to weigh in with your words of wisdom, gleaned from some other site while you were creating your comment for this post.