Ex 
Has anyone found a good way to describe a "beginner-friendly issue" without using non-inclusive words, like easy, simple, or straightforward? #opensource
Afficher cette discussion
-
I think "quick" has the same problem though. How bad am I if I'm not able to solve this quickly? Care to elaborate on what a "quick fix" is to you?
I mean, how many "easy" labelled issues have caused a major refactoring ;-)The reason for "quick" (time based) vs "simple" (skill based) is that the time scale is more relative and has less reference points than the skills scale.
-
-
I.e. if I am a beginner piano player, I am happy and proud I learn something [simple] in a week. I call it "quick", while perfectly aware an experienced person can learn it probably in minutes. Same with tech I guess.
Merci. Twitter en tiendra compte pour améliorer votre fil. SupprimerSupprimer
-
-
-
I’m afraid don’t understand what you mean by “more relative and less reference points”. Could you say “quick”, in this case, could refer to a limited scope then, where the fix is “well-defined”?
-
Ok, let's try another way. The perception of "easy" is more or less similar across the board without much context. While the perception of "quick" may vary across the same board. What theoretically may lead to less frustration from any misalignment If we speak in blurry terms =)
Fin de la conversation
Nouvelle conversation -
Le chargement semble prendre du temps.
Twitter est peut-être en surcapacité ou rencontre momentanément un incident. Réessayez ou rendez-vous sur la page Twitter Status pour plus d'informations.