[TECH ED] Naming accounts consistently #101
Labels
🏕 Priority Mandatory
This work is expected
🦔 Size Tiny
Less than 30 minutes
📅 Sprint 1
Assigned during Sprint 1 of this module
🎯 Topic Communication
Reading, writing, speaking, and listening in English; expressing our ideas
📅 User Focused Data
Tickets for User Focused Data
Link to the coursework
Your own accounts!
Why are we doing this?
Naming Accounts Consistently
Tip
Use the same name everywhere in your work with CYF.
Consistency in online account names
During the CYF course you will make accounts online. (Such as Slack, GitHub, Google, LinkedIn...)
You should always use your real name. It must always be the same name. Don't use any other words apart from your name. Do not ever put your birth year or age in your user name. These things can harm your job prospects so start as you mean to go on.
Trainees use the same name everywhere in their work with CYF.
Note
CYF recognises you may need to keep your birth name private. When we say real name, we mean the name you go by. It does not have to match your birth certificate or any other legal document.
Your profile picture does not have to be a picture of you. It must be safe for work, consistent and unique, so you don't get mixed up with other people. If you need to keep your photo private, you can use Robohash to make a unique profile picture.
Summary
Don't use cute handles or put the year of your birth in your username.
Use the same username and picture across all CYF accounts. This also means professional profiles like Linkedin and GitHub.
Maximum time in hours
.1
How to get help
Swap with a classmate and check their profile. Ask yourself:
If you didn't know them, would you know this was their Slack account? If you didn't know them, would you know this was their LInkedIn? If you were a recruiter reading their GitHub, could you find their LinkedIn within six seconds? If you wanted to invite them to an opportunity, could you do that without asking them first?
The text was updated successfully, but these errors were encountered: