handbook / Getting Started

Expectations

What we expect from each other, roughly in order of importance.

1. Honesty about problems. Tell us early when something is not working. A project, a collaboration, your own workload, anything.
2. Ownership. Once you have taken on a task, see it through, or say clearly that you cannot.
3. Reasonable working hours. We do not track hours, we track output and wellbeing. You still need to follow the institute norms on working hours and leave. Personally, I do not care how many hours you put in. What I do care about is that you are available from 10 AM to 5 PM on weekdays, since that is when we plan and discuss things together. If you cannot make it on a given day, let me know beforehand if possible.
4. Documentation. Code, data, and reports should be understandable by someone who joins the project after you.
5. Active participation. We want to build a team where everyone takes part in group activities, of serious or fun nature. If you have a conflict with any of this, talk to me.

These are defaults, not fixed rules. We can sit down and work out something different if your situation calls for it.

What we do not expect from you

• We do not expect you to know everything on day one. Ask questions.
• We do not expect perfect results at all stages of a project. Failed simulations, dead ends, and bugs are a normal part of research.
• We do not expect you to work weekends or late nights as a rule. Occasional crunch before a deadline happens, but it should not be the norm.
• We do not expect you to agree to every task that lands on your desk without discussion, particularly if it does not fit your project or your bandwidth.

What you can expect from me as a guide

1. Scientific and technical guidance. You can expect me to help you frame the problem, discuss possible approaches, and give feedback on your results and interpretation.
2. Regular meetings. You can expect a standing one on one and a group meeting, and my full attention during that time.
3. Timely feedback on writing. When you send me a draft, expect a response within one to two weeks in most cases, sooner if a deadline is close.
4. Support for your career. Reference letters on time, advice on grants, fellowships, and job applications, and introductions to people in the field where I can make them.
5. Resources. I will do what I can to get you the compute, funding, and equipment you need to do your work well.
6. Fair treatment. If something feels unfair, or you are uncomfortable with how a situation is handled, tell me directly.

What you should not expect from me

• Do not expect me to completely assign a research project myself. I will put more efforts initially, but at the end I would like you to come up with your own ideas and workplans.
• Do not expect an instant reply to every message, I dont expect the same from you. I will get back to you, but give it sometime before following up.
• Do not expect me to debug your code or fix a broken script line by line. I will help you think through a problem, but the first pass at solving it should be yours.
• Do not expect me to remember every detail of your project without a reminder. Keep me updated, especially before meetings.
• Do not expect unconditional agreement. I will push back and ask hard questions. That is part of the job, not a sign that something is wrong.