Computer Science
Grade 9
20 min
Online Manners
Online Manners
Tutorial Preview
1
Introduction & Learning Objectives
Learning Objectives
Define key terms like Netiquette, Digital Footprint, and Code of Conduct.
Analyze online interactions using the 'THINK' framework to determine if they are appropriate.
Apply a structured approach to resolving digital disagreements in a collaborative coding environment.
Identify and avoid common pitfalls of digital communication, such as tone misinterpretation.
Evaluate the impact of a digital footprint on future academic and career opportunities in technology.
Draft a professional and constructive code review comment.
Ever sent a message and had someone get completely the wrong idea? 🧐 Let's explore why that happens and how to be a pro communicator online.
This lesson explores 'Online Manners,' or Netiquette, from a computer sci...
2
Key Concepts & Vocabulary
TermDefinitionExample
NetiquetteA combination of the words 'network' and 'etiquette,' it refers to the set of social conventions and rules for polite and appropriate communication on the Internet.Not typing messages in ALL CAPS, as this is universally understood as shouting online.
Digital FootprintThe trail of data, both active and passive, that you create while using the Internet. It includes everything from code commits to social media posts.A comment you made on a public bug report for a software project 5 years ago is part of your digital footprint and could be seen by a future employer.
Code of Conduct (CoC)A formal document that outlines the expected behaviors and social norms for participants in an online community or open-source project.The Linux Kernel Code o...
3
Core Syntax & Patterns
The 'THINK' Protocol
Before you post, ask yourself: Is it True? Is it Helpful? Is it Inspiring? Is it Necessary? Is it Kind?
Use this as a mental checklist before sending a message, posting a comment, or submitting a code review. It acts as a filter to ensure your communication is positive and productive, preventing impulsive and potentially damaging posts.
The Public-Private Data Rule
if (is_personal_or_sensitive_data) { share_location = 'private_channel'; } else { share_location = 'public_channel'; }
A simple conditional logic for sharing information. Always assume public channels (like a main project chat or a public forum) are permanently archived and searchable. Share personal information (like phone numbers, passwords, or private concerns)...
4 more steps in this tutorial
Sign up free to access the complete tutorial with worked examples and practice.
Sign Up Free to ContinueSample Practice Questions
Challenging
You and a teammate have a persistent disagreement about coding style that is slowing down code reviews. Based on the principles in the tutorial, what is the most professional, multi-step approach to resolve this?
A.Continuously argue your point in every code review until they give in.
B.Publicly post in the team chat asking who is right, and then follow the majority opinion.
C.First, send a private message to find a compromise. If that fails, suggest adopting an automated linter/formatter for the project to enforce a consistent style objectively. If needed, involve a team lead as a final step.
D.Secretly reformat their code to your style before merging it into the main branch.
Challenging
A new open-source contributor makes a mistake, and a senior member replies in the public forum: 'This is a classic rookie mistake. Read the contribution guide before wasting our time.' As a moderator, which response BEST upholds the project's netiquette and Code of Conduct?
A.Delete the senior member's comment and ban them immediately.
B.Publicly reply to the senior member: 'That was an inappropriate comment.' Then, privately message the new contributor to apologize and offer help.
C.Privately message the senior member explaining why their comment was unhelpful and against the CoC. Publicly post a helpful, welcoming comment to the new contributor, guiding them to the correct resources without mentioning the negative interaction.
D.Do nothing, as the senior member was technically correct that the contributor should have read the guide.
Challenging
A project's Code of Conduct includes rules like 'No harassment' and 'Be respectful.' However, the project is known for having frequent, long-lasting flame wars over technical decisions. Which concept is likely missing or not well-defined in their CoC that could help address this?
A.clause about software licensing.
B.clear definition of 'Constructive Criticism' and a protocol for de-escalating disagreements.
C.list of the project maintainers.
D.rule against using all caps.
Want to practice and check your answers?
Sign up to access all questions with instant feedback, explanations, and progress tracking.
Start Practicing Free