Network/Unplugged aims to provide a wide range of solutions to its users for file management. Outlook backup is a major issue in market today as for many, mailbox data file is single most important file. However, with its size hovering around a gigabyte, backup is not an easy task. Network/Unplugged provides a quick method to backup mailbox incrementally even when it is open. Additionally, users can use Network/Unplugged to backup and synchronize other files too. It has a set of file differencing methods and an engine sitting on top to select best differencing technique for a given file at a given time. Moreover, it is possible to maintain a different set of rules when synchronizing in a LAN environment and when synchronizing over a slower link. Besides, Network/Unplugged’s virtual network enables users to view their network offline using a caching technology. Users get same look and feel of network when disconnected along with performance of synchronization attributed to Mobiliti’s intelligent Delta Selection Process (iDESP). It is possible to use virtual network feature even when file servers are available. This feature coupled with background synchronization accelerates file access over a slower connection. Version 5.0 of Network/Unplugged builds upon this existing feature set to consolidate usage further.

And why not? It sounds a lot better than “computer programmer,” and it looks much better on one’s business card. Unfortunately, it’s often inaccurate. Engineering is, after all, application of sound technical principles to develop systems that are robust, efficient and elegant. I’ve found that a great many software engineers can develop working programs, but do little or no real engineering design.

Does this sound harsh? Perhaps, but I’ve also found it hard to deny. I’ve encountered very few software engineers, for example, who have clean, crisp and readable coding styles—an essential element of elegant software design. I’ve also encountered a preponderance of cryptically written functions, clumsy software abstractions and bizarre spaghetti code. To my dismay, I’ve discovered that even among computer science graduates, many reduce object-oriented programming to mere use of private data, public functions and object instantiations. It’s enough to break a teacher’s heart.

Now, I won’t go so far as to say that most programmers write spaghetti code. That would not be fair. However, I do think that relatively few programmers have a deep appreciation for artistry of software development. That’s not to say that they’re ignorant of such things; not at all. Rather, it’s more that engineering aspects of elegant code design are all too often neglected.