By now it is obvious that you have a large investment in-house on 64-bit. Servers, desktops, laptops, etc. But how are your apps doing? Are they still on 32-bit? If so, you are not harnessing the true prowess of your hardware. But before you start designing...

Many times, we have heard the word "process" and cringed. To a lot of us, process is simply the techie garb for red-tape. For instance, wouldn't you as a developer love to hunker down at your terminal and tap out great code? But that is not all you are expected to do. First, you must read a voluminous requirements document - depending on your organization's way of working, there may be more than one such document. Business requirements, functional specifications, UX documents, performance and security guidelines, build documents, deployment guidance, and so forth. You also need to add documentation of your own - the technical specification, data flow diagrams, various other flowcharts, class diagrams, database diagrams, unit testing guides and more. And that was just documents. Organizations also follow quality control mechanisms like code reviews, inspections, automated unit and functional testing, which are all your responsibility. [...] Not all processes lead to excellence. Even those that should, do not, unless you follow them for the right reasons, in the right spirit and with the right follow up actions....