Shared Windows Mobile Calendars without Exchange

Google, Mobility
7 Comments

Untitled document

Free tool allows you to syncronize your Windows Mobile phone with free and sharing-friendly Google Calendar.

Every now and then I get approached by someone that needs a shared calendar or a good calendar for their use but they don’t need Exchange. Newlyweds need help coordinating their joint activities. Pregnancy or new baby brings up a scheduling nightmare. Party planning. As Windows mobile becomes a commonplace so does the reliance on shared calendars but the only thing Windows Mobile will sync against is Microsoft Exchange. Enter Google Calendar.

Google Calendar, which launched just a few short weeks ago, has become a de facto standard for free calendars online. It is friendly, dynamic, fast… and supports sharing… AND now can be synced to your Windows Mobile device using this free utility: Companionlink for Google Calendar.

It’s free, syncs using Outlook (which is also free with every Windows Mobile phone you buy) and you can sync and share to your hearts content without bringing in Exchange/SBS. Now all thats left is the the disappointment that comes with knowing how boring you are and how little life you have.

Guys over at msmobiles really did a good job selling this and also have a story about G-Spot XP, a free tool to take better screenshots of your SmartPhone.

Update: Whoa, what a bait and switch. Apparently earlier today it was free, now its magically only a 14 day trial. What a bait and switch. I'm sorry I sent you there under the wrong premise (unintentionally) and I would nuke the links to it along with the post except this may be worth it to someone, somewhere. As for the publisher, shame on you.

Hooked on BlogJet

Vladville
Comments Off on Hooked on BlogJet

I must admit, I too am hooked on this BlogJet thing. I’ve only used Performancing plugin for Firefox to do semi-automated posting for QuickVlad but it had far too many problems with my previous blog that I eventually just turned it off.

The blogjet thing is very cool and perhaps very important for me. Why? I’ll leave it at two words: Spell Check. But hey, now that its easier to blog and share, can I give the almighty pope the run for her money in terms of number of daily posts?

Shockey Monkey Demo 2

Shockey Monkey
4 Comments

Untitled document

Yesterday I decided to document my journey of managing software development but I had no idea how much I would learn in just under 24 hours. For starters, I've never prepared myself for an Outlook folder containing "Partnership Opportunities" to have a four figure count of new items as we average a few dozen a week, tops. Second, the word free brings out so much me-too-ism that it begs asking the question of which point actually sold them on the product? I'm an admitted fatass but even I step back and look at what I'm being handed while walking around Costco (they give out free food samples while you shop, yes, its THAT great to live in America). Just because something is free it doesn't make it a good idea. Anyhow, here we go with the lessons so far that begin before anybody sees your product:

Answer the FAQ before someone asks the question

Putting up a wiki takes just a few minutes but saves hours and hours of thread responses and cut&paste activity. Point being: anticipate what your testers are going to ask and document it up front. Doing so puts you in the right frame of mind because you will no longer try to explain the feature or concept as you would to a computer (through pragmatic development, syntax, error checking) but to an actual user. If you do that, you will likely find where you as a human are making the mistakes of relating too much to the computer and too little to the end user. After all, its all about the user experience, right?

To this point everything about Shockey Monkey is sight unseen. It's Duke Nukem: Forever as far as everyone is concerned. So it is important to detail the core concepts of why you are creating this software in the first place. What problem will it solve? 

Give people a place to go

Just because they wanted it yesterday does not mean they will ever pay for it tomorrow. Just because you make it doesn't mean they will come. That is the sad reality every shareware author realizes initially. However, the opposite is true as well. Perhaps I struck someones imagination yesterday but they were between trying to find a dip recipe and flipping the burgers on a holiday weekend. I'm sure they bookmarked the post, either physically, mentally or via email and thats where the thought ends. 

This perhaps was the biggest mistake of all, not having a place to send people off to so they can keep in touch with the project progress. No RSS feed, no web page, no wiki, nothing. Now my circumstance is limited because I just dropped the hot soup into the lap of a site with tens of thousands of daily visitors, but its a good practice to hold nonetheless and one I just learned today: Give people a place to go.

Make yourself available

Someone asked yesterday if there was a chance that the livemeetings would be recorded. I most certainly hope you never succumb to that pressure (or that of a spell check since I have no idea how to spell succumb) because at least initially you are just dying for fanboys. You need people to cheer you along the development cycle but you also need all the eyes you can get. What good is it to just hand out a PR webcast for something that does not yet exist? Thats great for something you are trying to sell but as you're writing the software you need all the help, advice, opinion and angle you can take.

How do you intend to use this software? What would make it easier to use? Here is what we were thinking when we did this, does it make sense? What would make more sense? In which situation do you think this would be applicable? How do you work?

MicrosoftBS has a very nice marketing campaign titled "People Ready" where they talk about how they write software that "works the way you do". Now for a moment just pardon the fact that this message is totally separated from reality, much like most of MicrosoftBS, and focus on the idea of it. You initially identified the problem and tried to solve it – but along the way you can find out from others with the exact same problem and hear their solutions. Yours may not be the best, so be there to hear their opinion too!  

Control the experience

This is a biggie. For most software "controlling the experience" is limiting the distribution to the specific people that may be qualified to break it and provide feedback. This is something I learned just recently from the Microsoft Exchange team. Steer people in the direction where you are seeking feedback. That is, hold a webcast. Show a specific feature. Now that you've seen the feature, what do you think? How will you sell it? Why won't you sell it? Where do you think it will solve the problem?  Don't just aim to control who sees your previews, aim to control in which light the features are seen.

Ask the stupid questions

If you were brilliant you wouldn't need to beta test your software or patch it, ever. But we're all flawed, whether by design or by the experience, so try to ask the stupid questions. Here were some of mine:

Do you like this shade of blue? Do you ever encounter the business that looks at their IT this way? Is this something you'd ever customize? Are we on the right page with this one? Who would do this?

For example, Shockey Monkey has several classes of users each with authorizations to do different things. There is the Administrator and Staff member that work for the IT Solution Shop. There is the Accountant that is not interested in the Helpdesk, just how much we need to bill. For the client we have a Client Administrator (their IT guy that does on-site work, controls who gets to report problems, etc) and the end user, Client. Now this is going to sound stupid but I never forsaw a reason to give Client Administrator the right to add users. Sure, thought of a reason to allow them to escalate tickets, answer tickets on their own, add knowledge base articles, everything but manage users. One gentleman said today that it would save him a ton of time if he could just delegate that client employee management to the Client Administrator. Another remarked that:

"some of my clients change employees more often than they change their underwear."

So don't be afraid to step out of your comfort zone of only discussing your ideas and be open to the ideas your customers bring up. Sure, it might be a huge chunk of functionality that you will have to develop, test and manage but its your duty to make the software people want to buy so you better be open to that feedback.

Thank the cheerleaders first

Oh lord does coding suck. Today I looked at the same 120 lines of code for about 10 minutes before I found what was producing this obvious debug report to be displayed even though I had switched off the debug flag. It just kept on printing the "ticket total" number and I could not find it. So I went through the code commenting half the module out with multiline comments and I found the bug. Whats disheartening is that this wasn't some nasty hidden bug that would have taken a ton of time to isolate. It was just a single line print statement that anyone else would have seen a mile away from my desk. I've been looking at this code for days and it took me 10 minutes to find it.

Development ain't easy. When you get the joy of being in touch with the people that use and benfit from what they do suck up all the cheers and positivity you get. Each atta-boy is worth 50 headbangs against the table 🙂

Conclusion 

CIS & MBA degrees didn't prepare you for that, did they? Now obviously this is not something that is ever going to be seen in the academic materials but if you're a coder and looking for some more real world software development information take a look at a great book written by Scott Berkun: The Art of Project Management.

Shockey Monkey & The MSP Bandwagon

Shockey Monkey
8 Comments

Untitled document

I've quietly watched as my partners transition in the managed services market for quite some time and seen a fair share of MSP pitches from both the community and the commercial organizations. One thing that has been somewhat consistent among the small business consultants has been the obvious price point miss that these professional management solutions had and that small business consultants were valuing the software at.

At the same time we at Own Web Now were working on an upgrade of our internal management systems and we saw an opportunity to get some free help in specing out the future of how we do business. After all, our partners will be using it, what a novel idea to give them a say in how it should operate to make them most effective (and thus more profitable for us). But as I sat there coding the framework underneath Shockey Monkey management system I realized we could really do a lot more with it. I decided to add a few more forks to it.

So we decided to go an extra step: make Shockey Monkey a hosted management system for our resellers and give them the same power to manage their SMB practices as we get in our business. Pretty good symbiosis, they resell our products and make us money, we give them a management system to manage and grow their business with ease. The biggest problems with SMB helpdesks is the cost (free!) and the deployment issues (who wants yet another server to manage, patch, backup, tweak). We can do better.

But Vlad, what are you selling?

Nothing, this is not going to be a commercial product. What I hope to do here is detail my journey on this software development project, the wins and defeats, that you can face as a software product manager. Hopefully it will give you younger whipper snappers in college an idea what its like to manage software development and the monuments of inefficiency that are programmers.

P.S. Parts of this blog post may be outsourced to India. 🙂

Is the SBS community a good substitute for training?

IT Culture, SMB
16 Comments

Untitled document

This is my formal response to this post. I feel that I, as a community leader and a great contributor to it, have the right to this opinion based on my experience over the past 10 years working in IT.

Now I'm sure by now nobody asks why Susan Bradley writes pages and pages of op-ed on her blog. The latest one has been prompted by me and several months of lost sleep discussing the SBS "community" with her and exactly what the value, responsibility and participation in that community means.

Introduction

I have not hidden my disgust for incompetent people that pass themselves off as small business IT consultants. I first met Roger Otterson at TechEd and within about 30 seconds of introducing myself I managed to stick my foot very far up my mouth in my assessment of the small business IT consultants:

“Roger, I have over 4,000 partners out there. Now, only about 5% of that actually does any true consulting or IT business, the remainder of them are just people that failed in the corporate world and thought they could quickly cash in on their mediocre technology skills”

How’s that for the elevator pitch? Although I’m sure I could have phrased this much nicer the truth is much uglier than that. You see, active small business consultants that float up to the “global SBS community” tend to have one characteristic that is invaluable to anybody looking for a competent employee: willingness to learn. Willingness to admit when they need help, willingness to research. Over time that help is paid back, as those that were “new” yesterday become the “gurus” of today. It’s a good thing, this is why we go to events, this is why we network, this is why we promote the concept of community in terms of working together, sharing our problems, successes and failures so that we can globally help one another win.

The Problem

Now as the concept of community gets adopted by more people the community undoubtedly attracts ignorant leeches that have no business being an advisor to anyone, on anything. You’ve met them, perhaps they have destroyed your network. You’ve received their business card, they likely didn’t have a web site or a phone number attached to them. Everything about them screams “hobbyist” yet they stand in front of you demanding your support.

Allow me to share a story of a gentleman I nearly punched at a TS2 event. This person has been involved in a migration which caused his clients network to be downed for a few days. JJ had pulled me aside to assist the gentleman with the question he had on SBS Migration. JJ recently wrapped a TS2 Wednesday on the Web with Jeff Middleton who is the author or SBS Swing Migration toolkit, an excellent and comprehensive resource on SBS migration. I had just finished an interview with Jeff for the SBS Show where he shared the future of his company, the changes to the Swing Migration pricing and structure and nearly all the details. This gentleman that was standing before me had a simple question:

“Can you please tell me more about the Swing Migration, I have a server that I need to move immediately and I don’t know how to proceed. Can you explain how Swing Migration works?”

Ok, innocent question. Did you watch JJ’s webcast? No. Ok, did you listen to the SBS Show? No. Ok, did you look at SBSMigration.com? Skimmed it. Ok, please go review those resources and I’ll be glad to point you in the right direction afterwards.

“Well, no, I can’t do that I have too much to do. I don’t have the time for that. Can you just tell me how it works, what the steps are?”

At this point I walked away from this gentleman as I was quite ready to punch his lights out. How ignorant could you possibly be that you refuse to do the basic research and training for the job you quite obviously told someone you could do?

Believe it or not, this is the overall competence level of majority of the small business consultants out there. Do not believe me? Please go to a TS2 event and listen to the questions they ask. They have some of the brightest PSS engineers that also happen to have a personality representing their interests to Microsoft and the best questions they can muster are “Why isn’t xxx in the Action Pack?” I am one of the biggest TS2 supporters out there and I constantly call the real partners in the Microsoft community to come out, network, learn, share. Do they? No. Why not? Because they get disheartened to see what their competition is up to. Yes, the guy stealing the swag at a TechNet/TS2 event. Yes, the guy with no business card. Yes, the guy that let his customer “try out” software from his Action Pack. You know them well, they are out there.

 

The SPF

Last month I had a prolonged public discussion with David Schrag regarding the SPF – Single Point of Failure small business consultant. The sole proprietor, unincorporated, poorly trained individual that seems to be the jack of all trades, master of none. You’ve met him. This man can design a mainframe and also does web development on the site. Yes, he has 50 years of corporate IT experience, has been in business for 20 years, looks about 40 and has never managed to grow his business past the sole proprietor status. SPF looks for every opportunity, pretends he can do anything from CAD training to network engineering but somehow doesn’t own a business card. He is an expert at VoIP and Cisco high end routers yet doesn’t know what show config does or where the DNS records are edited. You know him well, your friendly neighborhood computer guy that in any corporate environment wouldn’t even be allowed to clean the dust off the power supply. 

These people are dangerous. Failure is the name of their game and they are the number one, largest, most resilient part of small business IT. These are the men and women that destroy one small business after another, the ones that use Windows XP as a server, that tell businesses they don’t need a server, that host business web sites on dyndns, that have never in their life even bothered to read a book. The “enthusiast” – and now they have become the managed services provider.

Yes, this sole proprietor shop that cannot give anybody a lead, that will not share his customer with anyone that might be able to help, that will not reveal a single thing about what they do or share anything they may know – these guys and gals are out there writing managed services agreements. They are out there, without backup, without failover, without someone to lend them a hand… they are approaching small business and telling them that for a flat monthly fee they will be their tech support department. Yes, anything goes wrong, we’ll be there! Oh really dear SPF, will you? What happens if something happens to another client of yours, whom you’ve promised one hour on-site response time, while you are working on my problem? Do you leave me in the water while you go save them? How do you prioritize? How and when do you train? How and when do you take vacations?

In my years in the IT business I have met many consultants. Only a tiny fraction of them is still in business as a sole proprietor. Those that survived are the ones that specialized heavily and networked every step of the way to provide a comprehensive solution to small business. Majority of them that got very successful at what they do formed partnerships, even bigger companies on their reputation and excellence. I am one of those people.

The rest. They died. You see, an SPF is a leach. SPF has a few clients, perhaps one well established one that keeps them around. SPF’s skills are not high enough to be attractive enough to any employer, but they are a means to solving the most basic of IT problems, the company representative when it comes to research and overall less of a burden for a small company than an IT person might be. They stay in business as long as their sugar daddy business stays around after which they find a new role selling real estate, insurance, mortgages or whatever else requires little education.

 

The Problem

The single biggest thing Susan Bradley has against me is that I consider IT a profession. What comes with being a professional? Education. Experience. Certification. Reputation. Ethics. I see these lacking more and more as the “community” grows and I feel that we as community leaders are committing an immoral task by empowering incompetent people to do more complex tasks instead of handing them a loaded gun with suicide instructions.

Last year I had an “IT Professional” from Orlando ask a very basic DHCP question. This happened on a public Orlando IT Pro mailing list where a gentleman asked about the DHCP server in his Virtual PC shutting down. Before I got a chance to respond another “IT Professional” responded leading the first guy in the completely wrong direction. This is the practice that my friend Pablo Averbuj calls “blind leading the blind.” I scrapped the presentation for the next months meeting and instead held a presentation with JJ on the basics of networking and Windows Domain Controllers. We went through routing, IP assignments, domain controllers, FSMO, trusts, authentication, troubleshooting mail, network, authentication and related problems. After we were done with the presentation I told my group that they need to look around and seek a mentor. If you are just getting started the learning curve is sharp enough. There are too many books, too many webcasts, too many podcasts, too many blogs, too many white papers, too many classes, too many e-training opportunities – get someone you can learn from to tell you where you should focus on. A guidance counselor on your way to IT Professional excellence.  

For the most part, I have never seen most of the people in that meeting again. It was one of our most densely attended meetings, New Horizons offered everyone in the group a two week course at over 75% off and there was just no excuse anyone could have come up with. 

At that point I decided that SPFs are no longer going to benefit from my hard work and that I will not allow my community to become what TS2 has become. I will not allow the people that can’t even understand the basic concepts of computers and networking to be on the same list as the true professionals that are in this business to help small business. In order to participate in the group discussions you must have at least one server you are responsible for. If you have 0 servers you are added to a newsletter list. No beta access for you. No Microsoft incentives for you. No opportunity to ask stupid questions that when pasted into Google produce a solution on the first result. You have to be a serious IT Professional in order to be a part of the IT Professional Association. It’s much like the Bar Association, except for IT Professionals.

I today manage two lists. One for general information on events and happenings around Central Florida. The other is for true IT Professionals. Everyone is welcome to the meetings, everyone is welcome to voice a problem. However, as far as I am concerned, if you are detrimental to the business you are supposed to be consulting I am not empowering you. Susan has on many occasions tried to guilt me into offering help to those that don’t deserve it. She fails to understand the SPF concept. Susan is an accountant, she is a DIY(er) – Do it Yourself(er) because she had to deal with incompetent IT support in the past. She sees my limitation of the Association membership as a personal wall that would never have allowed her to become who she is today.

To an extent she is right. But the day that Susan Bradley hires me as a Jr. Tax Specialist is the day I back away from my morals and start helping liars and thieves. SPFs are rude, they are dishonest, they are immoral and they expect you to do their job for them. They want every aspect of their job explained to them, every problem resolved, every issue handled and they expect you to document it for them. They refuse to do any troubleshooting, post intelligent questions, train, educate, etc.

 

Responsibility 

I am not the smartest person in the world. I, however, am fairly successful. Why? I always looked up to the people that are doing better than I am and always strived to learn more and do better. Recently I spoke to a dear friend, Beatrice, who put me at somewhat of an ease about not being the community punching board for SPFs:

“Was any of it easy? Was getting your MCSE easy? How many books did you read? How much troubleshooting, experimenting, testing and banging your head against the wall have you had to do to get to this level? How much have you sacrificed for your expertise…. And people want you to give that away for free? Yeah, right.”

This community has a responsibility to its participants. Who assumes it? Generally, no one. I recently brought up this topic, “Is the SBS community a good substitute for training?”. Here is that conversation:

Vlad Mazek says:

so basically SBS Community = substitute for reading documentation

Jaded MVP Alter Ego:

How is the world a better place if you spend your free time empowering people who are not qualified to do their job?  Who wins?

Vlad Mazek says:

the customer wins according to Susan. If you could have a do-over, would you wait for a community to help guide you through the job or would you hit the books, get certified, get trained?

Jaded MVP Alter Ego:

That's exactly what I did.  Dude – 3 months in to my MCSE, I knew more than 75% of IT Pros out there because it was still fresh in my mind.  It has been a long time since anything other than self-study was more efficient for me (and I'm guessing you're similar).  A lot of people aren't like that, though.  My thing is that I'm not interested in talking to the lower 2/3s.  It's not the best use of my time.

Jaded MVP Alter Ego:

yeah, I'm not a big fan of that.  You empower joe-bob to install server #1.   he does ok on day one.  day 2 something breaks.  are you now morally obligated to help him out?

Jaded MVP Alter Ego:

Honestly, I don't know how they'll answer that one.  Given the number of newsgroup threads that end with "that didn't work, now what?", I'd say that the sense of responsibility ends rather quickly.

That last line sums up the problem very quickly. Is the community empowering the wrong people and to what extent should it be allowed?

 

Conclusion 

And there you have it. SBS community is one of the biggest and most dynamic on earth. But as this community grows and reaches people that may not understand the community spirit, at what point should we stop handing out the fish and start handing out fishing poles? Everyone in small business IT consulting is concerned about the Geek Squad and Best Buy yet nobody seems to have the SPFs on the radar. I feel it is immoral and a form of academic cheating to do other persons job for them. I am not saying we should build a huge border around the community and make only the most athletic of idiots that jump over it participate – but I am saying that as we grow we resist the temptation to act as an evangelical church that is out to save everyone and force them to recognize SBS as their personal savior. Not everyone is cut out for IT. This is not an easy job, this is not a static job where skills don’t need to be worked on for years. This is a profession. So to everyone that doesn’t treat it that way, let me be the first to give you the following words of advice from Simon Cowel: 

“You are just awful. You should give this up now.”

Welcome e-bitz to the podcasting family

Podcast
2 Comments

Untitled document

Please welcome Susan Bradley to our SBS podcasting family. She has published her first podcast so give it a listen. It just might give you an idea about why your WSUS is downloading a 6.5 GB file overnight if you selected SQL 2005 & Service Packs to be automatically downloaded.

 http://www.acidplanet.com/artist.asp?podcasts=509847&t=1065

 RSS: http://www.acidplanet.com/podcasts/rss.asp?id=165    

Add it to your streamer.

Now, I just know the question thats going to come up – are you afraid she is going to steal your thunder? If I had a penny for every time I heard "Oh, I was going to do SBS Show but you beat me to it" I would be a much richer man. I know this is going to just shock you, but… we don't make any money on the SBS Show. Really, $0. As a matter of fact, yours truly has spent a ton of money, time and effort on the SBS Show to give people an opportunity to share their story. I absolutely love it when yet another person takes the time and effort to contribute their expertise and skill. It is all about sharing information, helping someone, somewhere. It is a good feeling. We love Eriq. We love the Inside SBS Guys. We love Exchange screencasts. I looooove Amanda Congdon. Sharing information is a good thing. Please do it. The satisfaction that comes out of helping strangers is amazing, getting their email after you've saved their day is even better. So get to it. No, we are not afraid of you. 

What are you gonna do, take away the hordes of attractive women that are throwing themselves at me because of the SBS Show?  

Tim goes Gem Digging

Events
3 Comments

Untitled document

My PR consultant, Tim Barrett, is doing a TS2 Wednesday's on the Web seminar today at 3 PM EST. If you have the moment to join us today you'll find out about the more advanced features of SBS. I'll be there!

http://www.msreadiness.com/WS_abstract.asp?eid=15004161

Ron will be joined by Tim Barrett (Microsoft Small Business Specialist and leader of the Kentucky Small Business Server User Group) to look at extending SBS beyond the wizards with value-ads such as the OWA Administration tool, Monitoring SBS with MOM Workgroup Edition, and demonstrating how to easily document your SBS network configuration with OneNote. We’ll take a look at some SBS best practices, tips & tricks, and the webcast Q&A will be manned with SBS-MVPs & SBS User Group Leaders. If you're an SBS-er, you won't want to miss this!

Crazy Ligmans Summer Savings Sale

Deals
6 Comments

Untitled document

Now this has to be the funniest blog post I've read in quite a while. I like the numbers breakdown, too. Here is my take on it:

Get your unbeatable bottom price on SBS, SBE Office, XP Upgrade deals this weekend at Crazy Ligman's software sale. All business platform SKU's must go! We got a huge shipment from the factory and ALL must go before June 30th. $922? Forget about it. $800? No way! Just $797 gets you in a seat of a brand new SBS CAL, XP Pro Upgrade Cal and SBE Office. $797, fully loaded! You'll be cruising your office documents – anywhere. Don't have a PocketPC? We'll throw that in too! Everything but the kitchen sink! Come and see us at the corner of 1 Microsoft Way at Crazy Ligmans where our volume means savings for you! We finance eeeveryone! (guarantee not a guarantee, must be a small business and qualify for the financing. all tax, tags and financing charges excluded)

Now all joke aside this is a pretty good deal. First off, you can stack all the discounts described in the blog, standardize on a platform for the next 3 years, get a free upgrade to R2 when it comes out and probably get Vista in there. They'll even hook you up with a phone and financing. If you've got a business thats been avoiding an upgrade they will not see this good of a deal anytime soon. Plus the time is just ripe to get in before the Vista upgrade cycle. If they don't sign the dotted line for this you likely just have a lost hope on your client list, cut them loose and go win some business with this one. 

Office 2007 Beta 2 Available (Weasel Edition)

Beta
Comments Off on Office 2007 Beta 2 Available (Weasel Edition)

Untitled document

Without going through connect.microsoft.com as well. Follow this link to either download a copy or have them mail you a few disks. Now, watch out because they are really being weasels about this:

In software development, a "beta release" of a product is one that is still in development but is published for testing purposes. Evaluate the next release of Microsoft Office products for testing and planning purposes with 2007 Microsoft Office system Beta 2. The beta release contains all the functionality of the regular release, but is not the final product."

Oh god I hate PR weasels. What they fail to mention in the above text is that Beta, Microsoft for "broken", is a mirracle of software development when software actually works. Should you be stupid enough to test their hypothesis and destroy your system Microsoft will send you to a newsgroup where you will have to rely on kindness of strangers to get yourself back to normal. Or perhaps it will work flawlessly the first time. Thats the risk, feel free to gamble if you wish.

Now that I've covered this for end users, if you're an IT Pro I'm sure you're already brewing that image of XP to try this on. The interface, interaction and behavior of 2007 is drastically different and in two simple words – kicks ass. Downloading as we speak!

Underestimating Human Complexity

Programming, Shockey Monkey
5 Comments

Untitled document

For the past month I have been embarking on a task of replacing myself with a shell script. This isn't as complicated as it seems, turns out I'm very predictable in terms of how I manage the business. The problem is that in the world where there are only 24 hours but I need to work 30 hours there is a need to hand off certain responsibilties to another monkey and hopefully with minimal training be able to delegate some of the responsibility without affecting the result (network up).

So about a month ago I set out to code the NOC management system for Own Web Now and man, did I underestimate just how much stuff happens transparently without really thinking or documenting it. For example, last night I spent nearly two hours writing the function to calculate ticket age. The function itself took about 10 minutes, the debug/test/what if took just shy of two hours. Why? Well, time zones. Leap years. SLA plans.

Here is the context. No client should be knocked out for more than 0.1% of the day —  If the monitoring system notices a downed state it opens a ticket. So far so good. Now, the system calculates the time between the initial outage and service restore and if that period is less than 0.1% we're delivering on our SLA. Now let's say the system goes down at 11:58 PM but comes back at 12:04 AM. How is the outage logged? Uhh, it was just down Bob! But, the panel that shows the client flawless performance throughout the week will now have two orange fields instead of just one red one if we dropped the ball.

That makes me look bad even though they were only down for 6 minutes – maybe they were not even down, maybe it was just timing out on my monitor because we only do ping checks for this client. Hrm. Ok. Now, let me widen the range. If the time crosses two calendar days but we meet the SLA on the total outage I only count that as one down, not two separate incidents (as it appears in the overview panel). Ok, now calculate which day had a longer outage and stick the report into that calendar day. Woo! Oh, the field of when the outage happened? Ok, 11:58 PM. But wait, the other function calculates the time by subtracting the resolution time from the open time. Outage interval: -23:54? Ok, throw in another consistancy check.

So as a monkey I really only had the server out for 6 minutes in my head. On a logical evaluation and reporting mechanism I have 200ish lines of code to explain that to the computer. So who is smarter, the monkey or the computer? And people wonder why I keep on calling myself and my staff the monkey force. There was literally a moment last night / this morning where I felt like the gorilla at the opening of 2001 Space Odyssey, thank god there were no bones around me or that monolith would have been beaten.  🙂

But here is some value-add for you to thank you for reading all this text: Here is a blog post off digg.com where someone made cheatsheets for web development. Now I've never been accused of being a great developer so this is a total life saver for me. I honeslty do not spend enough time in JavaScript to justify learning all the parameters that XMLHttpRequest object takes. Digg it!