Latest Entries »

Pleygo No More

madLegoAbout 3 weeks ago we were referred by a friend and fellow parent to a site called #Pleygo. An interesting service hailed as Netflix meets Lego. You subscribe and get a stream of lego sets sent to you. Depending on the plan (low, medium, and high) you can pick from different sets. Medium for example would be about $30 a month and sets would be about $85 on the shelf to buy.

Of course, handing a child a lego set has inherent risk. Pleygo advertises that the sets come with a side bag of extra common pieces; sets are completely sterilized between uses; they allow up to a certain number of pieces to be lost when being returned; and of course have a procedure to buy the set if your child absolutely doesn’t want to part with it.

All of this and a one month 30 day free trial!

Except… It didn’t work. It was a complete fail for us.

About a month ago, we decided to hand them a credit card and see what 30 days would bring us. After one week of Aiden checking the mailbox to no avail I called them. They told us that our wish list (viewing queue) wasn’t full and that they fulfill from the list in order of availability. I explained that there was no mention of requiring a full queue and there was no way to know that everything that was on our mostly filled (80%) queue was all unavailable.

While on the phone, I padded the queue to fill it and noted that it would be a STRONG suggestion to let users know what sets are currently available and which aren’t. I was told that I should see a set within the first 7-10 business days but there was a strong back log.

From here I explained that I was on the free trial. I wanted to emphasize that my interest here was “Trial” not “Free” and that I was evaluating their service. That to this point I had to explain to my seven year old why there was no mail for him on a daily basis and no way to know if there was ever going to be any. The person noted she’s take the comments down (but really gave an attitude of ‘this is just the way we work.’

Last evening, two weeks later, I got a general “Aren’t we great, New Sets” email from Pleygo. It saddens me that at this point they’d all but slipped my mind. I made a note to myself to do a followup call this morning. going to the website I was (less than) surprised that the support phone number is no longer there. There is a limited support section that is primarily driven by community postings. There is also a blog that primarily is proudly talking about their tie in to the recent Lego Movie.

A long time ago I might have had more patience for this. But now money is tighter. The idea of having a wealth of (fairly expensive) Lego open up to my child for far less (even though it was a subscription) seems like a fantastic idea. That being said, NOTHING is worth trying to comfort a crest fallen child every day for two weeks for reasons other than, “I guess we just have to wait, I don’t know what’s going on.”

Obviously, I cancelled my “Free Trial” as I take solace in the fact that at least it didn’t cost me financially to know that the service failed the trial. Honestly, I hope in the long run the idea succeeds. But for now… There is far too much broken in the system for a person to join that ecosystem.

uploadingThe first image upload API is now finished. This API will now take images in any format and save it tied to a relevant record in a web neutral format to the archive. This work took more effort than I expected, but it’s making things move very well. I’ve also fixed several links so that development and production environments work exactly the same. The client is now pulling entirely from the new APIs and works when used over the VPN. For some useless statistics I now have over 100 active source files with about 110 lines of code on average per source. This seems very short but the reality is that there are several subclasses that are very tiny working off nicely complex but not obfuscated super classes. I am likely missing a tonne of material. There are also several test apps that are folded in there whose entire purpose is to test APIs. Once they are removed the numbers will be a little more realistic. However, the important thing in development is not the size of the work but the results.

On the downside I’ve been fighting a bad back for the past 3 days. I will likely be calling my doctor tomorrow to take a look and see what is going on there. On the upside, however, the only chair I find any comfort and support in is the one in my home office. So, as long as I discipline myself to work… the pain isn’t as bad. (Granted, a good bit of Aleve® helps quite a bit)

Tomorrow’s goals are to call the doctor. Implement the location uploader in the DataUploader utility, And make sure that I blog for the day.

 

OfficeDesk-smTime at the desk has been limited this week. The extreme cold has listed Pittsburgh as one of the 20 coldest cities hit by the arctic polar vortex. As a result, My 7 yr old has been out of school both Tuesday and Wednesday and my over/under guess is that he will also be out on Thursday. We are due for another sub-zero with windchill morning. My time in the office has been limited. I have however, had time to finish doing some cleaning to my work desk. I’ve been trying to do a full clean and organise over the past month due to the fact that this is now my 24/7 work place. (If only I were getting paid)

But onto the progress. Software design is often an experience of two steps forwards one step back. Sadly, the one step back also usually consists of several O’Reilly manuals, a bunch of gSearchs, and of course documentation and answers found on StackOverflow. Today was no exception. Finally back on my desktop app for entering data I realised that I wasn’t just doing SQL puts to the database. I was also uploading graphic resources. These however were going into a directory with references being added to the database. Sigh, back down to the API level.

So today, I had to learn in Java (and to some extent on the Client level) how to compose programmatically an upload post and then correctly save it to my server. Now, I (as always) realise that there are probably simple libraries to do this and experienced Java, JSP, and LAMP folks will scoff at the likely banal process this is. I however hadn’t done it before so I had to teach myself. Happily, info was available in the form of a few StackOverflow questions, a couple of nice online tutorials, and a few hours later; my Poster test app is sending the requisite info and it’s causing a file to be saved. This isn’t finished. I haven’t actually put in some of the path and file directives and I’m not sure that the file is storing up in clean shape. But considering the fact that I have only gotten about an hour at the desk today; and that before that hour I didn’t know how to do this at all; I’m kind of happy about the results so far.

Tomorrow, I hope to have more time at the desk (even though the child is home again) and I hope to finally be done on the API level… for a while. Also, I will be having a conference with one of my “volunteers for credit counting.” What this means is that they’ve agreed to volunteer time in exchange for tracking hours and converting it to value once we see more funding. I’m incredibly excited to have this person working on the team because they have great business depth, incredible sense of organization, and a great working relationship with me to call me on stupidity when needed without taking a response of NO personally.

Things trudge, but I think we’re on track to keep moving forwards.

As always, if people are interested on helping out.. I’ve got plenty of work to go around.

I don’t get nearly that much done on the weekend with The Project. Sadly my back went out today so I found myself enjoying the comfort of my home office chair.

I managed to finish up the last of my API calls that allow me to start crawling back up the stack. As a reminder, I started on the end client with hard coded data. Then I went down and created an SQL based relational database to hold the data. Then I realised I needed an app to enter data. Then I realised I needed an API for the Apps to use.

So, thus began my love-hate relationship with Java and Tomcat. Both of which I knew next to nothing about.

Fast forward about 3 weeks.

The first version of the APIs are done. However, in checking the logs for the Tomcat server, I discovered some sites had been snooping around. I had hits from Wichita  Kansas, Brooklyn NY, and several hits from places in China. Needless to say, this made me just a little cranky.

So today, I got up close and personal with two technologies. Tomcat Addr Valves (which is like a Tomcat Firewall) and VPN. After a bunch of minor testing, I can say with (unlearned and naive) assurance; the net-facing service is now accessible by VPN only.

I wish I had more of a choice here; but I don’t. Until I’m ready to open the floodgates, I need to have access for people helping me who aren’t on my internal network while still having the resource accessible remotely. This seems to be the best approach.

Where does this put me? On Monday the first thing I do is gut the old client’s APIs in favor of the new ones. Then I start fixing up the data entry program. Then I start entering about two month of newer data.

Then we can start pushing on that client full speed again. Whee!

ftp-big-iconI’ve been updating my web hosting customers WordPress this weekend. Partly to move them onto new servers with new updates. In doing so I got to learn about ftp configuration on unix. It’s a bit more involved that I was expecting. Quite the endeavor.

Just a short update. Tomorrow we hopefully wrap up the overhauled APIs on the project and move back up the stack.