# Afterthoughts around about Kernel code and custom operators complaints

**URL:** <https://discourse.elm-lang.org/t/afterthoughts-around-about-kernel-code-and-custom-operators-complaints/5558>\
**Category:** Request Feedback\
**Created:** [April 16, 2020, 8:40am UTC](https://discourse.elm-lang.org/t/afterthoughts-around-about-kernel-code-and-custom-operators-complaints/5558 "2020-04-16T08:40:44Z")\
**Posts on this page:** 1\
**Showing post:** 57

<div class="post-metadata">

**Author:** ![KasMA1990](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/kasma1990/32/2115_2.png) [@KasMA1990](https://discourse.elm-lang.org/u/KasMA1990)\
**Post date:** [April 21, 2020, 2:21pm UTC](https://discourse.elm-lang.org/t/afterthoughts-around-about-kernel-code-and-custom-operators-complaints/5558/57 "2020-04-21T14:21:03Z")

</div>

Maybe a different way of framing it would also be useful: Elm itself is designed for user success, or making it easy to do the right thing, and hard to do the wrong thing.

Is this a way of thinking that could be applied to working _on_ Elm too? Because right now it seems that the process of trying to contribute to Elm actually sets people up for failure. `elm-explorations` is one place where we’ve seen this now, but I think it’s the same problem that occurs when someone creates a PR or an issue that doesn’t get a timely or useful response, [like in this thread](https://discourse.elm-lang.org/t/the-governance-of-elm-docs-and-smaller-tools/4571).

I realize things are this way for a reason, and I’m not suggesting any change here is easy or simple. But maybe just asking “How can we set the user up for success both when using Elm as a tool, but also when interacting with the process around Elm?” is helpful.

---

_[View the full topic](https://discourse.elm-lang.org/t/afterthoughts-around-about-kernel-code-and-custom-operators-complaints/5558)._
