Thursday, July 29, 2010
Lotus Notes – Shortcut Key to access Lotus Notes Databases:
http://www.keyxl.com/aaa221f/167/IBM-Lotus-Notes-email-software-keyboard-shortcuts.htm
Wednesday, July 28, 2010
Why we need Documentation:
Documentation always seems to be the most difficult part of the project to complete. There is little glamour and no major kudos in doing documentation. That does not diminish its importance, however. There are at least five reasons why the project manager and team need to do documentation on the project:
Reference for future changes in deliverables. Even though the project work is complete, there may be further changes that warrant follow-up projects. By using the deliverables, the customer may identify improvement opportunities, features to be added, and functions to be modified. The documentation of the project just completed is the foundation for the follow-up projects.
Historical record for estimating duration and cost on future projects, activities, and tasks. Completed projects are a great source of information for future projects, but only if data and other documentation from them is archived so that it can be retrieved and used. Estimated and actual duration and cost for each activity on completed projects are particularly valuable for estimating these variables on future projects.
Training resource for new project managers. History is a great teacher, and nowhere is that more significant than on completed projects. Such items as how the WBS architecture was determined, how change requests were analyzed and decisions reached, problem identification, analysis and resolution situations, and a variety of other experiences are invaluable lessons for the newly appointed project manager.
Input for further training and development of the project team. As a reference, project documentation can help the project team deal with situations that arise in the current project. How a similar problem or change request was handled in the past is an excellent example.
Input for performance evaluation by the functional managers of the project team members. In many organizations, project documentation can be used as input to the performance evaluations of the project manager and team members.
Reference for future changes in deliverables. Even though the project work is complete, there may be further changes that warrant follow-up projects. By using the deliverables, the customer may identify improvement opportunities, features to be added, and functions to be modified. The documentation of the project just completed is the foundation for the follow-up projects.
Historical record for estimating duration and cost on future projects, activities, and tasks. Completed projects are a great source of information for future projects, but only if data and other documentation from them is archived so that it can be retrieved and used. Estimated and actual duration and cost for each activity on completed projects are particularly valuable for estimating these variables on future projects.
Training resource for new project managers. History is a great teacher, and nowhere is that more significant than on completed projects. Such items as how the WBS architecture was determined, how change requests were analyzed and decisions reached, problem identification, analysis and resolution situations, and a variety of other experiences are invaluable lessons for the newly appointed project manager.
Input for further training and development of the project team. As a reference, project documentation can help the project team deal with situations that arise in the current project. How a similar problem or change request was handled in the past is an excellent example.
Input for performance evaluation by the functional managers of the project team members. In many organizations, project documentation can be used as input to the performance evaluations of the project manager and team members.
Resize Power point photos in Same Location:
How many times have you resized a photo on a PowerPoint slide and then must take the extra step of moving it back to the correct location? This shortcut will allow you to resize your photo and keep it still in the same place on the slide.
Resize One Photo on the Slide
1. Click on the photo to select it.
2. Hold the Ctrl key while you drag the corner selection handle to resize it to the desired size. Notice the outline of the new size while you drag the mouse.
• Note - Dragging a corner selection handle of the photo retains the proportions of the photo.
Release the mouse and the Ctrl key and the new resized photo will be centered in the same location.
Resize Two or More Photos on the Slide
1. Click the first photo to select it.
2. Hold the Shift key while you click on the remaining photos to resize. (Holding the Shift key allows you to select more than one photo on the slide.)
3. When all photos are selected, release the mouse and the Shift key.
4. Now hold the Ctrl key while you drag a corner selection handle of any one of the photos (it does not matter which photo you choose). All photos will be resized and remain centered in their original locations.
Resize One Photo on the Slide
1. Click on the photo to select it.
2. Hold the Ctrl key while you drag the corner selection handle to resize it to the desired size. Notice the outline of the new size while you drag the mouse.
• Note - Dragging a corner selection handle of the photo retains the proportions of the photo.
Release the mouse and the Ctrl key and the new resized photo will be centered in the same location.
Resize Two or More Photos on the Slide
1. Click the first photo to select it.
2. Hold the Shift key while you click on the remaining photos to resize. (Holding the Shift key allows you to select more than one photo on the slide.)
3. When all photos are selected, release the mouse and the Shift key.
4. Now hold the Ctrl key while you drag a corner selection handle of any one of the photos (it does not matter which photo you choose). All photos will be resized and remain centered in their original locations.
Monday, July 26, 2010
Test Harness:
A test harness is a small program specially written to test a particular subroutine or module. It feeds known data to the module being tested, and displays the results. It often has a Graphic User Interface, so that you can make up test data and pump it into the module being tested, but it can also have test data hard coded or stored in external files.
Frequently, a test harness will create a log file (a simple text file), so that there is a permanent record of what has been tested and what the results were. More complex test harnesses will save that data in a database for later analysis.
Frequently, a test harness will create a log file (a simple text file), so that there is a permanent record of what has been tested and what the results were. More complex test harnesses will save that data in a database for later analysis.
Sunday, July 25, 2010
Apache Subversion:
In software development, Apache Subversion (formerly called Subversion, command name svn) is a revision control system founded and sponsored in 2000 by CollabNet Inc. Developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly-compatible successor to the widely used Concurrent Versions System (CVS).
Features:
• Commits as true atomic operations (interrupted commit operations would otherwise cause repository inconsistency or corruption).
• Renamed/copied/moved/removed files retain full revision history.
• The system maintains versioning for directories, renames, and file metadata (but not for timestamps). Users can move and/or copy entire directory-trees very quickly, while retaining full revision history.
• Versioning of symbolic links.
• Native support for binary files, with space-efficient binary-diff storage.
• Apache HTTP Server as network server, WebDAV/Delta-V for protocol. There is also an independent server process called svnserve that uses a custom protocol over TCP/IP.
• Branching and tagging as cheap operations, independent of file size (though Subversion itself does not distinguish between a tag, a branch, and a directory)
• Natively client–server, layered library design.
• Client/server protocol sends diffs in both directions.
• Costs proportional to change size, not to data size.
• Parsable output, including XML log output.
• Open source licensed — Apache License in the projected 1.7 release; prior versions use a derivative of the Apache Software License, v1.1
• Internationalized program messages.
• File locking for unmergeable files ("reserved checkouts").
• Path-based authorization.
• Language bindings for C#, PHP, Python, Perl, and Java.
• Full MIME support - users can view or change the MIME type of each file, with the software knowing which MIME types can have their differences from previous versions shown.
Features:
• Commits as true atomic operations (interrupted commit operations would otherwise cause repository inconsistency or corruption).
• Renamed/copied/moved/removed files retain full revision history.
• The system maintains versioning for directories, renames, and file metadata (but not for timestamps). Users can move and/or copy entire directory-trees very quickly, while retaining full revision history.
• Versioning of symbolic links.
• Native support for binary files, with space-efficient binary-diff storage.
• Apache HTTP Server as network server, WebDAV/Delta-V for protocol. There is also an independent server process called svnserve that uses a custom protocol over TCP/IP.
• Branching and tagging as cheap operations, independent of file size (though Subversion itself does not distinguish between a tag, a branch, and a directory)
• Natively client–server, layered library design.
• Client/server protocol sends diffs in both directions.
• Costs proportional to change size, not to data size.
• Parsable output, including XML log output.
• Open source licensed — Apache License in the projected 1.7 release; prior versions use a derivative of the Apache Software License, v1.1
• Internationalized program messages.
• File locking for unmergeable files ("reserved checkouts").
• Path-based authorization.
• Language bindings for C#, PHP, Python, Perl, and Java.
• Full MIME support - users can view or change the MIME type of each file, with the software knowing which MIME types can have their differences from previous versions shown.
Thursday, July 22, 2010
Paste as CSV:
To prevent copied numbers from being pasted as text, you may be able to paste the data as CSV.
1. Copy the data in the other program
2. Switch to Excel
3. Select the cell where the paste will start
4. Choose Edit>Paste Special
5. Select CSV, click OK
1. Copy the data in the other program
2. Switch to Excel
3. Select the cell where the paste will start
4. Choose Edit>Paste Special
5. Select CSV, click OK
Wednesday, July 21, 2010
How to find perfect programmers for the Specific problem:
Certainly, it is better to find the programmers with the best qualities. But these geeks are expensive, often unavailable or will be bored with your problem.
Therefore,
• Understand the problem before hiring. Assess the required level for each quality. Prepare questions and even tests.
• Build a perfect team with not necessary perfect programmers. Just ensure that a sum of qualities of team members matches required levels. Probably only cooperation is very important quality for every team member.
• Create environment that enables most effective use and growth of these top qualities. Use right leadership style. Make programmers happy.
People with good core qualities will pick up the best approaches including writing unit tests and refactoring; learn design patterns and what is most important – deliver great and useful software.
Perfect programmers are not born, they just work on the right for the problems.
Therefore,
• Understand the problem before hiring. Assess the required level for each quality. Prepare questions and even tests.
• Build a perfect team with not necessary perfect programmers. Just ensure that a sum of qualities of team members matches required levels. Probably only cooperation is very important quality for every team member.
• Create environment that enables most effective use and growth of these top qualities. Use right leadership style. Make programmers happy.
People with good core qualities will pick up the best approaches including writing unit tests and refactoring; learn design patterns and what is most important – deliver great and useful software.
Perfect programmers are not born, they just work on the right for the problems.
Subscribe to:
Posts (Atom)