Zero day¶
20 min Foundations Needs: the email Holberton sent you
Four accounts run your training. This tutorial gets all four working. Do it before your first day, not during it.
Why this matters¶
Every hour you spend chasing a login is an hour you are not learning. These four platforms are also how your work gets seen and graded, so a broken account in week one turns into a missing submission in week two.
The four platforms¶
Three of them use one password. GitHub is the exception, and it is the one that follows you after graduation.
Step 1: Set up the intranet¶
Go to intranet.hbtn.io and log in with the credentials from your welcome email. Bookmark the page. You will open it every day.
Then finish your profile:
- Click your profile icon in the bottom left corner.
- Fill in every field marked with an asterisk.
- Add a photo. A plain head and shoulders shot is fine. This is the photo your instructors and future employers will see.
- Save.
Do not change your password yet
Slack and Containers on Demand read your account from the intranet. Change the password now and you may lock yourself out of the other two before they have synced. Wait until all four platforms work.
Step 2: Join Slack¶
Open the intranet and find the Slack link in the left navigation panel. Log in with the same credentials.
You are added to your cohort channel automatically. Download the desktop or phone app as well, because the browser version is easy to forget and that is where schedule changes get announced.
Step 3: Create your GitHub account¶
Already have one you use professionally? Use it and skip to Step 4.
Otherwise go to github.com/signup. Two choices matter here:
The email. Use one you will still read in five years. Not a school address that gets shut off when you graduate.
The username. This becomes part of your professional identity. It appears in every project link you ever send to an employer. Something close to your real name works well. Something you thought was funny at nineteen does not.
When you have it, go back to your intranet profile and add the username there. The automated grading system uses it to find your work, so a typo means your projects do not get marked.
Step 4: Start your development machine¶
Containers on Demand gives everyone the same Linux machine with Python and the ML libraries already installed. Nobody has to debug somebody else's laptop.
- Go to cod.hbtn.io and log in with your intranet credentials.
- Set the Region dropdown at the top of the page to Europe. This affects how fast the connection feels from Tirana.
- Find ml_ubuntu_2204 in the container list and click Spin Up Container. Give it up to a minute.
- Click Actions, then VS Code. A full editor and a Linux terminal open in your browser.
Containers stop after four hours
Your container shuts down four hours after you start it, and anything you have not pushed to GitHub is gone. You can add more time while you work, from the same Actions menu. Two habits protect you: commit often, and never leave your only copy of something inside a container.
Check yourself¶
Five minutes, and it proves all four accounts work.
- Log in to the intranet and confirm your profile shows your photo and your GitHub username.
- Post a short hello in your cohort channel on Slack.
- Open your GitHub profile page and check the username reads the way you want an employer to read it.
- Spin up a container, open the terminal, and run
python3 --version. You should see Python 3.10 or higher.
If any of the four fails, ask in Slack now. This is exactly what the channel is for.
Quick reference¶
| Platform | Where | What it is for | Login |
|---|---|---|---|
| Intranet | intranet.hbtn.io | Projects, deadlines, grades | The one from your email |
| Slack | Link inside the intranet | Questions and announcements | Same as intranet |
| GitHub | github.com | Your code and portfolio | Your own account |
| Containers on Demand | cod.hbtn.io | Linux machine for coding | Same as intranet |
Next¶
Your accounts work. Now set up the tool that saves your work.