Wednesday 22 May 2013

Troubleshooting

It may come as a surprise to some, but sometimes your IT Guy does not know instantly what is wrong.

I know, it is a deep and hidden secret that we do not like to talk about, but at great risk to myself I am willing to admit it.

Sometimes we have no idea.

But no need to despair yet, we have the tools and the knowledge to find and fix the problems though.

When we start saying things like test and replicate, we are not referring to the Replicants of Blade Runner, as wonderful as that may be. Instead we are referring to the troubleshooting steps needed in order to get the error that you are getting.

As stated elsewhere, there are millions of lines of code in your software, and sometimes a new update perhaps, or a different hardware driver has unintended consequences.

In those cases we need to test and do what you did, in order to get the same result. Thus replicating your procedure and troubleshooting the problem.

Whether it is as easy as a new driver, or more involved and complex, we tend to get to the answer eventually.

You can rest with the reassurance that if we have no idea to start with, the more we do and the more time is spent looking and investigating, poking and prodding, we will get to the solution.

Sometimes you have to eliminate everything that is not wrong to get to what is.

This may not be an easy process and we know that you cannot afford downtime or slowing down, but once the answer and fix has been identified, it is usually resolved pretty quickly.

The biggest and best tools we have is experience and knowledge about how things should work, thus we can figure out why it doesn't.

All we ask for is a bit of time to allow the process and thinking to happen in order to get you back to your happy place.

Wednesday 6 February 2013

50 Million Lines of Code, Approximately


The original MS DOS 1.0, (go ask your IT Guy what it is) consisted of about 4000 lines of code, approximately 120 pages, enough for a novella.

The next big thing, Windows 95, remember that? Around 8 Million lines of code. We are already talking 242 copies of War and Peace or Lord Of The Rings here.

Windows XP started with 45 Million lines and also supported over 10 000 drivers, out of the box. That is more than double the amount of drivers supported for printers, sound and screen cards, motherboards, etc; than lines in the original MS DOS code itself.

Windows 7 that we all know and love, is guessed as containing 50 Million lines. That is more lines of code than words in the Encyclopædia Britannica.

It is not just for the love of numbers that I am boring you with this, but to illustrate a point.

The later versions of Windows all have to be backwards compatible, to a certain degree. This means that some of the bugs from Windows 95 had to be carried over to Windows 8, with more and more increasingly complex work-arounds and fixes to make sure that the new features also work.

And that code has to interact with other software as well, there is probably just as many lines in Microsoft Office now.

Imagine the effort and time needed to ensure that it all works just right, just so.

It all has to be checked and tested, then released into the wild for people to play and break with, before it ends up on your PC.

When your IT company comes and installs your Accounting software, and then tweaks and customises it further for your specific needs, we know what happens sometimes.

Sometimes the different changes and work-arounds and new ideas, just doesn't work.

The developers have to find out and trace back to what the work-around and fix for bug A is in order to get feature Z to work and get past error B.

And just when you think you have it right, there appears a ghost in the machine, where the different lines of code start to interact in other weird ways.

Because we can never be satisfied with what we have, we always want more.

But imagine doing your workload on a typewriter and having to file it all.

Sometimes the extra time waiting for the developer and IT Guy to make sure everything is right works out to a day or three saving, and isn't that worth it?

 

Thursday 15 November 2012

Saturday 6 October 2012

Apple to think about

After Steve Jobs, Does Apple Still Innovate Like It Used To? : The New Yorker - http://m.newyorker.com/online/blogs/comment/2012/10/apple-after-steve-jobs.html

How low can you go?

With a little fear, skydiver ready to leap into record books - http://pulse.me/s/dZCwC

Tuesday 2 October 2012

Apple says sorry

They were forced to apologise due to a huge number of complaints. I can't help but wonder if we would have had the same apology if he was still around.

I remember the fallout from the 'Grip of Death' saga and the users were told that they were holding the phones wrong and were then belatedly offered free covers.

Would we have seen something similar if Jobs was in charge?

Apple says sorry for iPhone maps app - IOL SciTech | IOL.co.za