Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update glossary.yml #258

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Update glossary.yml #258

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
7c14081
Update glossary.yml
Blind4Basics Jan 29, 2021
d5cfa2b
Apply suggestions from code review
Blind4Basics Jan 30, 2021
e721329
Update glossary.yml
Blind4Basics Jan 31, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion glossary.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -244,9 +244,14 @@

It's useful for [debugging - TODO]() too.

- term: Power user
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Power user is not about having "powers".

A power user is a user of computers, software and other electronic devices, who uses advanced features of computer hardware, operating systems, programs, or websites which are not used by the average user. A power user might not have extensive technical knowledge of the systems they use but is rather characterized by competence or desire to make the most intensive use of computer programs or systems.

https://en.wikipedia.org/wiki/Power_user

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mmmh, I went too much "litteral" here (happy frenglish... x) ). What about:

Codewars' users gain honor in different ways. Doing so, they progressively unlock some privileges giving them access to extra features like the possibility to approve kata, maintain kata they didn't author, resolve comments, ...

?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not about gaining privileges. If they don't actively make use of them, they're not power users.

I think the key point in the Wikipedia is:

desire to make the most intensive use

The opposite of power user is average user. Those users that only uses Codewars to train are average users even if they have many privileges unlocked. They don't use features like authoring kata, or get involved with maintaining Codewars.

Users' activities can be broken down like the following:

  1. Train
  2. Review
  3. Create/Translate
  4. Maintain

Probably 99% of the users only does 1 and partially 2 (solving beta). 3 and 4 are power users that affects Codewars.

description: |
Codewars' users gain honor in different ways. Doing so, they progressively unlock some [privileges](references/gamification/privileges), hence "powers".
acronym: PU

- term: Preloaded (code/section)
description: |
In a Kata, the preloaded section is code that is executed _before_ the solution of the user is defined. The code hold by this section isn't visible to the user but every function or variable defined there is accessible to him drugint the executions of his code.
In a Kata, the preloaded section is code that is executed _before_ the user's solution. The code in this section isn't visible to the user but every function or variable defined there is accessible to the solution during execution.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
In a Kata, the preloaded section is code that is executed _before_ the user's solution. The code in this section isn't visible to the user but every function or variable defined there is accessible to the solution during execution.
In a kata, the preloaded section is code that is executed _before_ the user's solution. The code in this section isn't visible to the user but every function or variable defined there is accessible to the solution during execution.


If you need/want to see the preloaded section of a Kata, open a fork of a solution _after_ you solved it and look to the `Preloaded` panel.

Expand Down