| 10 | | |
| 11 | | == Writing tips == |
| 12 | | |
| 13 | | This section is only relevant to you if one of the outcomes of your project is some kind of a written publication such as a paper, a thesis or design documentation. |
| 14 | | |
| 15 | | === Content === |
| 16 | | * If you provide some sort of HelenOS overview chapter, please do not blindly follow the pretty much outdated 0.2.0 design documentation (i.e. forget about ''pseudothreads'' and use the current terminology) and stick to the things that seem relevant to your own work (e.g. no need to provide in-depth description of the kernel architecture if your focus is on some userspace application). There is also no point in retelling the early history of the project in each thesis. |
| 17 | | * If you provide a related work chapter, consider providing comparison with similar microkernel multiserver operating systems (if applicable), i.e. the Hurd, L4 and MINIX 3. These will be very interesting and useful as you will be comparing apples with apples and not apples with elephants in case of comparing HelenOS with GNU/Linux or any other monolithic system. |
| 18 | | |
| 19 | | === Form === |
| 20 | | * Always differentiate your own words from words of someone else by providing proper citation information. Never let other people think that some ideas or words are yours whereas in reality you just saw some handy text or used some notoriously known phrase. Note that these things can happen even [http://en.wikipedia.org/wiki/Meme unintentionally]. |
| 21 | | |
| 22 | | === Planning === |
| 23 | | * Getting the thesis into a good shape (grammatically, stylistically and visually) can take as much as half of the entire time you reserved for working on the text of the thesis. People don't usually believe this advice or don't take it seriously enough, but then all of them are found to have a very eventful and exciting submission week and the end result is not as good as it might have been if more time was spent on editing the thesis. |
| 24 | | * Most of the time, there will be people willing to proof-read your thesis, so plan ahead to allow enough time for these proof-readers to do you this favour and also to incorporate their suggestions. |
| | 35 | == Writing tips == |
| | 36 | |
| | 37 | This section is only relevant to you if one of the outcomes of your project is some kind of a written publication such as a paper, a thesis or design documentation. |
| | 38 | |
| | 39 | === Content === |
| | 40 | * If you provide some sort of HelenOS overview chapter, please do not blindly follow the pretty much outdated 0.2.0 design documentation (i.e. forget about ''pseudothreads'' and use the current terminology) and stick to the things that seem relevant to your own work (e.g. no need to provide in-depth description of the kernel architecture if your focus is on some userspace application). There is also no point in retelling the early history of the project in each thesis. |
| | 41 | * If you provide a related work chapter, consider providing comparison with similar microkernel multiserver operating systems (if applicable), i.e. the Hurd, L4 and MINIX 3. These will be very interesting and useful as you will be comparing apples with apples and not apples with elephants in case of comparing HelenOS with GNU/Linux or any other monolithic system. |
| | 42 | |
| | 43 | === Form === |
| | 44 | * Always differentiate your own words from words of someone else by providing proper citation information. Never let other people think that some ideas or words are yours whereas in reality you just saw some handy text or used some notoriously known phrase. Note that these things can happen even [http://en.wikipedia.org/wiki/Meme unintentionally]. |
| | 45 | |
| | 46 | === Planning === |
| | 47 | * Getting the thesis into a good shape (grammatically, stylistically and visually) can take as much as half of the entire time you reserved for working on the text of the thesis. People don't usually believe this advice or don't take it seriously enough, but then all of them are found to have a very eventful and exciting submission week and the end result is not as good as it might have been if more time was spent on editing the thesis. |
| | 48 | * Most of the time, there will be people willing to proof-read your thesis, so plan ahead to allow enough time for these proof-readers to do you this favour and also to incorporate their suggestions. |
| | 49 | |
