Code snippets vs Components

ericwsw wrote:

All the code snippet can be simply cut and paste. Hereby you can simply keep it in anywhere you want. Personally don't recommend to keep in project format because it hard to find.

And this is my biggest displeasure to the use of code snippets - programmers simply copy and paste all over at leisure. One of the goals in your programming (practice) should be to cut down the amount of duplication and promote code/component re-use.

By the mere act of copy and pasting common code, you demonstrate the lack of design and modular factors in your thinking. Such code should (almost a must)be placed into utility classes and re-used by all in your team. Have a dedicated class library developer to maintain that project, or at least have each class assigned a "master" for proper ownership and control.

may turn the snippets into a set of useful libraries, like boost?

I agree with icelava, but developers looking for snippets still have retain the choice of what to do with the snippet...

feelite wrote:

may turn the snippets into a set of useful libraries, like boost?

In small projects, IMHO, this would be ok, but in a big proj of many developers, IMHO, this idea falls short.. I have seen it with my own eyes, somehow the snippets seem to creep into the code creating replication...