Hello all,
Since some time I've been investigating more time into profiling things better, really think about how to do a thing and why. Now I'm going to start a new project, where I will be writing a report about.
The report will be about anything what I wrote in the project, why, and I'll be investigating some things and do particular research about them. I've seen some reports, such as game programming in Haskell using FRP. However, after reading several reports they all seem to be build different.
I have a few questions about writing a report:
1] What are the things I really should include, and what are the things I really shouldn't include?
2] Is it useful to include graphs about different methods/approaches to a several problem, where you only included one into your project, to show WHY you didn't include the other methods. Or should I just explain the method/approach used into the project.
3] Should I only be writing the report after I've completed the project, or should I also write pages about what I expect, how I'm going to build the software?
Thanks,
William van Doorn
