Shockey Monkey

Futility of Incompetence (how Monkey is made)

I have been fortunate enough to build a big enough business that calls for a lot of decisions on a daily basis - so statistically speaking, I get to deal with a lot of incompetence. I have gotten so good at it that I am no longer afraid of failing, and even have that little sixth sense when I can feel my ass getting bit as I'm making a call. Most failures are of the "Ah crap. Oh well." nature, learn the lesson, hope not to make it again, move on..

Then there are those failures where you don't get to shake it off and move on. The kind that grab you by the back of your head and rub your face in it. The kind that make you deal with your failure, all day long, while making you shake your head in slight disbelief at just how magnificently you suck. The kind that when you turn to your friends for some comfort they not only laugh at you, but also tell you all the other bad sides of your failure that you haven't even considered. Such is the story of Thursday in Vladville.

This entire week I have been deploying Shockey Monkey 2.0 into a sandbox environment for the purpose of both testing and further development. It gives me a chance to write the deployment scripts and scenarios and also go through all the #VLAD code segments where I left a note for myself to spend more time on. Maybe I am alone at this, but I am far from a linear programmer, when things are going well I just keep on cranking it out and leaving breadcrumbs in the areas that I need to visit back later. Mostly complex validation, bounds checking, fixin' the stupid user, etc.

Yesterday I decided to take the entire day to improve the UI a little. The biggest reason for the lack of management software adoption in business is the visual design. If a user has to click on 50 links in order to enter time, or if they have to dive through 6 tabs, two popup windows, three inline divs and one link to just say they took 2 minutes to call the vendor.. guess what, they aren't going to do it! Now, some say that if you want a paycheck you'll do it but threatening users to use the software or not get paid is not a good company morale move. Truth is, the software sucks. For the love of god, one of the two solutions that loosely compete with Shockey Monkey are either so poorly designed in both form and function that they require a friggin University to figure out. The other one follows the abandoned concepts of each era of UI design: never be afraid to pop up a window, whenever possible stick crap into a frame and back it with ActiveX so it only works in one browser (poorly) and lace the interface with more stars and input field forms than a warez site trying to get you to click on as much porn as possible before it takes you to the actual download. I thought I could do better than that.

Boy was I wrong. Yesterday I decided to improve my time entry UI. Here is a tiny screencap:

smentry

Now the first obstacle is trying to make sure that the time format is recognizable by the people that don't follow the AM/PM system. Since the monkey is famous worldwide, this was more than important. So I ping one of my partners:

Vlad Mazek:  ping
Ian Watkins: pong
Vlad Mazek:  question, if you got a moment
Ian Watkins: Sure
Vlad Mazek:  when you're entering time, does it take the 24 hour military time or the american am/pm time?
Ian Watkins: Both
Vlad Mazek:  you use 24hr, rght?
Ian Watkins: Can sometimes get confused
Ian Watkins: Sometimes :)
Ian Watkins: But we tend to use it if we need to be specific
Vlad Mazek:  well, you've been pretty much useless to me today, Ian :)

Now here is what the above actually means, in my mind: you can't count on the user to follow the form, so bind onChange and a few other events so when they enter 23 instead of 11, deduct 12 from their total and flip the am/pm select box to the proper index. This isn't hard, it's just a giant pain in the butt. Fast forward a few hours, I try to seek some positive reinforcement from my peers:

Rich Walkup:  oh i've done all that before - trust me - i used to work on a biometric payroll system with a computer timeclock
Rich Walkup:  what really sucks is .....
Rich Walkup:  when shit starts at 11:30 and goes over the DST
Vlad Mazek:   and ends at 2:00? :)
Rich Walkup:  sorry to throw a wrench into your system brother but....

Visions of someone starting a time entry at 1AM on a DST day and ending it at 2 AM on a DST day fill my head with livid rage, because I know someone will do this and of course they get paid $20 million an hour and this could bankrupt them so they demand free crap. Note to self: Add an address input field to the signup form so if/when this happens I can go kill the bastard.

You see, in college I used to teach a CS course. I remember saying things like: "I understand that these fundamentals are hard for some of you to do because they are time consuming, but they help those who have never programmed before learn how the data is processed, how to do proper error checking, how to write good software." and I would generally murmor something about how by the time they are writing any commercial code these things would be built into the IDE anyhow and will just require a drag and drop of a time control.

Yesterday I spent all day writing time validation functions for Shockey Monkey. My professional development career has effectively been reduced to keeping stupid people from trying to bill 26 hours in a 24 hour day.

FMR.

Monkey in the land of Not So Free

Today is a bittersweet day at Casa de Vlad. On one hand, I am stoked that yet another product of mine is going worldwide as a commercial success. On the other hand, it’s deployment is guided by a political/trade compromise that is very hard for me to take.

I have made my dislike of a certain subcontinent and what its done to the American economy a subject of frequent parodies on this blog. Today, the shoe is on the other foot, and America, the land of the free, is no longer a place trusted by the businesses or citizens outside of USA. Captain’ Chokes on Pretzels and the Patriot Act have made our neighbors to the north hesitate to store data in USA. European Union actually has laws requiring notification when the personally identifiable data is stored on servers in America. Yup, the land of the free is not good enough for the privacy laws. Australia and NZ are trated like distant cousins crashing the family dinner and being asked to pay for their meals - the cost of bandwidth down under is nothing short of unreal (think US cell phone data while roaming).

So today, as the servers are being prepared and shipped to Sydney and London, I do so with a very heavy heart. Not that I am a stranger to the world of global commerce, but this move is not to create a globally redundant network, it is being made to appease the foreign governments and admit (with my money) that we are no longer the #1 most desireable country to host data. Sucky feeling.

Not all bad news, there is a little saving grace in Shockey Monkey’s promise back to the community that helped build it – that it will be hosted in the countries that helped  put it together. At Shockey Monkey 2.0 launch we will have a home in Dallas, Los Angeles, London and Sydney. Worldwide monkey domination

 

The Eve of Shockey Monkey

SmlogoIt’s hard to believe that it has been nearly two years since I first shared the vision of Shockey Monkey, even harder to belive the amount of people and effort that went into building this beast. Tomorrow I get to talk about what I’ve been working on for over seven months, largely by my damn self, to pay back the people that make my business so damn successful. Talk about a payback, the affordable SMB practice management software built by the SMB people, void of the political mess that makes the other commercial solutions suck and force SMB into the compromise.

While I certainly wish I put more resources into this from the getgo, I don’t think the product would have been this good if it didn’t take every single feature from the actual people that run these practices. The learning process that I went through in bringing this to the market fundamentally changed the way I run my business in the SMB space, and in turn became an ultimate symbiosis between the world of SMB consulting and the world of management system development.

The people that will be paying for this software will not only be supporting their own community (SBS group kickbacks), they will be financing my new development company. Talk about pressure: my success is directly tied to the savings and success that Shockey Monkey has within my clients practice!

This has been a journey fillled with learning, learning and more learning. I cannot thank all the people that have taken their time to be a part of this process enough. If you’ve been waiting…… well, folks, trust me, it’s been worth it. You’ll find out just how much throughout February!

Working with EU: Does location matter?

With the launch of SM 2.1 (yeah, yeah, looking forward, you’ll get the details on Monday folks!) and its commercial nature I have to cross the unglobalization bridge that the US has been burning and pissing on for quite some time – nobody trusts having their data in the good ol’ USA. Even care free Canadian’s are hating the Patriot Act. So it’s sever shipping time.

As far as I have been told, UK businesses have to disclose if any confidential data is going to be stored on the servers outside of EU. I may be wrong (if I am, please correct me) but I have heard the same from users in France, Germany, Italy, etc. One question I do have is, does it matter where in the EU the servers are located? I am currently considering Netherlands and Germany.

For Australia, I am still working on it. There may be a significant premium to having a localized server (20–40% depending on the number of users – the 2 IT shops in Malta are pretty much screwed) and some places are just not going to be possible at all due to the IP allocation restrictions.

Looking for Project and Network Documentation Volunteers

I'm looking for some volunteers to help with the best practices on Network Documentation and SMB Projects. This is a part of my soon to be announced agenda behind Shockey Monkey 2.0 and the way the product is being positioned outside of the backoffice. Thats about all I am willing to say until the week after February 4th when the Shockey Monkey conf call will happen. (if you are a current SM subscriber you'll really want to be on that call)

Concept Description

Network Documentation - Picking up on the great work by Karl Palachuk, this will be an electronic network documentation offering. The problem with paper based network documentation is that it is obsolete the moment it is printed out. Still, it is a huge asset to the company because it identifies what it owns. I would like to come up with a basic set of network documentation items (server passwords, ISP information, etc) and a more complex one that will be commercial. At this point I am considering offering the ability to create your own templates and the ability to purchase other templates for your use.

Read between the lines: I am looking to create a commercial layer where you can make money by creating electronic forms and selling them to the other Shockey Monkey users who can in turn make SM a tool the company cannot live without, an asset instead of just your own backoffice automation tool.

Project Management - Again, pimping Karl because he turns vapor into wine. But as you may imagine, this rabbit hole goes even deeper than it appears. We all know how to move a domain from one registrar to another. We also know how to switch around MX records. We all also know the syntax to export users from the active directory. Not brain surgery by any means. But quick, can you in a single sit move a pop3 user to Microsoft Exchange in the office and roll out ExchangeDefender without referring to any documentation while the phone simultaneously rings while your boss is beating you down for not being a profitable asset of his or hers company. If so, come and work at Own Web Now, we're always hiring! Ok, Ok, back to the topic :)

The concept behind PM is not to replicate the functionality of Microsoft Project or other tools that nobody with less than an 8 figure project uses. The concept behind SM Project Management is to create a process for the project. Assume process is deploying a brand new server into a p2p environment. The SMPM (another acronym) is to create series of tickets and forms that can be assigned and managed by multiple people. Heck, even one person can get distracted and thrown off their game far enough that they miss a step and take 5x longer to do the simplest task. But if there was a checklist, or better yet, if there were trouble tickets to go along and update as each part of the process was completed it would become rather obvious just how far along the project is, it would become easier for multiple people to work on the project and it will become easier to get contractors to manage aspects of it too! For example, what if you outsourced the box drop, cabling and connectcomputer tasks to someone that is more suited to sitting in front of workstations and running cables and fans? You could now integrate third parties into your project and because everything is outlined in canned (that means per-populated / pre-set) tickets the process goes on without your constant advice, followup and explanations.

Just as in the items above - mo money, mo money. Think of it as a layer of compensation for community participation.

If you are interested, please drop me an email at vlad@vladville.com. Please be patient as I only check that mailbox once a day and at times there are hundred messages, or thousand messages. Preference will be given to the individuals that are using Shockey Monkey (eventually) but this need not be locked down because of what I will be discussing during February re: Shockey Monkey 2.0

Owned by the Monkey

No Vijay, it’s not what you think.

Last night at about 9 PM I thought I’d sit down and work on a new feature and try a few more interface tricks I learned. The concept is pretty simple – make bookkeeping so easy everyone on the team can do it. Hopefully through the process more projects are handled to completion by the same member of the team, there are no drops in communication between the person that sold, the person that provisioned and the person that billed the customer. It might even make people more cognizant of how money comes into the company and how through just a few more clicks we can be that much more productive. So the natural thinking process is, once the order is completed (say upgraded quota, or new ExchangeDefender account or whatever) there should be just a few more clicks to update all the accounting. It already happens on the backend, but from time to time there are questions, mistakes.. This just cuts a lot of phone calls.

This is where I pwned myself. Looking back, its almost like a self-fulfilling Dilbert strip staring me, from start to finish. I’m coming up with stupid features, I’m designing them, and at about 2 AM cursing myself for the stupid idea to do this in the first place.

First, I decided to allow the admin to create billing objects on demand.

Then, I decided that those objects shouldn’t be fixed but dynamic and buildable on demand.

Long story short, I went from a few HTML input fields and a few SQL statements to a full blown table, form, validation and query designer.

My brain hurts. I wish I was dumber, at least I wouldn’t be going to bed at 4 AM.

Relaxing.. Focusing.. Grooming Pointy Hair..

icon_the_boss Today, I am the perfect Pointy Haired Boss from Dilbert Comics. Not only because I run a software company or the genetically deformed head that extends outward symmetrically right where the pointy hair grows, but because I downed three bottles of Nyquil and god knows what else over the past three days. Those of you that had to talk to me this morning, sorry.

So here I sit with my 3 IQ points, reading Karl's book and contemplating the release support strategy for Shockey Monkey. The software itself doesn't matter, I could be launching Sheep Herder 3.0.8 and still have the same problems and the ethical dilemma that comes with the support of such a product.

Regardless of situation, there are only two ways to provide support for a software product: before shipping or after shipping.

Support for software before shipping comes in the form of writing documentation, designing the web site, etc. Pretty much the stuff that nobody ever reads. Support for software after shipping comes in the form of frustrated, angry users who have encountered an obstacle that must be fixed, yesterday. Because everyone is aware of nobody paying attention to #1, they end up costing out #2 as an expense that is variable with the product uptake - if lots of users use our product, then we'll have lots of revenues and lots of room to provide technical support to people that didn't read the manual. But eventually the firm just stops writing a decent manual to begin with because the smartest people that can actually use the product will be able to get it going right off the bat while the ones that don't will likely give up on the product no matter how well its documented.

So I find myself in an interesting position. I have already written and sold a ton of Shockey Monkey, so my commercial launch timeline is flipped backwards. Now I'm sitting here trying to figure out the documentation aspect - video, audio or a book?

Update on Shockey Monkey 2.0

SmlogoI wanted to offer a little update on Shockey Monkey considering that I haven’t kept you up to speed on all the developments and have missed the November deadline with the hopes of going commercial on Jan 1. Unfortunately, I will be bumping that later deadline to February 1st, 2008 or roughly a month from now for the launch of Shockey Monkey 2.0.

I want to say that I truely appreciate the amount of support and input I have received through the whole process. There are now three of us working on Shockey Monkey and the delay was related to a number of reasons, most of them centered on supportability - both of the code/platform and of the people using it. It turns out that SM is generally the first helpdesk for most users and most people have questions about how to implement it, how to customize it, etc. This required a lot of documentation, which later got scrapped for video, which later got scrapped for something I never thought I’d ever do.

The product has grown fundamentally and gotten a facelift to accomodate the message I’ve been sending for over a year – that its all about customer service, not making sure that as little of it gets done as humanly possible. This required quite a bit of code, I had to bring people on, clean up a lot of items, etc.

There are a little over 3,000 active users of Shockey Monkey. Over the past three months there has been a slight percentage dip (about 400 or so fell off the face of the earth) which means they either changed their mind, ran out of business, switched to a different helpdesk solution.. best of luck to them. We feel this is a very long term investment for all of our clients and our partners clients and have been working very hard on bringing the 2.0 to market.

I decided to call it 2.0 because it brings a lot of concepts that I explained on the road to fruition, it is not just a CRM rip. It’s more of a system.

But more on that in January.

P.S. I still aim to offer this as hosted (our server) or downloadable virtual server / vmware image (your server); The product will remain free through February, by the time all the bug fixes are completed in February we will look at a commercial route. Also, starting with February, the product will be fully supported by OWN.

Howto: Speeding up AJAX web applications with htaccess and mod_expires

After the millionth time of watching my mobile phone choking on loading quarter meg of Javascript of Shockey Monkey’s new mobile rich interface I finally remembered the pain while searching for my lost Blackjack earlier this afternoon. Not only did Katie find it (love yooou honey!) but I also sat down to finally put the pesky Javascript static-code reloads to a grave.

Here is an article on how to use Apache’s mod_expires to enforce selective caching of javascript files.

http://www.vladville.com/using-apache-mod_expires-for-faster-ajax-sites

That sounded like a mouthfull. Here is what it means: I telll your browser how long it needs to cache my Javascript code. One day? One month? One year? My call. By telling it which Javascript libraries do not change often I can force it to cache them and not have to download them every single time. Faster load times, less bandwidth, more efficient experience. And hopefully less need for a phone warranty as you watch that GPRS ghettonet connection struggling with the last few K worse than a fat man with the 26th mile of the marathon.

P.S. Yes, of course I am still working on Shockey Monkey! Lack of hype does not translate into lack of development, there are over 4,000 people using, you didn’t think I’d just let that slide did you? Geez.

Shockey Monkey Activations

I know its been a few weeks since I closed down the signup forms for Shockey Monkey but the avalanche of signups was so big (along with the other internal OWN issues I mentioned) and it has taken me a while to process everyones signup – I am about a day away from being done though!

I estimate that all the people that received the “You’re in email” will be in OWN Support Portal by the end of business tomorrow, and I hope that everyone is up and running and online by the end of the week. Please remember that once you get the welcome email from the support portal you need to update the contact and company information (this is required in order to generate a valid SSL certificate request) and then follow the instructions to order Shockey Monkey (which is free, for now and for a while); After the SSL certificate is generated you take it to GoDaddy or your choice of SSL signing places and obtain the cheapest possible SSL certificate signed for Apache. Copy and paste the certificate (or attach) to the order ticket and I’ll get you up and running by the end of this week. Promise.

Considering that there is no way to get Shockey Monkey anymore, this is the end of the line where I’m going to be the sole marketer / developer / activator and manager of the project so things will start moving quite a bit faster from now on.

For what its worth, thank you for your patience and I look forward to spending most of my time on development again…