This presentation discusses the Clean and Green Code initiative to promote writing cleaner code. It encourages coders to rebuild their will to write beautiful, reusable code through discipline and making coding a form of recreation again. Clean code is defined as simple, well-structured, robust, efficient and passes all tests, making comments redundant. Writing clean code leads to green outcomes like tests passing with green results, high code maintainability, and lower carbon footprints from code execution and technologies used. Reasons why coders don't always write clean code are discussed. The presentation pledges that coders will take responsibility for writing clean and green code.

1. • Learning is a continuum.
• We Learn. Unlearn. Relearn.
Life=Learning

2. Clean And Green Code
Lalatendu Rath

3. The Facts of this Presentation

4. • Inspired by some green grass outside the
clean glass.
• As software professionals [coders and
henceforth], how do we and how can we
contribute?
• Clean and Green Code Initiative
Inspiration

5. Objectives
• Rebuild the lost will and power to write
beautiful code
• Inculcate a “sports culture” discipline in
coders
• Make “Code Creation” a Recreation again
• Opt to be right always.

6. Our Users

7. Our Users
• Our Users need us.
• Our Users entrust on us, their data, their
operations, their systems and their lives.
• Our Users believe that we understand
machines and machines languages better than
them.
• Our Users are our co-developers. They help us
develop better solutions, better products and
better ourselves.
• We need Our Users more.

8. Our Machines

9. Our Machines
• Our Machines/Systems Always listen to Us.
• They don’t fail Us. We fail them.
• We fail them by our inability to express
ourselves, to command them and put them
into proper use.
• Its time to feel, think and act [code/configure]
for them.

10. Our Processes/Tools

11. Our Processes/Tools
• Our Processes and Tools do NOT slow us.
• They enable Us.

12. Our Code

13. Our Code
• Code is inevitable.
• We need to “housekeep” and “reuse”.
• We would need to read code to write new
code.
• Code is the only credible documentation we
would have.
• Code will be written once and will be run
anywhere, anytime and any N of times.
• Our Code is Our Power [Our Pride].

14. Clean Code. What is Clean Code?

15. Clean Code is
• Simple[Brevity is wit but clarity is care]
• Well-indented and Well-intended
• Robust; Easy to Use And Hard to Misuse
• Runs Efficiently
• Clears all Tests
• Makes comments redundant

16. Clean Code=Green HOW?

17. Green Code
• Essentially always, clean code ends being
green.
• Test results Pass. Color is Green.
• “Alls Well” Status for PMs. Color is Green.
• Clean code is maintainable; Coders 40 hours a
week; Workstation Carbon Footprint; Green.
• Clean code executes elegantly. Overall Carbon
footprint; Green.
• BPM;RIA;SOA[SaaS]. Green Technologies.

18. We do not Write Clean Code.
Why?

19. Reasons
• Code + Commerce
• “Make it work”=“Make IT Work”
• “Not Informed/Skilled Enough”
• “Fear to Ask/Inform”
• “Cost/Price of Ownership”

20. We Want to Write Clean Code.
HOW?

21. Few Ways
• Code Smells
• Refactoring Skills And IDE Tips
• TDD and Automated Tests
• Agile Processes

22. We ,The Coders Pledge

23. We, The Coders Pledge
“We, software professionals, [coders and henceforth], know that
our users need us, invest on us and co-develop us.
Our machines listen to us and never fail us.
Our code will reach, impact, serve and outlive us.
Our processes and Our tools enable us.
We acknowledge this power and own up the responsibility and
the accountability too.
We, the coders, take the pledge that we would assure clean and
green code. ”
(C) Lalatendu Rath, “We, The Coders”2008

24. Thanks For Listening
Lalatendu Rath
lalatendurath@yahoo.com