Step 1: Pre-course survey
Why
The survey tells me who is in the room and what data you work with. It records your GitHub username, which steps 2 and 3 need. It also asks whether you plan to send a dataset in step 3. Have a look at that page first. If you are not sure or the answer is no, I write back to you. It takes under ten minutes.
Take the survey
Please complete it by Friday, 11 December 2026.
What it asks
- your consent to the use of the answers for this workshop (the answers are stored in Zurich, shared with nobody, and your email address is deleted after the workshop);
- your email address and your GitHub username;
- the operating system of your laptop and whether you can install software on it;
- your role and your work with data;
- whether you plan to send a dataset in step 3, and what holds you back if not;
- your programming experience and, optionally, the AI tools you use;
- what you want to take home.
No GitHub account yet?
The survey asks for your username. If you have no account, the survey walks you through creating one. It takes about five minutes, and the steps are these:
- Open https://github.com/signup in a new tab.
- Enter an email address you will keep and choose a password.
- Choose a username made of letters, digits and hyphens, no spaces. It is public, for example in the address of your projects. Many people use firstname-lastname.
- Confirm your email address with the code GitHub sends you.
- Go back to the survey and enter the username, without the @.
You will be able to upgrade to a paid level of service, apply discounts, join organizations, etc. in the future, so don’t fret about any of that now. Except your username. You might want to give that some thought.
A few tips, which sadly tend to contradict each other:
- Incorporate your actual name! People like to know who they’re dealing with. Also makes your username easier for people to guess or remember.
- Reuse your username from other contexts, e.g., Twitter or Slack. But, of course, someone with no GitHub activity will probably be squatting on that.
- Pick a username you will be comfortable revealing to your future boss.
- Shorter is better than longer.
- Be as unique as possible in as few characters as possible. In some settings GitHub auto-completes or suggests usernames.
- Make it timeless. Don’t highlight your current university, employer, or place of residence, e.g. JennyFromTheBlock.
- Avoid words laden with special meaning in programming.
- Avoid the use of upper vs. lower case to separate words. We highly recommend all lowercase. GitHub treats usernames in a case insensitive way, but using all lowercase is kinder to people doing downstream regular expression work with usernames, in various languages. A better strategy for word separation is to use a hyphen
-.
You can change your username later, but better to get this right the first time.
Next
Stay signed in to GitHub and go on to Step 2: post a comment on the check-in issue.