New phone development...

Last month I posted about the purchase of my new Android based LG Thrill and remarked how I was going to write that next flashlight application that everybody would want. (There are hundreds already out there). In reality I wanted to get into the Android development paradigm because I found the IOS development environment restrictive in various ways. ( You need a Mac... You need to use Code... Natively you need to learn ObjectC). To that end I have installed the latest bits of development requirement on my windows 7 laptop, and started toying around with the Java based development environment for the Android device environment. I found the initial Hello World style of application easy enough. I also found the task to deploying the application refreshingly simple. Code signing and certifying using the development environments own sample certificate to sign the apk package and I was able to just send to blue tooth device on my laptop to place it on my phone. Once the file was sent to the phone, the phone itself asked what I wanted to do with the file. I selected to install it where Android dutifully did so and the test app appeared in my set off apps. Touch it and it runs just as you might expect.

The development environment also allows easy sending of test applications to the software based Android emulator. you can use one of the 3 pre-built android configurations that came with the development environment, or you can build one with specific parameters that you want. IE Screen size, Memory, SD Card Size, and so on. Using the tools I built a emulator environment that closely matched my LG Thrill in feature set. and I use that emulator environment when I want to test an app without sending it to my actual phone.

I purchased a number of books via Amazon on Android development, and have them on my Kindle app in my IPad, (I still think the IPad makes a better kindle than an actual kindle does), and I was just playing with Java in Eclipse with thee android SDK when I came across some information about MONO Droid.. and my whole life changed....



Mono Droid Main web presence... Wonders did my eyes behold....

MONO Droid is a port of the MONO development paradigm to the Android device pool. Its an offshoot of Xamarin's MONO Touch environment for the IOS devices (IPhone and IPad). I had basically forgotten about MONO Touch because it was initially owned by Novel and they gave the whole project and the staff working on that project, the axe last spring. My office, full of bits of technology that are no longer supported, had no room for yet another one so I gave up on writing C# for any of the I-devices. Well the original Novel development team lead by Miguel de Icaza, formed the company Xamarin out of the ashes left by Novel and are carrying the development forward. MONO Droid is a port of the MONO runtime with support for the Androids native libraries and features. It allows me to write C# code in the native C# environment I use every day for a living, Visual Studio 2010. From my own comfort zone I can write in the language I am most familiar with, in the environment I am most familiar with, to target my Android devices. (MONO-Touch also exists, for IOS. It affords C# language development for the I-devices but it has some of the key barriers for me personaly in that it requires a MAC development environment)
I first downloaded the trial of the MONO Droid sdk from android.xamarin.com and installed it. The SDK installs a number of things that support its needs including the MONO run times, and MonoDevelop (A visual studio like environment for those folks who don't have Visual Studio Professional). It also installs a number of add-ins and templates that expand on Visual Studio 2010 to support Android development. After installing MONO Droid, Visual Studio showed new project types in its new project dialog for various ANDROID deployments. Selecting one of these new project types creates a new project with everything needed to target an Android device.



New Project Dialog Showing Android Templates added to VS2010

The site also includes a series of short tutorials to help someone like myself jump right in and start to play with all the shiny knobs, bells and whistles in this new environment. The trial version will not however deploy to actual devices only emulator images built using native Android SDK that I was talking about at the outset. It even recognized the special emulator image I built to mimic my LG Trill.

Start Emulator Dialog

Using MONO Droid is easy. A simple tutorial available shows how to consume Web Services. Using that tutorial I was able to easily leverage all this code we have written in our silverlight developments. Over a single weekend I was able to write an android application that ports a laarge part of the face sheet functionality of one of our EHR applications (IhSIS). I dial up a persons record and can look at their Address History, Authorizations, Claims, Incidental Expense Requests, Service Provider List, and Supports network all from my Android Phone, Sweet.....



Emulated LG Thrill running my test IHSIS-DROID application actually connecting to my Web service Layer.

- Posted using BlogPress from my iPad

Location:Way up in the air.

New phone..... (First Impressions)

This weekend I decided to break free of the shackled existence that is the IPhone. While I initially enjoyed the simple interface and limited options that IOS presented to me as the user, two years ago, I have since wanted more. Looking at the android platform, mature a bit, and grow in diversity, I found myself beginning to loath my IPhone and its drones of fanboys all mindlessly parroting the party line. Mostly, I found myself somewhat embarrassed by my own apparent succumbing to the reality distortion field that surrounds that whole walled garden. So this weekend I bit the bullet and upgraded my old phone to a shiny new LG THRILL.


Stats...

1 GHz TI OMAP4430 processor with a dual-channel, dual-memory architecture for power and multitasking efficiency

Brilliant 4.3" 480x800 (WVGA) TFT touchscreen with support for glasses-free 3D viewing

Dual 5 MP high-definition cameras for 3D image and video capture plus a front-facing camera for video chat

8 GB internal memory and an included 8 GB microSD™ card.. (I purchased a 32 gig card because I have over 20 gigs of music.)

Dimensions and weight: 5.07" x 2.68" x 0.47", 5.99 ounce (Its powerful but definitely not svelte)




Overall impressions

The screen is very sharp albeit less so than the screen on the iPhone 4. Much improvement over my older IPhone 3gs.

I find typing on the on-screen keyboard of the android OS more accurate than that of the old phone. The word suggestion feature seems to be more useful as well.

Much is made by the apple camp regarding the massive gap in app availability in the app store over the android marketplace. I can say that so far, I have found everything I needed to replace functions and featured apps I used on my IPhone. Most of which are in fact the same versions I used on my old phone, besides, how many flashlight apps does one need?

The phone is fast, fast, fast. Dual core processor makes the thing just slick, even with all manner of extra stuff all sucking on the battery. Battery life I can see will be short though, for me that has never really been an issue, as I rarely need long battery life. However one thing I do like is the fact that I can replace my own battery with larger capacity batteries without having to send it back to the mothership for the retrofit.

One thing I went to android for is to be able to write code for my phone without having to invest personally in a Mac to do so. Also the native development environment is Java based for the android, conceptually a small transition from my comfort zone in C# vs the chasm that IOS's ObjectC presents.

As I said above I have a 20 gig music library. Plugging my phone into my PC for the first time. I was asked by the phone if I wanted to share the SD card via USB. On doing so, the phones SD card appears as a drive in windows. Copied my whole library over which was not a fast operation even by pokey slow USB 2 standards. Yet on disconnect the phone scanned the SD card and recognized my music. Just like iTunes had it organized. Cover art and all. Definitely a pleasant surprise even moving iTunes to iTunes never went as smooth.

Another feature I wanted to employ was faster Internet where available. I waited 2 years to IPhone to support 4g speeds on ATT and I would still be waiting. I also wanted to tether my phone to my PC in places where I need it, rather than having to use my old aircard. While I can now do so on IOS after paying extra, its still only 3g in places where it could be better. Now I have both, and by ditching my old aircard I can actually save a few bucks each month. Oh and it will also hotspot, so I don't have to actually be tethered to use it.

The android OS supports flash in the browser, and YouTube, so more of the web is available than IOS affords me. Though as a silverlight developer that aspect of the web that I contribute to still is off-limits to my phone

The phone has a number of high end features that frankly feel gimmicky and did not contribute to my purchase decision. Most notable being 3d capable without glasses. In my mind a non feature and frankly I have found it to get in the way from time to time. As they say "nothing is perfect"

There are definite differences between various android implementations. Not all of these are necessarily good though. For example, the new phone contained two types of on-screen keyboards. The standard android keyboard featured haptic feedback where the phone vibrated a little as you single finger type, and the LG keyboard the mimicked the IOS keyboard. No haptic feedback, only audio clues. The LG keyboard doesn't suggest words though. Personally I find the android keyboard better. Choice however, is why I went android in the first place, and the combination of the android OS and the High performance LG Thrill, makes me feel liberated and excited again about my phone and what I can do with it. (Note... after posting this I found a buried setup feature where I could activate items like haptic feedback for the LG keyboard. The primary difference with the LG keyboard being that it looks more like the IOS keyboard as it is implemented.)

Now to install all the Development tools and write a flashlight app 8)

Being anal ain't all bad

I tend to be rather short with people and process that I consider overly burdened with steps and detail. In other words I hate 'ANAL' people. Folks who have their list of steps for everything, and follow those steps with religious zeal, bordering on fanaticism. You know the folks, the ones who want the results of report x ordered the same way each and every time as and example. Such a person calls out the national guard when a software change presents output in a different order. Such a person questions the validity of such output simply because two rows of output are swapped. I used to think of this kind of behavior as a bad thing, wasteful of precious time that I have never had enough of. Sweating the small stuff, I felt sorry for these folks, while being annoyed with them in my interactions. These folks are everywhere after all.

Hypocritically perhaps, I find my interactions with systems to follow such an anal pattern. Initially this behavior on my part was undertaken to simply allow the kind of compliance that I feel will come in any such system rollout to the larger whole. Sure the steps followed religiously in testing and development are overkill, unnecessary and wasteful of precious time, but at some point, when I am going to be tasked with deployment and the whole thing gets put under the scrutiny of external eyes, those anal bastards are gonna want all the i's dotted and the t's crossed. I better just do it at the outset, it's better that way. At least that's what I have always told myself.

One such measure I have found myself, initially begrudgingly so, undertaking is to have a complete history of each and every version of project z that is being deployed to a client even in test. This is not to say that through the miracles of source control I could recreate said archive. No rather I am talking about having each version archived in it's own bundle, in a repository on the clients own environment. If the client has a training and production version then there is an archive of each of these items for every version that has ever been sent along to the client. Overkill? Perhaps but required for certain levels of compliance with certain regulatory bodies whose sole existence is to ensure that measures such as this are in force, else bad things will happen inflicted by ( insert big brother here ).

I have been at a training seminar for the past few days. Each day spent from 7am through 6pm in sessions. Of course we have a client who has an urgent need for 16 new and changes to a rollout that I must also attend to. So even though I am away I have to get this stuff done as well. Long nights in hotel room working remotely, and many a early morning deployment to test environment for the clients review. As you might imagine, many of these nights have had me performing these tasks in in a very impaired state of exhaustion. Mistakes in deploying a project of this type can be catastrophic and given the mental condition I am in in these scenarios are inevitable. In these instances I now see a new use for the Anal behavior I have trained myself to follow. It provides the appropriate safety net for the require CYA necessary when you do something like deploy a training version over a production installation at 4am.......


- Posted using BlogPress from my iPad

Location:W Flamingo Rd,Las Vegas,United States

Light dawns onto propeller beanie

It's been an excruciatingly long set of months leading up to this post. All of it spent in death march style months on two tasks that's have consumed my every waking moments attention. Looking over the past few years I am struck by one overriding thought, "What's new?".

Indeed if you read this dusty corner of the Internet, you will see that those kinds of intros have been in an overwhelmingly common occurrence. So with that astonishing revelation I am further struck by another thought, "What am I doing wrong".

I feel like I am in that STTNG episode where the ship is suddenly presented with a debilitating anomaly, rudderless and on a collision course with another ship that has appeared from the cloud. There is carnage and destruction and death and then there at the poker game again. Like a twisted cruel ground hog day from hell. The past few years have been one such occurrence after another. Each time I find myself saying, "Well we won't make that mistake again".

Indeed, we tend not to make the same mistakes again, yet we do find ourselves in the same tenuous position. Fires raging all around, doom and gloom, and a squirt gun filled with gasoline to put them out. Eventually we have either managed to extinguish the flames by sheer will and perseverance, or they have extinguished themselves by simply running out of fuel to burn. (squirt guns don't have that large a capacity).

This particular project presented itself like any other. We engage with it like we have done before, with differences gleaned from the past designed to avoid painful bruising and internal injuries sustained in prior battles. Yet I sit here headed off to Vegas for my end of phase decompression feeling just as shitty as ever. The real problem on this one is that the source of this is really not through with it's carnage yet. The project is not finished, just an important milestone has been reached.

As I sit here thinking about what has gone wrong on this particular project and what has gone right, I find myself dismayed by the fact that the measures we employed at the outset have had the desired effects, it's just that new dis-functional elements have appeared that have wreaked havoc on the project. Like some twisted game of whack-a-mole, we stamp out a problem with process and another more insidious one appears to take it's place.

In this case the new elements have taken the form of a set of overwhelmed managerial elements on the other side of the table. This has resulted in feature creep that has killed our ability to deliver. The cart is leading the horse here and that is never a good thing. Our mistake was not seeing this at the outset and enforcing some measures that stand a chance at mitigating the effects. I am very disappointed, not at the client, but at myself rather for not recognizing this sooner. The whole thing is so textbook, and yet we fell victim to the standard pressures that befall every small company, struggling to stay afloat in what can charitably be called challenging economic times. The client is really in the same boat as we are in all this. They to have economic challenges and pressures to keep parties happy and all the kinds of things that lead this kind of nonsense. from the outside looking in, the problems are as plain as the nose on my face.

I have been reading a few things from other sage's in the industry over the past few weeks, in between compilations and bathroom breaks, and I am struck by the amount of tellings of these same tales of woe. Each pundit clearly outlining the problems in all the gory details that are not fit for children to see, each pundit unable to show a solution that will surefire rectify the situation. That is unless, as a company, we want to price ourselves out of the market. A small and very cut-throat market at that.

So what are we left with? Scorched earth in our wake, bandaged and bruised, we trudge on to the next bit of green pastures. Our collective experience, the bandages for the next skirmish to be held in those green grasses and fragrant woods. The cycle will continue unaltered by the actions of our rag tag group of disillusioned developers until wars end. In my case I can see one one real end to this and it's filled with the witty catch phrase "Would you like fries with that?"




- Posted using BlogPress from my iPad

Location:36000 feet en-route to Vegas

Revelations

Have had a very very busy couple of months. The pressure of impossible schedules and deadlines that seem to come faster than they go have kept me away from this small dusty corner of the inter web for some time. The 80 hour 7 day weeks all bleeding one into the other leading to the sudden awareness of the holidays come and gone, a new year now well underway. This current road trip started on this past Sunday with a one way rental and drive through Allentown Pa. To pick up a co-worker and continue on to Erie Pa. That was to be two days then hoof it to Pittsburg and fly to Tampa. The main source of my last few months labors.

Here in Tampa, our client had been struggling with what every client struggles with in a new development. What is wanted, what is needed, what can be afforded, what order to implement in. As they say same shit different day. Also common in every one of these endeavors I have been involved in we find communications lacking amongst the constituents. In this I felt a major communication bottleneck occurred in a particular department headed, as they all are by a single person. Now there are many times when I have encountered this situation, finding the barriers being the result of a general impedance mismatch between parties. Not to blow my horn but generally that finding has been that the party with which the difficulties arise seemed to alway be out of touch with the reality of the situation.

Now in this case I found out something very interesting and quite eye opening. You see this individual had a former life as a very high ranking researcher in cancer treatments at the genetic level PHD level stuff, lab coats and security badges an all that stuff. After many years of research this person decided that they were tired of that and instead wanted to take on different challenges and decided to enter into information technology management. This person has been at that new and radically different profession now for longer than the former profession. Along the way having engaged into many systems development efforts and designs. This unique person has had what is effectively two lifetimes of profession in the span of time that I have only managed to struggle out a single such achievement ( rather badly I have come to realize ). Oh and this person has a family as well. In my case I can barely keep my spouse able to tolerate my presence, this person not only has been happily married this whole time but managed to have children as well.

I can truly say I am humbled by this revelation. In fact I realize that the communication barriers that seem to be there are not the result of any sort of superior grasp of intellect that I posses, no rather the other way around. You see from an intellectual understanding level I am simply not even worthy to carry this persons sandals. Very Eye opening indeed and further evidence of the distance I have yet to travel in all this entropy.....

False Sense of Security.

Recently I have been involved in a number of interviews and talk sessions connected with a highly involved government audit. As with many of these sorts of things when money is channeled through and organization that has it's origins in tax revenues, Uncle Sam and his mini me's will want to make sure that a series of written doctrines and processes are being followed and adhered to. Failure to do so results in the river finance drying up, followed by the plague of legal locusts swarming in the black cloud of litigation. Such is the lot of doing business with government agencies at the state and federal levels.

I readily acknolowedge the need for oversight of these sorts of things. Indeed our very existence is in some respects due to the fact that some of these sorts of requirements exist. What I do feel is overblown are the reasons cited for some of the requirement. From the outside looking in, a list of features built into the seal of approval from such audits would read to instill some level of confidence. From inside looking out however the vibe is a very different one. Let's take the notion of information security as an example.

In one such engagement we had a requirement for a separate team of folks to be responsible for building a public facing application, rather than the development team being responsible for such endeavors. In fact the actual requirement, had that dedicated build team responsible/required to conduct all such building and deployment activities even into the test environments. The reason cited was to enhance security. Specifically the notion being that a separate person or team of persons would be less likely to inject unwanted content into said application, (read as backdoors or security holes into said application). As if a person who collects a set of components, places them in a specific location on a dedicated machine and then clicks a build button, would somehow magically see a back door phase into view should one exist, just like a Romulan War Bird dropping out of cloak before their very eyes.

I know that somewhere in the past some agency was bitten by some disgruntled nit wit and found itself to be vulnerable to an attack staged by said nit wit. In the post mortum, someone disconnected with the whole mess thought this measure would have prevented this issue. In their report they wrote it up and it has forever been yet another thing that adds to the cost of doing such business. Anyone who has written anything more complex than HelloWorld might beg to differ with that sentiment. In reality that specific measure does little more than keep someone else employed. (admittedly a worthy cause in this down in the dumps economy). Facts are that it presents yet another hurdle to agility in a development effort. Worse yet it contributes to the false sense of security those on the outside have in the workings of such technology endeavors. The world of IT is rife with such issues.There are all manner of certifications and regulations that are in many cases targeted at securing the information within from the unsavory without.

I found myself thinking about this very point as I was standing 50 deep in queue, holding my shoes in one hand, along with my pants because I had to take my belt off as well. Waiting to pass through the xray machine at the airport. My mind wandered from thoughts of pity for the poor soul who was forced to look at the macabre ugliness of humanity as it schlepped through this particular checkpoint myself included. Yet I was all warm and fuzzy feeling the huge boost in my personal safety that this measure of indignity afforded my meager existence. It was then I realized the resemblance this measure had with what we face in in IT every day.

IT endeavors and their interfacings with the general population are full of said measures that are laughable. One collection of said measures goes by the moniker of HIPAA. It's basic premise is good in that it supposed to prevent the unwanted dissemination of private health related information about a person to others persons who are not supposed to see that information. Things like a person name and such. Yet every time I go into a doctors office I sign in on a sheet with perhaps dozens of other peoples names who have come in before me, or when I pick up my Viagra at the Pharmacy I sign a sheet with the same peoples names....

Now I can hear the the supporters of these regulations saying that these measures are necessary and the breaches cited are minor and innocuous in nature. What about when IT worker q installs a policy at the enterprise server that prevented the workstations connected to said server from activating their USB ports. The idea being that those pesky USB ports were conduits for wanton information dissemination via storage keys, smart phones, and music players. This poor IT guy, tired from the weekend of wine and women filled debauchery, having made a typical human mistake and also turned off every one of the hundreds of workstations keyboards and mice. ( they were after all USB devices.) How about that, Marge from accounting, who always complains that her sled of a machine was garbage is the only one working now because it didn't use USB ports for the keyboard and mouse, imagine that. All kidding aside though, this same regulation also is creating serious issues in the world that the promise of IT could address. One such example would be when the same regulations prevent doctor x from knowing that I am being treated for something by doctor y, this because doctor x does not have a release of information submitted to doctor y. Doctor x then goes on to prescribe something to me that runs counter to what doctor y is doing.

I hear people clamoring well you should have told the doctor what you were doing with the other doctor, they ask you about your other treatments don't they. Yes standard practice has you drill out everything you are taking, thinking, doing every time you go into a doctors office. What if you forget a dosage as you are filling out this form for the umpteenth time, what you have been in a horrible accident that has left you in a coma and the ER doc has no way of knowing. Don't kid yourself into thinking that the safety supposed to be provided by these layers of regulation will help you in this scenario, don't think that it never happens that way either.

I work every day with people who know that the sharing of information of this type would go so far to silence the squeaky creaking of a healthcare system that has been on life-support for longer than most of the patients it so treats. The entire system sits in its own iron lung even as it struggles to care and provide services for the people who need it. In a vacuum a single happening requiring said system to provide care and healing, shows that the system can work remarkably well. I break my leg when I am a young child, and I go to the hospital to get it set and cast, revisiting said doctor when its time to remove it and all is well. Its when the picture gets complicated, after years of interactions with the system and people and places involved have come and gone that regulation like that cited prove a hinderance.

The situation is even worse on the behavioral health side. Ironically the stigma associated with substance abuse, mental, and developmental disability issues were a major impetus for the regulation as it stands today. Yet on the public sector side of the population where the involvements in service providers are many and varied and lengthy. Information sharing would provide the greatest of benefits. Yet there is that pesky regulations set in place. The systems employed could easily be made to talk to one another if the regulation allowed it to. Then the real promise of IT could come to provide a real sense of security rather than the Majinot line we have today.


- Posted using BlogPress from my iPad

Location:35000 feet some where over the Atlantic ocean

That which does not kill us....

It's been a full year since the most difficult project I have ever undertaken went live, albeit without a great deal of it's present functionality. Project X as we called it at the time was, at that time, the latest of impossible missions we had undertaken. It was however exciting and when we undertook the effort a mere 60 days prior, we felt we could make the targets. The client seemed fully aware that they were asking for something that would have to evolve into their vision and that the "live" date would be a mere shadow of what was come. This time 1 year ago we were on day 60 of 18 hour days frantically coding to a nebulous specification, fraught with meetings, and other pace killing interruptions. The system was largely incomplete, new versions were being deployed into sandbox almost hourly. The client was nervously excited, we were completely exhausted. I personally had not been home for 4 weeks at that time. Then the switch was thrown...

We went live with version 1.0. Surprisingly enough it was not a complete disaster. A testament to the small but dedicated team we had on the project. The problems that would tax my very desire to continue to live would come later. Simple facts are that we should never have taken the thing with the constraints the project was running under. It needed a full year to be coded right. As with so many projects like this the client became angrier as the pace of new functionality slowed. ( more difficult to perform work on your car while it's speeding down the highway). Design shortcomings not surprisingly began to rear their ugly heads. The days continued to drag on with some of my own personal weekly times logged reached the 90+ hour level over a 7 day span. At one stretch I was not even home once over a 8 week span. The hotel I stayed at thought of me a Howard Hughes albeit a little less a wacko and with no money. That's when things really turned sour. The client called in the parent of one of the partners to take an assessment of what was wrong. The resulting report was, as one might expect, fairly critical of the development team and methodologies employed. The resulting effects on the pace of work was profound.

We got involved in a large number of additional hands being thrown at the project. This being a constant in these sorts of things, were management feels compelled to add bodies to a late project thinking it to be the way to speed things up. This of course rarely works as intended and Project X was no different. The party brought in to assess the situation felt that the only way to fix the issue would be to start anew on version 2 with version 1 limping along in a state of moribund undead stasis. ( maintained by us but not advanced by us ). While version 2 was built correctly by others. All the while the threat of litigation, extremely nasty and contentious meetings continued unabated. Good people who found themselves in situations were there was no winning up and left for their own sanity. I felt envious of them. They had achieved escape velocity and left the madness behind them. I was not so lucky. Pressures within and without kept me at it, why I cannot really say. Perhaps it was cowardice, I would not have been able to find work that paid what I needed, my wife and I would have lost some of the things we had. Perhaps it was stubbornness, most would agree that I have a thick skull about things I believe in. Loyalty perhaps played a part. I certainly would not have wanted to leave my co-workers and my boss in the lurch.

As they say it's always darkest before the dawn, Project X was no different. Slowly things changed a little. A small amount of the disfunction was removed. One of the things that came out of maelstrom of the projects darkest hour was a better process for documenting what needed to be done. Even though a well written business process specification though proved to be ineffectual at times. ( I remember coding up exactly what was written only to have it flatly rejected by the client as improper and incorrect ). Slowly this documentation proved its worth and the client became softer, perhaps they came to realize that the system was becoming what they wanted all along. The project is by no means complete even 1 year later but Project X was still running along. Multiple new releases adding the kind of functionality envisioned at the outset. Truth be told I have since focused my attentions on a similar effort for another client. Over the past 3 months or so even though I still work on Project X from time to time.

The scars of that effort still fresh in my mind have lead to my altering the new projects to some extent, both in the way they are architected, and specified. My own code has changed to reflect some of the ideals that were written up in the assessment report on Project X. Even the stubborn occasionally learn a thing or two. The new project I am on is largely a solo effort from a coding standpoint, I still find myself putting in 80 hour weeks but somehow this is easier. Perhaps it's the client being a little easier to work with. Perhaps it's the lessons learned on that year long death march that left me questioning my resolve. I have been solo largely here in this new effort so that's definitely a contributor.

As we are on the 1 year anniversary of the projects release into the wild. I am struck by one overall sentiment....

That which does not kill us, makes us stronger.

So when I raise my beer to toast the participants at our little party next week I will remember that sentiment, like high school however, I will never want to re-live it....




- Posted using BlogPress from my iPad

Location:S US Highway 301,Tampa,United States