Hi. I'm Scott

I saw  +Steve Karam  write an article similar to this, and I thought I'd try my hand at something like this as well. The Early Years My parents bought a used Texas Instruments 99-4a , when I was in the 2nd or 3rd grade. We had a couple games, including a version of Kings Quest which had to be loaded via a cartrage AND a cassette tape in order to play. I recall the TI having some sort of BASIC interface to load games, or interact somehow via a command line. Shortly after that, We got an Apple ][+, complete with AppleWorks, OKIData Printer and a handful of other games. As I entered my middle school years with this computer, I had to write several papers. If I learned anything from this system, it was this: Save First, Then Print. I lost many a paper on this system, but somehow still have fond memories playing Zaxxon and Oregon Trail on the green screen. My First PC As I approached high school, my family purchased an IBM PS/2, with a 486 processor, 25 mHz and 4 MB RAM. While t

We all have todo lists. Some of us have several todo lists. Maybe each project, or each client gets a list, followed by deadlines, and so on. Thousands of pages have been devoted on creating lists of things to do. A typical productivity guide will devise a way to efficiently develop a todo list. Great, now you know how to build a list...but you still haven't accomplished anything. And lets be clear, you can't bill hours to building a list of things to do. So how do you do those things? How do you start? How do you know what to do next? I'm great at building lists, and terrible at using the lists.

I'm still trying to digest everything that I learned from OOW13. Plug-able databases, data modeling, CTX package, etc. I found myself emailing my boss on occasion during the conference to say stuff like 'hey boss, I just learned about this. We should totally being to this thing .' And it was hard not to wall myself up in my hotel room and work on it until it was finished. Fortunately, I resisted the urge, and kept on attending sessions. Let it be said that Open World is NOT a training conference. I'm not sure I came away with more tangible skills on Friday than I had on Sunday. What I do have, is more knowledge of the tools available. As the saying goes, if all you have is a hammer, everything looks like a nail. After each Open World conference, I feel like I have a new tool available to me. I don't like the idea of being one dimensional, so having a wide range of tools to solve problems helps me be more valuable. Finally, it's not always WHAT you know, but