-
Notifications
You must be signed in to change notification settings - Fork 18
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
adding Hyrums Law #212
adding Hyrums Law #212
Conversation
Build Successful! You can find a link to the downloadable artifacts below.
|
Thanks for your proposal, @dret. I'm not sure about the youtube video reference. Is there also an article/paper from Hyrum we can reference? What do the others think? |
docs/1-terms/H/term-hyrums-law.adoc
Outdated
// tag::DE[] | ||
==== Hyrums Law | ||
|
||
Hyrums Law (benannt nach dem Google-Ingenieur Hyrum Wright) besagt, dass bei einer ausreichend großen Anzahl von Nutzern irgendjemand von jedem beobachtbare Verhalten einer Schnittstelle abhängen wird. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
*beobachtbaren
I don't see that relevant, as the rule is not mentioned in the Foundation curriculum. Therefore, I don't want to care about it. It's a nice mention during the trainings, though. |
It will be part of the API module for sure, so it would be nice to have it included in the glossary. |
Ola Erik, we are currently discussing wether to restrict the Glossary to Foundation-terms, as NO other advanced group has ever actively participated in its creation and maintenance... and for the Foundation it is highly useful for exam preparation (which is not relevant for Advanced). |
On 2025-02-18 12:27, Dr. Gernot Starke wrote:
Ola Erik, we are currently discussing wether to restrict the Glossary to Foundation-terms, as NO other advanced group has ever actively participated in its creation and maintenance... and for the Foundation it is highly useful for exam preparation (which is not relevant for Advanced).
Ok, that's useful info, thanks. I was under the (apparently mistaken) impression that other modules should be represented in the glossary as well. I am completely fine to just focus on the foundation, and then all we (the API module) have to do is to possibly add a few terms from foundation that we want to use as well and that aren't currently covered in the glossary.
Here's my personal opinion: Hyrum's law should be something everybody knows about. You can design all you want and still people will build things in ways you didn't think about... https://xkcd.com/1172/
|
I believe Eriks thesis that everybody should know this rule... (although I've never heard of it). Glossary entries contain no risks, therefore it might be better to have more |
Part of addressing #209