Monday, December 13, 2010

Structure of a white paper

If you are planning to write a technical white paper the following high level structure may be helpful.

Parts of a paper:
  • Title (keep it short!)
  • Authors (typically listed in alphabetical order unless some one’s contribution stands out)
  • Abstract (shorter version of intro)
  • Intro (here is where you do the selling – perhaps the most important section)
    • What is the problem?
    • Why is it important? What are the applications?
    • Why are existing solutions inadequate?
    • What are our key technical contributions?
    • Highlight of experimental results
  • Related work (here you compare & differentiate with existing work, try to be comprehensive)
  • Model & Problem definition (formal statement of the problem)
  • Algo/solution for subproblem 1
  • Algo/solution for subproblem 2
  • Experimental evaluation
    • Data sets (preferably real-life)
    • Performance metrics (accuracy, execution time)
    • Algo/solutions compared
    • Experimentation platform
    • Performance graphs
  • Conclusions
    • Recap of contributions, experimental results
    • Directions for future work
  • References
  • Appendix (here’s where you put details like proofs of theorems, non-critical but useful reference material) 
Try to fill all these in 10 pages.

Sunday, December 5, 2010

We, "the players...."

Writing after a long time...on this blog.Lots of events to mention...

Visits to my teams in Singapore, Jordan. Taiwan and Sunnyvale visits.
Carol joined as our CEO
Ari , our Head of Engg left
Blake joined
PSR left
Org changes. Emerging Markets teams have moved to different teams after reorg. I am going to stay back with my VP heading the Quality Engineering for Yahoos new search strategy..mainly the vertical intent search team. I also need to lead the Locals and Listings Platform QE also. Need to set up a new team. First 90 days book again useful here. Another good news. I got promoted as Director - Quality Engineering.