Last modified by Niklas Rentz on 2023/10/10 10:45
<
From version < 30.1 >
edited by cmot
on 2016/04/01 00:54
To version < 27.1 >
edited by cds
on 2015/04/08 11:19
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.cmot
1 +XWiki.cds
Content
... ... @@ -15,7 +15,7 @@
15 15  
16 16  = Interaction With Your Adviser(s) =
17 17  
18 -A good interaction with your adviser(s) is key to success. Unless you happen to have substantial work experience and to already be an expert in your field, your adviser is ahead of you in terms of experience and expertise. Take advantage of this to improve your own work.
18 +A good interaction with your adviser(s) is key to success. Unless you happen to have substantial work experience and to be already an expert in your field, your adviser is ahead of you in terms of experience and expertise. Take advantage of this to improve your own work.
19 19  
20 20  Advisers are humans. They like to help you with your thesis topic; they don't like to have to "drive" it, or to get the feeling that their advice (including the hints on this page) is ignored. You, and not your adviser, should be the one who is pushing your work, asking questions, initiating discussions, and handing over thesis/chapter drafts without having to be explicitly asked for it. In short, your adviser should be convinced that your work is on track.
21 21  
... ... @@ -92,7 +92,7 @@
92 92  
93 93  The bottom line: write clean and proper code that adheres to our coding guidelines and document it. The quality and the readability of your code and of your documentation will influence your grade.
94 94  
95 -== Reviews and Ratings ==
95 +== Reviews and Ratings[[url:http://trac.rtsys.informatik.uni-kiel.de/trac/rtsys/wiki/Hinweise_Arbeiten#ReviewsundRatings||style="text-decoration: none;" title="Link to this section" shape="rect" class="anchor"]] ==
96 96  
97 97  To make sure that code is of a certain quality, it must be run through design and code reviews. The way this works is explained [[on this page>>doc:KIELER.Review Process]]. The reviews are not only intended to improve the quality of your code, but also to give feedback to you as a programmer to help you improve.
98 98  
... ... @@ -300,10 +300,6 @@
300 300  24
301 301  )))
302 302  
303 -= RtSys Stammtisch =
304 -
305 -Every student who is going to write a thesis and hence is considered an integral part of our group is more than welcome to join our [[doc:RtSys Stammtisch]]. We will meet monthly in different restaurants in Kiel to have dinner and a good time together. Please ask your advisor or other students to invite you
306 -
307 307  = Further Links =
308 308  
309 309  * Prof. Luttenberger at the [[Communication Systems Group>>url:http://www.comsys.informatik.uni-kiel.de/||shape="rect"]] regularly offers a very good course on writing and presenting scientific work.
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -28672020
1 +10751502
URL
... ... @@ -1,1 +1,1 @@
1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/RTSYS/pages/28672020/Writing and Grading Theses
1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/RTSYS/pages/10751502/Writing and Grading Theses

Navigation

Quick Links

KIELER on GitHub
RTSYS Homepage