Feeds, Needs and Speeds

Well, it's starting to get real. The database, that is. As I posted earlier on Twitter, 200 rows of data in a single column do not a RDBMS make, but it's a start (the count is currently 224). As Jackie Gleason quipped in one of his signature lines, "And away we go!"

The casual reader may be wondering at this point: there are actually folks out there still building relational databases? Isn't the non-relational NoSQL model more popular in terms of new deployments, versatility and just plain coolness?

I'd like to explain a bit of my personal journey that brought me to Forty-Two, the database.

Long ago, like teenagers everywhere, I faced highschool graduation without a plan. Not just a clear plan, mind you- NO PLAN. Computer Science was in its infancy at the time, and nearly nonexistent in most high schools. I was not one of the cool kids, nor was I a jock or a brain, but I was also not a nerd. However, I knew one or two nerds. And the nerds were highly focused in their scholarly discipline: they were not into math and science; they were into math. They were geometry slingers, wearing leather slide rule holsters on their hips. They had glasses, thick glasses. Below average complexion. Few social skills. Pocket protectors in their left shirt pockets. And behind the pocket protectors... punch cards for their next "program".They were the late 70's analogues of Drs. Sheldon Cooper and Leonard Hofstadler (The Big Bang Theory).

I was not them. Well, sort of not like them. I liked history. I was (probably) the worst kind of history nerd: I was a military history buff. I started out with Avalon Hill games like France 1940 and Panzer Blitz, and progressed to Tobruk and Squad Leader, eventually culminating in the non-Avalon Hill classic Fletcher Pratt's Naval Wargame. The point is this: as the complexity increased, the playability decreased, as did the number of folks willing to take on the rules. But, I digress.

I was accepted to Rosary College (later Dominican University). I declared history as my major, and spent two unremarkable years there. I eventually had five colleges or universities under my belt, with no undergraduate degree to show for all of the buckazoids invested.

Long before this became a mainstream theory in education, I discovered that we do not all learn in the same way, and that higher education was not really the best choice for me.

Fast forward a few decades. I've mentioned this fairly recently- I was working as a data analyst at an "action sports" company. The company designed paintball equipment, and had it manufactured overseas. My job as the data analyst was to take Wal Mart RetailLink data and dice and slice it into what my employer could use.

The problem was my employer was using either Office 2000 or 2003, which limited Excel to a maximum of ~64K  (I believe it was 63,536) rows. As time went on, my data often exceeded this artificial limitation, and I was forced to use Access just to grab the Monday morning data. Once again, skipping several steps, I became adept at moving data between Excel and Access.

Fast forward one more time to today. I use all sorts of tools to do my job; Access and Excel aren't really part of my professional portfolio of commonly used programs on the job, but I use them at home,.. pause for effect.

Yes, although I may have mentioned a bit about Forty-Two before, I don't think I've said too much beyond it was my own little database dev world. Here's where the title comes in: way back when I was an I.T. reseller, we used to often qualify sales by talking about speeds and feeds- equipment specifications. Needs are also important (besides completing the alliterative trilogy).

So, Forty-Two is an obvious reference to Douglas Adams works, and is so named because its' goal is to answer that elusive question: what is the meaning of Life, the Universe, and Everything. It is starting out life as an Access database, currently with only one table. Previous iterations have taught me to take it easy with adding tables, so my aim is to get this Titles table to be mostly complete before adding additional single- or very few-column tables and then finally starting to create the relationships.The first table is called Titles simply because it holds titles: books, videos, software... if its media, then its name goes here. Why? Forced normalization: why go through the normalization process when I can start out with a relatively clean dataset?

This is starting to turn into a wall of words (by my standards, anyway!), so stay tuned... Lego is next!

As always, I am hochspeyer, blogging data analysis and management so you don't have to.

Forty-Two, v7 (or so)

I've been spending a fair amount of time on Twitter (@CjoelHarrison) lately... so much, in fact, that other elements of my e-life have been suffering. Case in point: this blog. In January of 2015, while I was establishing my presence in the twittersphere, I did not post a single blog. Possibly even more tragic, my playing time on Rail Nation has suffered tremendously. And don't even get me started on my lack of quality Steam time... I'm not certain when the last time I played Sid Meier's Civilization V was.

In any event, here I am once more heralding the latest iteration of my pet database project, Forty-Two. This may indeed be Version Seven; then again, I've not kept track, so it could be any number greater than three. This iteration, though, is different from previous ones: it was not necessitated by a hardware crash or a software glitch. Rather, it is simply a fresh start with a few ideas to make a (relatively) large dataset more organized.

So, I suppose the logical question would be this: why would a home user with no database training want to even try to build an Access database in the first place?

I suppose I could just write it off as an Aspie thing- a project that goes on forever without a realistic chance of being completed (I'm not sure that's exactly an Aspie trait!) It could be that I haven't learned MySQL yet, or haven't even tried NoSQL, and let's not even bring Hadoop into the discussion!

The reality is a lot more pedestrian. And practical: I want to know what I don't know.

In plainer speech, I want to learn how to build a small relational database from the ground up. I want this database to be useful to my family. And, possibly the most important reason for building the database: should anything bad happen, I'd like to have it as a record for an insurance claim.

So there, that's what drives me to keep on trying to build Forty-Two, the database that answers the question of Life, the Universe, and Everything.

The other side projects that have been taking up my time are coding. Professionally, I'm a programmer. The interesting thing about that is that even if I spent the majority of my time programming, the world would probably not recognize me as a programmer, because the tools that I use are very specialized and are more related to composition and layout than programming- and when we DO actually write some code, there is absolutely no way it con be confused with a Turing complete language. Still, some of these tools DO have actual programming, and to help myself to better understand these areas, I've taken to studying the Python language.

Gasp- it's official now: yours truly is studying Python.

print("That's all for now folks!")