/
tips-for-msc-students.html
484 lines (441 loc) · 22.7 KB
/
tips-for-msc-students.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<!-- 2017-08-25 Fri 11:29 -->
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<title>Tips for MSc students</title>
<meta name="generator" content="Org mode" />
<meta name="author" content="Martin R. Albrecht" />
<style type="text/css">
<!--/*--><![CDATA[/*><!--*/
.title { text-align: center;
margin-bottom: .2em; }
.subtitle { text-align: center;
font-size: medium;
font-weight: bold;
margin-top:0; }
.todo { font-family: monospace; color: red; }
.done { font-family: monospace; color: green; }
.priority { font-family: monospace; color: orange; }
.tag { background-color: #eee; font-family: monospace;
padding: 2px; font-size: 80%; font-weight: normal; }
.timestamp { color: #bebebe; }
.timestamp-kwd { color: #5f9ea0; }
.org-right { margin-left: auto; margin-right: 0px; text-align: right; }
.org-left { margin-left: 0px; margin-right: auto; text-align: left; }
.org-center { margin-left: auto; margin-right: auto; text-align: center; }
.underline { text-decoration: underline; }
#postamble p, #preamble p { font-size: 90%; margin: .2em; }
p.verse { margin-left: 3%; }
pre {
border: 1px solid #ccc;
box-shadow: 3px 3px 3px #eee;
padding: 8pt;
font-family: monospace;
overflow: auto;
margin: 1.2em;
}
pre.src {
position: relative;
overflow: visible;
padding-top: 1.2em;
}
pre.src:before {
display: none;
position: absolute;
background-color: white;
top: -10px;
right: 10px;
padding: 3px;
border: 1px solid black;
}
pre.src:hover:before { display: inline;}
/* Languages per Org manual */
pre.src-asymptote:before { content: 'Asymptote'; }
pre.src-awk:before { content: 'Awk'; }
pre.src-C:before { content: 'C'; }
/* pre.src-C++ doesn't work in CSS */
pre.src-clojure:before { content: 'Clojure'; }
pre.src-css:before { content: 'CSS'; }
pre.src-D:before { content: 'D'; }
pre.src-ditaa:before { content: 'ditaa'; }
pre.src-dot:before { content: 'Graphviz'; }
pre.src-calc:before { content: 'Emacs Calc'; }
pre.src-emacs-lisp:before { content: 'Emacs Lisp'; }
pre.src-fortran:before { content: 'Fortran'; }
pre.src-gnuplot:before { content: 'gnuplot'; }
pre.src-haskell:before { content: 'Haskell'; }
pre.src-java:before { content: 'Java'; }
pre.src-js:before { content: 'Javascript'; }
pre.src-latex:before { content: 'LaTeX'; }
pre.src-ledger:before { content: 'Ledger'; }
pre.src-lisp:before { content: 'Lisp'; }
pre.src-lilypond:before { content: 'Lilypond'; }
pre.src-lua:before { content: 'Lua'; }
pre.src-matlab:before { content: 'MATLAB'; }
pre.src-mscgen:before { content: 'Mscgen'; }
pre.src-ocaml:before { content: 'Objective Caml'; }
pre.src-octave:before { content: 'Octave'; }
pre.src-org:before { content: 'Org mode'; }
pre.src-oz:before { content: 'OZ'; }
pre.src-plantuml:before { content: 'Plantuml'; }
pre.src-processing:before { content: 'Processing.js'; }
pre.src-python:before { content: 'Python'; }
pre.src-R:before { content: 'R'; }
pre.src-ruby:before { content: 'Ruby'; }
pre.src-sass:before { content: 'Sass'; }
pre.src-scheme:before { content: 'Scheme'; }
pre.src-screen:before { content: 'Gnu Screen'; }
pre.src-sed:before { content: 'Sed'; }
pre.src-sh:before { content: 'shell'; }
pre.src-sql:before { content: 'SQL'; }
pre.src-sqlite:before { content: 'SQLite'; }
/* additional languages in org.el's org-babel-load-languages alist */
pre.src-forth:before { content: 'Forth'; }
pre.src-io:before { content: 'IO'; }
pre.src-J:before { content: 'J'; }
pre.src-makefile:before { content: 'Makefile'; }
pre.src-maxima:before { content: 'Maxima'; }
pre.src-perl:before { content: 'Perl'; }
pre.src-picolisp:before { content: 'Pico Lisp'; }
pre.src-scala:before { content: 'Scala'; }
pre.src-shell:before { content: 'Shell Script'; }
pre.src-ebnf2ps:before { content: 'ebfn2ps'; }
/* additional language identifiers per "defun org-babel-execute"
in ob-*.el */
pre.src-cpp:before { content: 'C++'; }
pre.src-abc:before { content: 'ABC'; }
pre.src-coq:before { content: 'Coq'; }
pre.src-groovy:before { content: 'Groovy'; }
/* additional language identifiers from org-babel-shell-names in
ob-shell.el: ob-shell is the only babel language using a lambda to put
the execution function name together. */
pre.src-bash:before { content: 'bash'; }
pre.src-csh:before { content: 'csh'; }
pre.src-ash:before { content: 'ash'; }
pre.src-dash:before { content: 'dash'; }
pre.src-ksh:before { content: 'ksh'; }
pre.src-mksh:before { content: 'mksh'; }
pre.src-posh:before { content: 'posh'; }
/* Additional Emacs modes also supported by the LaTeX listings package */
pre.src-ada:before { content: 'Ada'; }
pre.src-asm:before { content: 'Assembler'; }
pre.src-caml:before { content: 'Caml'; }
pre.src-delphi:before { content: 'Delphi'; }
pre.src-html:before { content: 'HTML'; }
pre.src-idl:before { content: 'IDL'; }
pre.src-mercury:before { content: 'Mercury'; }
pre.src-metapost:before { content: 'MetaPost'; }
pre.src-modula-2:before { content: 'Modula-2'; }
pre.src-pascal:before { content: 'Pascal'; }
pre.src-ps:before { content: 'PostScript'; }
pre.src-prolog:before { content: 'Prolog'; }
pre.src-simula:before { content: 'Simula'; }
pre.src-tcl:before { content: 'tcl'; }
pre.src-tex:before { content: 'TeX'; }
pre.src-plain-tex:before { content: 'Plain TeX'; }
pre.src-verilog:before { content: 'Verilog'; }
pre.src-vhdl:before { content: 'VHDL'; }
pre.src-xml:before { content: 'XML'; }
pre.src-nxml:before { content: 'XML'; }
/* add a generic configuration mode; LaTeX export needs an additional
(add-to-list 'org-latex-listings-langs '(conf " ")) in .emacs */
pre.src-conf:before { content: 'Configuration File'; }
table { border-collapse:collapse; }
caption.t-above { caption-side: top; }
caption.t-bottom { caption-side: bottom; }
td, th { vertical-align:top; }
th.org-right { text-align: center; }
th.org-left { text-align: center; }
th.org-center { text-align: center; }
td.org-right { text-align: right; }
td.org-left { text-align: left; }
td.org-center { text-align: center; }
dt { font-weight: bold; }
.footpara { display: inline; }
.footdef { margin-bottom: 1em; }
.figure { padding: 1em; }
.figure p { text-align: center; }
.inlinetask {
padding: 10px;
border: 2px solid gray;
margin: 10px;
background: #ffffcc;
}
#org-div-home-and-up
{ text-align: right; font-size: 70%; white-space: nowrap; }
textarea { overflow-x: auto; }
.linenr { font-size: smaller }
.code-highlighted { background-color: #ffff00; }
.org-info-js_info-navigation { border-style: none; }
#org-info-js_console-label
{ font-size: 10px; font-weight: bold; white-space: nowrap; }
.org-info-js_search-highlight
{ background-color: #ffff00; color: #000000; font-weight: bold; }
.org-svg { width: 90%; }
/*]]>*/-->
</style>
<link rel="stylesheet" href="css/worg.css" type="text/css" media="screen" />
<link rel="stylesheet" type="text/css" href="css/bundle.css"/>
<link rel="stylesheet" type="text/css" href="css/custom.css"/>
<script src="css/bundle.js" type="text/javascript" ></script>
<script>
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
})(window,document,'script','//www.google-analytics.com/analytics.js','ga');
ga('create', 'UA-74660978-1', 'auto');
ga('send', 'pageview');
</script>
<script type="text/javascript">
/*
@licstart The following is the entire license notice for the
JavaScript code in this tag.
Copyright (C) 2012-2017 Free Software Foundation, Inc.
The JavaScript code in this tag is free software: you can
redistribute it and/or modify it under the terms of the GNU
General Public License (GNU GPL) as published by the Free Software
Foundation, either version 3 of the License, or (at your option)
any later version. The code is distributed WITHOUT ANY WARRANTY;
without even the implied warranty of MERCHANTABILITY or FITNESS
FOR A PARTICULAR PURPOSE. See the GNU GPL for more details.
As additional permission under GNU GPL version 3 section 7, you
may distribute non-source (e.g., minimized or compacted) forms of
that code without the copy of the GNU GPL normally required by
section 4, provided you include this license notice and a URL
through which recipients can access the Corresponding Source.
@licend The above is the entire license notice
for the JavaScript code in this tag.
*/
<!--/*--><![CDATA[/*><!--*/
function CodeHighlightOn(elem, id)
{
var target = document.getElementById(id);
if(null != target) {
elem.cacheClassElem = elem.className;
elem.cacheClassTarget = target.className;
target.className = "code-highlighted";
elem.className = "code-highlighted";
}
}
function CodeHighlightOff(elem, id)
{
var target = document.getElementById(id);
if(elem.cacheClassElem)
elem.className = elem.cacheClassElem;
if(elem.cacheClassTarget)
target.className = elem.cacheClassTarget;
}
/*]]>*///-->
</script>
</head>
<body>
<div id="content">
<h1 class="title">Tips for MSc students</h1>
<div id="table-of-contents">
<h2>Table of Contents</h2>
<div id="text-table-of-contents">
<ul>
<li><a href="#orgba90834">Commitment</a></li>
<li><a href="#org65f4927">Intellectual rigour</a></li>
<li><a href="#org0623c94">Organisation</a></li>
<li><a href="#org180339c">Creativity</a></li>
<li><a href="#orgd7444a7">Marketing speak</a></li>
<li><a href="#org408c177">Literature</a></li>
<li><a href="#orga0a70b7">Questions</a></li>
<li><a href="#org29d55de">Feedback on drafts</a></li>
<li><a href="#org65e4933">Writing</a></li>
<li><a href="#orge9a6ab1">Flexibility</a></li>
<li><a href="#org3e9a1a0">Tools</a></li>
<li><a href="#org41d9ddb">Coding</a></li>
<li><a href="#org5a57d08">Formalities</a></li>
</ul>
</div>
</div>
<p>
If you are a student doing or considering doing an MSc project with me, keep reading, this document will hopefully provide some useful guidance.
</p>
<p>
Given my area of expertise (computer science with a focus towards cryptography), most MSc projects I supervise will be somewhat technical in nature. Hence, the following guidance is written with a view towards that area.
</p>
<p>
However, I am happy to discuss/consider supervising MSc projects in other areas of information security as well. In this case not all advise below would apply. If you are unsure, come talk to me.
</p>
<p>
<b>Note:</b> Large parts of this document is shamelessly stolen from <a href="https://github.com/veorq/misc/blob/students/STUDENTS.md">JP Aumasson</a>.
</p>
<div id="outline-container-orgba90834" class="outline-2">
<h2 id="orgba90834">Commitment</h2>
<div class="outline-text-2" id="text-orgba90834">
<p>
In order to successfully deliver a good MSc project it quite important to work on something you are interested in and something you care about.
</p>
<p>
If you’re not enjoying working on the project at all this is not a good sign and you should probably come and talk to me. If you feel unsatisfied with the work you're doing or if you'd prefer to do something a bit different, we can discuss if it is possible to adapt the project to a topic that is better for you, in terms of learning, efficiency or career.
</p>
</div>
</div>
<div id="outline-container-org65f4927" class="outline-2">
<h2 id="org65f4927">Intellectual rigour</h2>
<div class="outline-text-2" id="text-org65f4927">
<p>
You will need to bring rigour and an analytical mindset. For example, you should be able to define the problem precisely, to determine what information you need to solve that problem and whether you have data or a theorem at your disposal that carries that information.
</p>
<p>
If you make a claim not supported by any data or theorem, you should be able to define the premises upon which your claim stands. Also, you should be able to detect bogus reasoning and fallacious claims.
</p>
<p>
When data is available, use it to make precise fact-based claims, rather than mere qualitative assessments or guesses. For example, instead of saying “this method is faster” you would say “this method is 2.6 times faster than the generic one on CPU model X”, or “this method runs at 123 GBps” — measure, don't speculate. Similarly, when you state that this or that construction is cryptographically secure, state precisely which security goals it meets under which hardness assumptions. Finally, make your results and measurements reproducible.
</p>
</div>
</div>
<div id="outline-container-org0623c94" class="outline-2">
<h2 id="org0623c94">Organisation</h2>
<div class="outline-text-2" id="text-org0623c94">
<p>
I strongly recommend that you maintain a todo list and notes in order to keep track of tasks and to prioritise them. I also recommend creating a rough project timeline against which you can measure your progress as you get on with the project. This way you can detect when things go off the rails. There are plenty of software options available to help you with that. Some people like <a href="https://trello.com">Trello</a>, some people like <a href="https://www.toodledo.com">Toodledo</a>, some people swear on <a href="https://evernote.com">Evernote</a> or <a href="https://www.onenote.com">OneNote</a>. I personally use <a href="http://orgmode.org">Org-mode</a>.
</p>
<p>
You should also organise your literature notes and your references in general in some systematic way. Some people like <a href="https://www.zotero.org">Zotero</a>, some like <a href="https://www.mendeley.com">Mendeley</a> to help them with that. I use <a href="https://github.com/tmalsburg/helm-bibtex">Helm-BibTeX</a>.
</p>
</div>
</div>
<div id="outline-container-org180339c" class="outline-2">
<h2 id="org180339c">Creativity</h2>
<div class="outline-text-2" id="text-org180339c">
<p>
Your project might include a research component. This means that you're not here just to execute tasks, but also to bring your own ideas regarding the direction and execution of the project. Creativity means, for example, finding different ways to solve a technical problem or adapting the goals of the project to more interesting/ambitious/original ones. Creativity is also about challenging my ideas and, even better, proving me wrong.
</p>
<p>
“But I'm not a creative person!”; creativity is not a skill or a character trait, it's a mode of operation. It takes curiosity and stubbornness.
</p>
</div>
</div>
<div id="outline-container-orgd7444a7" class="outline-2">
<h2 id="orgd7444a7">Marketing speak</h2>
<div class="outline-text-2" id="text-orgd7444a7">
<p>
If you are doing a <b>technical</b> project with me, do not spend the first 20 pages with marketing speak and quoting Gartner reports on business projections. For example, when investigating the security of some software for remote file storage, do not start with an extensive account on “why private, public or hybrid clouds are excellent for businesses”. It is important to motivate a technical question but keep it brief.
</p>
<p>
Similarly, equip yourself with a good detector for bad science. You'll need it if you work in information security! In information security, some signs are:
</p>
<ul class="org-ul">
<li>The abuse of the word “cyber”.</li>
<li>The use of superlatives instead of reliable facts. For example, “our ultra-advanced cyber detection system performs extraordinarily to reach a 200 threats.“</li>
<li>Incorrect use of technical terms, for example, confusion between “vulnerability”, “exploit" and “malware” or “cipher” and “cryptographic protocol”.</li>
<li>The use and abuse of buzzwords, especially when simpler terms would fit. For example, “secure blockchain-based deep learning”. New buzzwords appear regularly.</li>
<li>Forcing the blockchain on everything.</li>
</ul>
</div>
</div>
<div id="outline-container-org408c177" class="outline-2">
<h2 id="org408c177">Literature</h2>
<div class="outline-text-2" id="text-org408c177">
<p>
Random websites, press clippings and typically whitepapers are not reliable sources of information. Some technical whitepapers contain useful information, but often they are just glorified ads.
</p>
<p>
You will have to engage with the academic literature. But not all literature is of equal quality, you’ll need to develop a sense of what is good research and what is not. I suggest the following exercise:
</p>
<ol class="org-ol">
<li>Find 3 academic papers (preferably published, but in this fast moving field often pre-prints will have to do) on your topic.</li>
<li>Describe what each does in 3 sentences each max.</li>
<li>Rank these three papers from great to perhaps-not-so-great or worse. Explain why in 1-2 sentences.</li>
<li>Find the three top venues (conferences, journals) where papers on this area would be published.</li>
</ol>
<p>
This would give you (and me) some idea how hard a time you’d have engaging with the subject in the manner the MSc project would require: finding scientific work and critically evaluating it.
</p>
</div>
</div>
<div id="outline-container-orga0a70b7" class="outline-2">
<h2 id="orga0a70b7">Questions</h2>
<div class="outline-text-2" id="text-orga0a70b7">
<p>
Before asking me a question (such as “how to get command-line arguments in C?”), try to find the answer by yourself first in the usual places (literature, Google, StackOverflow, etc.). I can suggest some strategies for how to find good answers.
</p>
<p>
I will try to respond to your requests or questions by email fairly quickly. You can also come by my office hour (Thursday, 2pm) but I prefer a written form because it forces you to write down the question and thus think about it. A written response also leaves a trace for further reference (“but <b>you</b> told me that, look!“).
</p>
<p>
Similarly, the more specific your question the better are your chances of getting a good response. For example “Can we have a meeting about my project?” gives me no clue if and what I should prepare, how much time to schedule or if the issue at hand could be handled much more efficiently in writing via e-mail.
</p>
</div>
</div>
<div id="outline-container-org29d55de" class="outline-2">
<h2 id="org29d55de">Feedback on drafts</h2>
<div class="outline-text-2" id="text-org29d55de">
<p>
I’m happy to give you feedback on an early draft up until 4 weeks before the submission deadline. Before and after that deadline, I’m happy to answer specific questions.
</p>
<p>
I cannot give detailed feedback on grammar or spelling, but I will point out if I believe you should improve.
</p>
</div>
</div>
<div id="outline-container-org65e4933" class="outline-2">
<h2 id="org65e4933">Writing</h2>
<div class="outline-text-2" id="text-org65e4933">
<p>
To learn the basics of good writing, JP Aumasson recommends <a href="http://www.crockford.com/wrrrld/style.html">The Elements of Style</a>. It's a quick and easy read. To further improve your English, he also recommends you check William Zinsser's <a href="https://www.amazon.com/Writing-Well-Classic-Guide-Nonfiction/dp/0060891548/">On Writing Well</a>, another classic. You'll find a PDF <a href="http://www.brynmawr.edu/math/people/anmyers/ESem/on-writing-well.pdf">online</a>. <a href="http://www.isg.rhul.ac.uk/~slng/">Siaw-Lynn Ng</a> recommends <a href="https://www.amazon.co.uk/Line-How-Edit-Your-Writing/dp/0395393914">Line by Line - How to Edit Your Own Writing</a> by Claire Kehrwald Cook.
</p>
<p>
Royal Holloway has a <a href="https://www.royalholloway.ac.uk/ecampus/cedas/home.aspx">Centre for the Development of Academic Skills</a> which offers courses on improving Academic English writing. It also offers a service to connect you to a professional, approved proofreader. They will require a letter from me for the latter, I’m happy to provide it.
</p>
<p>
You may also have some success with automated tools such as <a href="https://app.grammarly.com">Grammarly</a>, <a href="http://typely.com">Typely</a>, <a href="https://www.languagetool.org">LanguageTool</a>, the latter is available as a plugin for Emacs, Sublime Text and LibreOffice.
</p>
</div>
</div>
<div id="outline-container-orge9a6ab1" class="outline-2">
<h2 id="orge9a6ab1">Flexibility</h2>
<div class="outline-text-2" id="text-orge9a6ab1">
<p>
You may receive emails from me at night or during weekends, but that does not mean that I expect you to also work at those times.
</p>
</div>
</div>
<div id="outline-container-org3e9a1a0" class="outline-2">
<h2 id="org3e9a1a0">Tools</h2>
<div class="outline-text-2" id="text-org3e9a1a0">
<p>
Feel free to use and propose other tools than the ones I propose. I neither care if you use emacs, vi, Sublime Text or MS Word nor which programming language, framework or libraries you use.
</p>
<p>
I highly recommend that you use revision control such as to organise and backup your project. I’ve written about using Git for academic writing on <a href="https://martinralbrecht.wordpress.com/2016/01/10/writing-crypto-papers-and-version-control/">my blog</a>.
</p>
</div>
</div>
<div id="outline-container-org41d9ddb" class="outline-2">
<h2 id="org41d9ddb">Coding</h2>
<div class="outline-text-2" id="text-org41d9ddb">
<p>
If you write code, it should not only work/compile, it should also follow the best practices and coding conventions for the specific language you're using. You should assume that your code will be published and be visible to your peers and future potential employers.
</p>
<p>
For example, don’t code a dirty or unsafe workaround thinking “that's ok since nobody will read the code”. If you have to use such code, add a comment highlighting it and justifying it.
</p>
<p>
To write code of better quality, use static code analysers and code formatters. For example, <code>pylint</code> and <code>pep8</code> for Python, gofmt for Go, and for C(++), <code>valgrind</code>, <code>flawfinder</code>, <code>clang-format</code>, clang's address sanitizer, to name but a few.
</p>
</div>
</div>
<div id="outline-container-org5a57d08" class="outline-2">
<h2 id="org5a57d08">Formalities</h2>
<div class="outline-text-2" id="text-org5a57d08">
<p>
The most straight-forward way to address me is just to use my first name, no “Mr.”, “Dr.” required. This is the general etiquette at Royal Holloway and British universities in general. Hence, I tend to address everybody by their first name as well. If that doesn’t work for you, let me know.
</p>
<div class="HTML">
<p>
</p>
</div>
</div>
</div>
</div>
</body>
</html>