exterminator
September 16th, 2005, 05:39 AM
I was wondering about what to include and what not to include in a whitepaper that I need to put up in sometime now. I am not even sure about the topic that I would be choosing for it leave alone the content. However, I would be willing to keep this related to some C++ programming language technicalities. And hence I needed some suggestions (as many as you can) regarding a few things:
1. Some good topics on which this could be started.
2. The length to which that content should be expanded.
3. Is it necessary to provide a solution or an alternative if I talk about some bad programming practice or can I just outline the issues that a developer can face and then make them aware about the various scenario's with sample code and output?
4. Anything else that you may feel like providing as an input.
I don't have experience with this (will be doing this for the first time). I did some searching for sample papers but I only got ones with very broad subject line. Like security, data management and so on. Can I not go ahead with something into the detail of a language as such? Any help (references) would be very much appreciated. Thanks and regards.
1. Some good topics on which this could be started.
2. The length to which that content should be expanded.
3. Is it necessary to provide a solution or an alternative if I talk about some bad programming practice or can I just outline the issues that a developer can face and then make them aware about the various scenario's with sample code and output?
4. Anything else that you may feel like providing as an input.
I don't have experience with this (will be doing this for the first time). I did some searching for sample papers but I only got ones with very broad subject line. Like security, data management and so on. Can I not go ahead with something into the detail of a language as such? Any help (references) would be very much appreciated. Thanks and regards.