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.

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

wants to merge 3 commits into from

Conversation

Blind4Basics
Copy link
Contributor

@Blind4Basics Blind4Basics commented Jan 29, 2021

update for : Power-user

data/glossary.yml Outdated Show resolved Hide resolved
data/glossary.yml Outdated Show resolved Hide resolved
Copy link
Member

@DonaldKellett DonaldKellett left a comment

Choose a reason for hiding this comment

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

I didn't realize that my edits removed the leading whitespace from the affected lines. Perhaps you may want to add them back, but other than that, LGTM

@kazk kazk marked this pull request as draft March 15, 2021 02:22
@kazk kazk marked this pull request as ready for review April 15, 2021 02:36
@@ -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.

@Blind4Basics Blind4Basics requested a review from kazk April 16, 2021 17:54
Blind4Basics and others added 3 commits April 16, 2021 18:49
Co-authored-by: Donald Sebastian Leung <donaldsebleung@gmail.com>
- 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants