Monday, February 15, 2010

The Free Lunch is Over

This is an article from Herb Sutter (A software architect at Microsoft, and chair of the ISO C++ standards committee) stating the importance Of multithreaded programming paradigm that has come up to the forefront because of changes in CPU architecture.

You can access it here

97 Things Every Programmer Should Know


Get 97 short and extremely useful tips from some of the most experienced and respected practitioners in the industry.

They encourage you to stretch yourself by learning new languages, looking at problems in new ways, following specific practices, taking responsibility for your work, and becoming as good at the entire craft of programming as you possibly can.


Contributions Appearing in the Book

  1. Act with Prudence by Seb Rose
  2. Apply Functional Programming Principles by Edward Garson
  3. Ask "What Would the User Do?" (You Are not the User) by Giles Colborne
  4. Automate Your Coding Standard by Filip van Laenen
  5. Beauty Is in Simplicity by Jørn Ølmheim
  6. Before You Refactor by Rajith Attapattu
  7. Beware the Share by Udi Dahan
  8. The Boy Scout Rule by Uncle Bob
  9. Check Your Code First before Looking to Blame Others by Allan Kelly
  10. Choose Your Tools with Care by Giovanni Asproni
  11. Code in the Language of the Domain by Dan North
  12. Code Is Design by Ryan Brush
  13. Code Layout Matters by Steve Freeman
  14. Code Reviews by Mattias Karlsson
  15. Coding with Reason by Yechiel Kimchi
  16. A Comment on Comments by Cal Evans
  17. Comment Only What the Code Cannot Say by Kevlin Henney
  18. Continuous Learning by Clint Shank
  19. Convenience Is not an -ility by Gregor Hohpe
  20. Deploy Early and Often by Steve Berczuk
  21. Distinguish Business Exceptions from Technical by Dan Bergh Johnsson
  22. Do Lots of Deliberate Practice by Jon Jagger
  23. Domain-Specific Languages by Michael Hunger
  24. Don't Be Afraid to Break Things by Mike Lewis
  25. Don't Be Cute with Your Test Data by Rod Begbie
  26. Don't Ignore that Error! by Pete Goodliffe
  27. Don't Just Learn the Language, Understand its Culture by Anders Norås
  28. Don't Nail Your Program into the Upright Position by Verity Stob
  29. Don't Rely on "Magic Happens Here" by AlanGriffiths
  30. Don't Repeat Yourself by Steve Smith
  31. Don't Touch that Code! by Cal Evans
  32. Encapsulate Behavior, not Just State by Einar Landre
  33. Floating-point Numbers Aren't Real by Chuck Allison
  34. Fulfill Your Ambitions with Open Source by Richard Monson-Haefel
  35. The Golden Rule of API Design by Michael Feathers
  36. The Guru Myth by Ryan Brush
  37. Hard Work Does not Pay Off by Olve Maudal
  38. How to Use a Bug Tracker by Matt Doar
  39. Improve Code by Removing It by Pete Goodliffe
  40. Install Me by Marcus Baker
  41. Inter-Process Communication Affects Application Response Time by Randy Stafford
  42. Keep the Build Clean by Johannes Brodwall
  43. Know How to Use Command-line Tools by Carroll Robinson
  44. Know Well More than Two Programming Languages by Russel Winder
  45. Know Your IDE by Heinz Kabutz
  46. Know Your Limits by Greg Colvin
  47. Know Your Next Commit by Dan Bergh Johnsson
  48. Large Interconnected Data Belongs to a Database by Diomidis Spinellis
  49. Learn Foreign Languages by Klaus Marquardt
  50. Learn to Estimate by Giovanni Asproni
  51. Learn to Say "Hello, World" by Thomas Guest
  52. Let Your Project Speak for Itself by Daniel Lindner
  53. The Linker Is not a Magical Program by Walter Bright
  54. The Longevity of Interim Solutions by Klaus Marquardt
  55. Make Interfaces Easy to Use Correctly and Hard to Use Incorrectly by Scott Meyers
  56. Make the Invisible More Visible by Jon Jagger
  57. Message Passing Leads to Better Scalability in Parallel Systems by Russel Winder
  58. A Message to the Future by Linda Rising
  59. Missing Opportunities for Polymorphism by Kirk Pepperdine
  60. News of the Weird: Testers Are Your Friends by Burk Hufnagel
  61. One Binary by Steve Freeman
  62. Only the Code Tells the Truth by Peter Sommerlad
  63. Own (and Refactor) the Build by Steve Berczuk
  64. Pair Program and Feel the Flow by Gudny Hauknes, Ann Katrin Gagnat, and Kari Røssland
  65. Prefer Domain-Specific Types to Primitive Types by Einar Landre
  66. Prevent Errors by Giles Colborne
  67. The Professional Programmer by Uncle Bob
  68. Put Everything Under Version Control by Diomidis Spinellis
  69. Put the Mouse Down and Step Away from the Keyboard by Burk Hufnagel
  70. Read Code by Karianne Berg
  71. Read the Humanities by Keith Braithwaite
  72. Reinvent the Wheel Often by Jason P Sage
  73. Resist the Temptation of the Singleton Pattern by Sam Saariste
  74. The Road to Performance Is Littered with Dirty Code Bombs by Kirk Pepperdine
  75. Simplicity Comes from Reduction by Paul W. Homer
  76. The Single Responsibility Principle by Uncle Bob
  77. Start from Yes by Alex Miller
  78. Step Back and Automate, Automate, Automate by Cay Horstmann
  79. Take Advantage of Code Analysis Tools by Sarah Mount
  80. Test for Required Behavior, not Incidental Behavior by Kevlin Henney
  81. Test Precisely and Concretely by Kevlin Henney
  82. Test While You Sleep (and over Weekends) by Rajith Attapattu
  83. Testing Is the Engineering Rigor of Software Development by Neal Ford
  84. Thinking in States by Niclas Nilsson
  85. Two Heads Are Often Better than One by Adrian Wible
  86. Two Wrongs Can Make a Right (and Are Difficult to Fix) by Allan Kelly
  87. Ubuntu Coding for Your Friends by Aslam Khan
  88. The Unix Tools Are Your Friends by Diomidis Spinellis
  89. Use the Right Algorithm and Data Structure by JC van Winkel
  90. Verbose Logging Will Disturb Your Sleep by Johannes Brodwall
  91. WET Dilutes Performance Bottlenecks by Kirk Pepperdine
  92. When Programmers and Testers Collaborate by Janet Gregory
  93. Write Code as If You Had to Support It for the Rest of Your Life by Yuriy Zubarev
  94. Write Small Functions Using Examples by Keith Braithwaite
  95. Write Tests for People by Gerard Meszaros
  96. You Gotta Care about the Code by Pete Goodliffe
  97. Your Customers Do not Mean What They Say by Nate Jackson

Here is the link to the home page:




Thursday, February 04, 2010

Alex Stepenov's Advice To Young Programmers

This is the summary of speech Given by Alex Stepenov (Principal Scientist,Adobe Systems) at Adobe India on 30 Nov 2004.


1. Study , Study and Study
Never ever think that you have acquired all or most of the knowledge which exists in the world. Almost everybody in US at age of 14 and everybody in India at age of 24 starts thinking that he has acquired all the wisdom and knowledge that he needs. This should be strictly avoided.
You should be habituated to studies…exactly in the same way as you are habituated to brushing teeth and taking bath every morning. The habit of study must become a part of your blood. And the study should be from both the areas: CS, since it is your profession, and something from non-CS…Something which does not relate to your work. This would expand your knowledge in other field too. A regular study, everyday, is extremely essential. It does not matter whether you study of 20 minutes of 2 hours,but consistency is a must.

You should always study basics and fundamentals. There is no point in going for advanced topics. When I was at the age of 24, I wanted to do PhD in program verification, though I was not able to understand anything from that. The basic reason was that my fundamental concepts were not clear. Studying Algebraic Geometry is useless if you do not understand basics in Algebra and Geometry. Also, you should always go back and re-read and re-iterate over the fundamental concepts. What is the exact definition of `fundamental’? The stuff which is around for a while and which forms basic part of the concepts can be regarded as more fundamental. Of course, everybody understands what a fundamental means.
Here are few books which I would strongly recommend that every CS professional should read and
understand:

  1. Structure and Interpretation of Computer Programs by Albenson and Sussman. I personally do not like the material present in this book and I do have some objections about it but this is the best book I have ever seen which explains all the concepts in programming in a clear and excellent way. This book is available online at “http://mitpress.mit.edu/sicp/“
  2. Introduction to Computer Architecture by Hennessy and Patterson. How many of you have shipped the programs by writing them in assembly? A very good understanding of basics of how a computer operates is what every CS professional must have. H&P Wrote two books on CA. I am talking about their first book, the introductory text for understanding basic aspects of how a computer works. Even if you feel that you know whatever is written in that book,do not stop reading. It’s good to revise basics again and again.
  3. Fundamentals of Programming by Donald Knuth The core of CS is algorithms and Data structures. Every CS professional must have the 3 volumes of Knuth’s Book on programming. It really does not matter if you take 30 years of your life to understand what Knuth has written, what is more important is that you read at least some part of that book everyday without fail.
  4. Introduction to Algorithms by Cormen, Leiserson and Rivest. This book should be read daily to keep your concepts fresh. This is the best book for fundamental concepts in algorithms.




2. Learn Professional Ethics
As a CS Professional, you are morally obliged to do a good job. What this means is that you are supposed to do your job not for your manager but for yourself. This is already told in Bhagwatgeeta : Doing duties of your life. The direct implication of this is: never ever write a bad code. You don’t need to be fastest and run after shipping dates; rather you need to write quality code. Never write junk code. Rewrite it till it is good. Thoroughly test every piece of code that you write. Do not write codes which are “sort of alright”. You might not achieve perfection, but at least your code should be of good quality.

Let me quote my own example in this context. You might have heard about STL, The Standard Template Library that ships in with C++ compilers. I wrote it 10 years ago, in 1994. While implementing one of the routines in the STL, namely the “search routine”, I was a bit lazy and instead of writing a good linear order implementation of KMP which was difficult to code, I wrote a best quadratic implementation. I knew that I could make the search faster by writing a linear-order implementation, but I was lazy and I did not do that. And, after 10 years of my writing STL, exactly the same implementation is still used inside STL and STL ships with an inefficient quadratic implementation of search routine even today!! You might ask me: why can’t you rewrite that? Well…I
cannot,because that code is no more my property!! Further, nobody today will be interested in a standalone efficient STL …people would prefer one which automatically ships out with the compiler itself.

Moral is, you should have aesthetic beauty built inside you. You should “feel” uneasy on writing bad code and should be eager to rewrite the code till it becomes upto the quality. And to the judge the quality, you need to develop sense regarding which algorithms to use under what circumstances.


3. Figure out your Goals


Always aspire doing bigger things in life.”Viewing promotion path as your career” is a completely wrong goal. If you are really interested in studying and learning new things, never ever aspire for being a manager. Managers cannot learn and study…they have no time. “Company ladder aspiration” is not what should be important for you.

You might feel that you want to do certain things which you cannot do till you become a manager. When you become a manager, you will soon realize that now you just cannot do anything!
You will have a great experience as programmers. But if you care for people and love people, you will never enjoy being a manager…most good managers are reluctant managers. If you see people as people, you cannot survive at management level.
Always aspire for professional greatness. Our profession is very beautiful because we create abstract models and implement them in reality. There is a big fun in doing that. We have a profession which allows us to do creative things and even gives nice salary for that.

The three biggest mistakes that people usually make are aiming for money,aiming for promotion and aiming for fame. The moment you get some of these, you aspire for some more…and then there is no end. I do not mean that you should not earn money, but you should understand how much money would satisfy your needs. Bill Gates might be the richest person in the world; he is certainly not the happiest. Our lives are far better than his.

Find your goal, and do best in the job that you have. Understand that what is in your pocket does not
matter…what is in your brain finally matters.Money and fame do not matter. Knowledge matters.



4. Follow your culture

I have seen the tradition that whatever junk is created in US, it rapidly spreads up in the rest of the world, and India is not an exception for this. This cultural change creates a very strong impact on everybody’s life. Habits of watching spicy Bollywood or Hollywood movies and listening to pop songs and all such stupid stuff gets very easily cultivated in people of your age…but believe me, there is nothing great in that. This all just makes you run away from your culture. And there is no wisdom in running away from your culture. Indian culture,which has great Vedas and stories like Mahabharata and Bhagwatgeeta is really great and even Donald Knuth enjoys reading that. You should understand that fundamental things in Indian culture teach you a lot and you should never forget them.




Finally, I would like to conclude by saying that it’s your life…do not waste it on stupid things…develop your tests, and start the fight.


This is the summary of speech Given by Alex Stepenov (Principal Scientist,Adobe Systems) at Adobe India on 30 Nov 2004.

Friday, March 16, 2007

Wednesday, January 03, 2007

Welcome 2007 !!!

So, 2006 ends ....
It was a great year filled with wonderful achievements for me like Becoming our departmental Organization QUASAR coordinator, the mesmerizing days of final semester, Joining in Persistent, training days, and Finally project in PSPL. Soooo wonderful !!!! I think, it was the best year so far for me.
Now, its time to look forward to 2007. I guess 2007 will also be a productive year too.

Thursday, November 16, 2006

9 November's Quarterly Party

Just after getting allocated to project , there was a quarterly party ! Moreover, the party was combined for last TWO quarters. The venue was Hotel Manas near Chandani Chowk in the outskirts of Pune . We all had a grat time there.
I was entralled by the Go Carting (Car Racing) especially. The boating, atmosphere, food was fantastic too !
Really enjoyed a lot !

Friday, September 08, 2006

First Weekly Review Meeting C++ Mini-projects

Yesterday from 3:00 pm to 5:00 pm we had First Weekly Review Meeting of C++ Mini-projects. My project partner Tushar Shirbhate started the presentation and I concluded it.

The only thing I can say here is that, our project is regarding IM(Instant Messeging) i.e. Chatting...

Many things about the project are yet to be finalised. Our Principal mentor Mr. Sheehari Marathe told us to close those issues as soon as possible.

Monday, September 04, 2006

Lage raho Munnabhai


On Sunday 3rd Sept. myself with Nilesh, Ram, Bharat, Mahesh C, Dhobale, Gajanan, Sonal) had a wonderful time watching Lage Raho Munnabhai

I thought, it was truly a fantastic movie... It had ALL the flavours : Drama, Comedy, Emotions, Morals, Patriotism...
The "Good Morrrrrrniiiiing Mumbai" from Janhavi was wonderful....
The director has really done a fantastic job. Everyone in the film justifies his role. Bringing Gandhiji in the film was incredible.

To sum up, its a MUST WATCH.... Have a good time then !

'Crocodile Hunter' Steve Irwin Killed'

When I was just browsing on the net, I read this shoking news.
Let's just have a brief look at his life :
Steve was an Australian naturalist, wildlife expert and television personality. He was best known for the television program The Crocodile Hunter, an unconventional wildlife documentary series which he hosted with his wife Terri Irwin that was broadcast worldwide. He also owned and operated the Australia Zoo at Beerwah in Queensland with friend William Rollo and his wife. He died after being stung directly in the heart by a stingray while filming a documentary segment for his daughter's show.