Zen Developer

1. Bad Practices

1.1. Complex

1.2. No Unit Tests

1.3. Cowboy Coding

1.4. Vague Names

1.5. Donkey Work

2. The Secrets

2.1. Hacker / Tinkerer

2.2. 10,000 Hours

2.3. Ritual

2.4. Know an IDE very well ( Jetbrains )

2.5. Know your limitations

2.6. No Ego

2.7. Discipline

2.8. Super Top Secret - Aim to Experience Flow / Get into the zone

2.8.1. Super calm state of mind

2.8.2. Work at amazing speed

2.8.3. No bugs

2.8.4. Code with Gut instinct

2.8.5. No Distractions

2.8.6. http://venkat2.blogspot.in/2009/08/getting-into-zone.html

2.8.7. http://venkat2.blogspot.in/2010/04/flow-psychology-of-optimal-experience.html

3. Suggested Resources

3.1. Top Coder

3.2. Books

3.2.1. Refactoring

3.2.2. Coders at work

3.2.3. Java Head First

3.2.4. Pragmatic Programmer

3.3. Write SCJP

3.3.1. But not from Book bank

3.4. Sites

3.4.1. ThoughtWorks Technology Radar

3.4.2. Joel on Software

4. Primary Objective

4.1. Solves Problems

4.2. Ensure it works forever

4.3. Use Resources Wisely

5. Is Coding an Art?

6. Good Practices

6.1. Simple

6.2. Unit Tests

6.3. Refactor

6.4. Descriptive Names

6.5. Automate