# The Worst Elm Code Possible

**URL:** <https://discourse.elm-lang.org/t/the-worst-elm-code-possible/9380>\
**Category:** Show and Tell\
**Created:** [October 7, 2023, 9:10am UTC](https://discourse.elm-lang.org/t/the-worst-elm-code-possible/9380 "2023-10-07T09:10:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![supermario](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/supermario/32/92_2.png) [@supermario](https://discourse.elm-lang.org/u/supermario)\
**Post date:** [October 7, 2023, 9:10am UTC](https://discourse.elm-lang.org/t/the-worst-elm-code-possible/9380/1 "2023-10-07T09:10:51Z")

</div>

I ran a light-hearted session at Elm Camp to seek out the worst Elm code possible.

Here was my session prompt:

> I’ve heard more than a few times “I’d rather deal with bad Elm than good Javascript”.
> 
> I think “bad Elm” is probably synonymous with “unintentionally bad Elm”.
> 
> But what about _the worst Elm_? Like, intentionally, maliciously, the absolute most horrible Elm possible. What does that look like? I’d like to think it’s actually still not that bad! Or at least, I can’t imagine not being able to refactor it happily…
> 
> Let’s find out together if that’s true!

Here’s my writeup of our session:

[Worst Elm Code Possible – Or, the checklist for good Elm, and the one thing to be careful to avoid](https://realmario.notion.site/Worst-Elm-Code-Possible-393f8fc7338b46afb13efb9766d909bf?pvs=4)

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex035/uploads/elm_lang/original/1X/50a05e53677a2c3b47776d7abd0f113eb50193a1.png) [@system](https://discourse.elm-lang.org/u/system)\
**Post date:** [October 17, 2023, 9:11am UTC](https://discourse.elm-lang.org/t/the-worst-elm-code-possible/9380/2 "2023-10-17T09:11:12Z")

</div>

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.