Naming accounts consistently
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- documentation
Research direction
The issue provides coursework guidance about consistent names, usernames, and profile pictures but names no file or test. Review where this onboarding content is maintained, then compare the published guidance with the requirements in the issue and confirm the completed text addresses the stated account-naming checks.
Written by the indexing model from the issue text.
Description
Link to the coursework
Your own accounts!
Why are we doing this?
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?
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CodeYourFuture/Module-Onboarding
-
🎯 Topic Communication 🏕 Priority Mandatory 📅 Sprint 1 Module-Welcome Setup Submit:None 🦔 Size Tiny
Difficulty 1/5 Under an hour Newbie friendliness 90/100
CodeYourFuture/Module-Onboarding#3 · 1 comment · 4 reactions ·
-
Do the Prep Open🏕 Priority Mandatory 📅 Sprint 1 Recurring Submit:None
Difficulty 1/5 Half a day Newbie friendliness 25/100
-
🏕 Priority Mandatory 📅 Sprint 1 Module-Welcome Setup Submit:None 🦔 Size Tiny
Difficulty 1/5 Under an hour Newbie friendliness 70/100
-
🏕 Priority Mandatory 🐂 Size Medium 📅 Sprint 1 Setup Submit:None
Difficulty 1/5 1-3 hours Newbie friendliness 20/100
-
🏕 Priority Mandatory 🐇 Size Small 📅 Sprint 1 Core Submit:None
Difficulty 1/5 Under an hour Newbie friendliness 55/100
All issues in CodeYourFuture/Module-Onboarding
Similar issues
-
sync-en
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
agilepathway/label-checker#640 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
BasedHardware/omi#15662 · 1 comment ·
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100