| 1. Do you use source control? |
2. Can you make a build in one step?
3. Do you make daily builds?
4. Do you have a bug database?
5. Do you fix bugs before writing new code?
6. Do you have an up-to-date schedule?
7. Do you have a spec?
8. Do programmers have quiet working conditions?
9. Do you use the best tools money can buy?
10. Do you have testers?
11. Do new candidates write code during their interview?
12. Do you do hallway usability testing?
| 1. TAKE IT SERIOUSLY |
2. SOFT WARS - ATTACK OF THE CLONES
3. BRAINSTORM FOR IDEAS
4. COMMUNICATE YOUR IDEAS AND THOUGHTS
5. SCAVENGER HUNT
6. CHART-OUT A PROJECT PLAN
7. ASSIGN ROLES AND RESPONSIBILITIES
8. DO PARALLEL PROCESSING OF CODING AND READING
9. BE WELL INFORMED AND UPDATED
10. START EARLY AND FINISH EARLY
11. LEAVE ENOUGH TIME FOR DOCUMENTATION
12. PRESENT YOUR PRODUCT WITH PASSION
| 1. Believe Defect-Free Software is Possible |
2. Think Defect-Free Software is Important
3. Commit to Delivering Defect-Free Software
4. Design Your Code for Simplicity and Reliability
5. Trace Every Line of Code When Written
6. Review Code by Programmer Peers
7. Build Automated QA into Your Code
8. Build and Test Daily
9. Use Automated Checking Wherever Possible
| * System Analysis |
* Specification and Design
* Alpha Test
* Beta Test
* Deliver the Software
| Step 1: Analyze the code |
Step 2: Design for threads
Step 3: Code the threads
Step 4: Debug for correctness
Step 5: Tune for performance
7.12 Steps To Better Security
8.Software Development: Steps To Better Ensure Success
9.The Programmers' Stone
10.Painless Functional Specifications
- The Net's Best Programming 'Hang-Outs'
- Directory of Programming Languages from Dmoz
- What is Extreme Programming
- Single list of HOWTOs ,in Linux
- Finding the Best Programmer's Font,Good Programming Font Criteria
Bhasker V Kode