Although I have yet to formally introduce WapSnap and release a Beta version, I have been thinking fairly in depth about how I would like a software company to be run if I decided to push WapSnap or any other project into the main stream. I have worked for multiple software companies and used enough products to believe that I can at a minimum spot what should and shouldn’t be done. Anything I miss will be an educational ride.
Ease of Use
When it comes to web based applications I do not know of any application that is as easy to use as WordPress. WordPress has always been well known for a straight forward installation that can get you blogging quickly. Although I cannot speak for myself, I have friends that have switched from developing websites and applications in Joomla and Drupal over to WordPress because it is said to be very logical and easy to customize. With the introduction of the one click upgrade I can see how that would be so. One of the biggest problems I have seen in using open source solutions is that the script kiddies get the security updates when you do and usually they can write an exploit script before you can upgrade and test an application along with all of it’s 3rd party components.
With this information in hand I have decided that when my application rolls out that I would like it to have the ease of use of WordPress.
Having to work on a poorly documented project or application has to be one of the biggest time waisters. When something isn’t documented well you spend most of your time debugging and chasing down answers in a forum instead of moving forward with what needs to get completed.
This is why I want documentation like CodeIgniter. When I started searching for a PHP framework to pick up, I started by looking in the documentation section of each. First stop, the getting started guide, then to the full docs, and then to the forums to see the amount of threads that go without a response. When I got to CodeIgniter I started with the first video tutorial which actually worked and was easy to follow. Wow what a concept, I say this sarcastically because this was not the case with many other frameworks that I tried.
Another positive of the CodeIgniter documentation is that it is easy to follow. Everything is separated out and named logically, this way if you do a search you are likely to find what you are looking for. I also enjoy that it doesn’t read like a 500 page manual and it isn’t a huge PDF that has to be churned through page by page. The CodeIgniter guide makes use of simple elements like line separators, code boxing, and bolding that makes the entire guide easy to read and follow.
With this information in hand I have decided that when my application rolls out that I would like it to have the documentation of CodeIgniter.
I think that anyone who has been in the IT arena for any length of time understands what I mean by poor support.
This is when every time to call with a problem you only get a message machine.
This is when your SLA’s are never met and nobody seems to care.
This is when you post to a forum and nobody answers.
These all constitute poor support.
Nusphere is one company that I have dealt with recently that has fantastic support. To start with, even before I bought PHPed I posted to the forum and quickly had a response. This has been the case for every forum post that I have added to the Nusphere site. Nobody ever asked if I was a customer,how many licenses I had, or did the tiered support two step. Another honorable mention from a recent voyage is Slicehost. Slicehost provided multiple support routes where I didn’t even need to open a ticket. I went to their chat channel and had a solution within minutes.
With this information in hand I have decided that when my application rolls out that I would like it to have support like NuSphere.
About a week about I wrote a small post ( SugarCRM Atlanta Meetup – Tips, Tricks and Tools ) as a follow up to a local Meetup that I attend and assist in organizing. After writing it I had to run out the door so I saved publishing until I could double check for spelling and other errors. Once I returned, I published the post and didn’t log back in for a few days.
A few days had past and logging in showed that there were a few plugin updates and one Worpress update. Using one of my favorite features “automatic upgrade” I made a few clicks and the job was complete. Shortly after I checked to see how Google was doing with parsing my latest sitemap I realized that there was 1 404 error where a page could not be found. It was my latest post. I proceeded back to my blog admin section and it was completely gone. I am still not sure if it was the WordPress upgrade, a plugin upgrade or bug, or just user error.
The next step was to get it back. No matter how small the post, nobody likes to spend time disseminating information to have it disappear.
Step 1 to getting it back was to see if it still existed. I logged into the database and searched through the posts table until I found the post. Luckily it was still there.
For step two I logged the id of the latest revision of that post and then opened the edit view on an existing post. After that I substituted my ID in the URL. This didn’t give me the edit view as expected but a revision view showing the latest revision and all past revisions. Since I didn’t see a way to post that revision or save it in some way I simply created a new post on another tab and did a copy and paste.
Now my post is available for the world to see. Hopefully you don’ t ever loose a post, but if you do, here is how to get it back.
- No public Twitter messages.