Master theses

For open topics, see the group's list and look for my name or the name of one of my current Ph.D. students or postdocs.

Necessary courses
I don't have a strict requirement for courses - it all depends on the thesis topic. Many of my topics involve changing something in the OS kernel, for example Linux. This means that, for such topics, you have to be good with C and operating system programming, and here INF4151 helps - but if you didn't take this course yet convince me of being a kernel hacker, that's okay too :-)
In general, I think that INF5072 is a good fit for many of the things I focus on, and maybe also INF5050, but that one is surely not a requirement for most of my topics.

About writing

First of all, please proofread your text AND use a spell-checker (in case you don't know one for LaTeX, I do: aspell). If you give me text full of typos or sloppiness mistakes, I take it as a sign that you don't care about wasting my time (because it takes me MUCH longer to correct), which is really impolite. I would have never thought of giving a text to my master or Ph.D. advisor without proofreading it myself first, AND running it through a spellchecker. If you don't care about being polite, perhaps you care about getting your text back soon - I really am faster when there are fewer minor mistakes to correct.

About English: if you're not super-confident regarding usage of articles (true for most students of Asian origin whom I met), please Google for "article usage english" and spend 10-15 minutes reading. If you're Norwegian, please make sure to correctly apply plural to verbs ("The cats is running away" is wrong. It should be "The cats are running away"). I also suggest to read these Comics - they either help you or make you laugh, or both, so it's always worth it :-) At least the "i.e." and semicolon problems are pretty common. Generally, spending some time with Google to try to improve your English should be seen as a constructive: if your English is better after submitting your master thesis, isn't that a good thing?

About your bibtex bibliography: Proper names in reference titles need protecting from Bibtex. Use {curly braces} around them, or Bibtex will map them all to lower case. Make sure there is enough info for a reader to find the document: authors plus title isn't enough. Don't blindly copy and paste ACM bibtex entries without fixing them: they list "New York, NY" as the address field, which means that all ACM conferences look like they took place there; just delete this, or - better - replace it with where the conference took place, which is much more helpful to the reader than the publisher's address. Please actually read the bibliography before submitting your thesis!

Finally, also in the interest of saving time for both me AND you, try to avoid giving me text that I have already proofread for another round of reading. Mark it somehow. Here, latexdiff helps a lot.


Last update: 15. March 2017
Back to Michael's page