I first happened upon Credo while building a console-based version of 2048 (this was the early stages of learning Elixir). Running Credo on my code for the first time was a delight. It made me instantly wish for similar tools for our non-Elixir code bases at work.<p>For those venturing into Elixir, Credo is especially useful. While I'm experienced in functional programming, Credo was a great way to learn more idiomatic usage of Elixir.<p>While Haskell has the fantastic ghc-mod for guided refactoring, Go has gofmt, and Ruby has rubocop among others, I find Credo to be a nice blend of the best features of all these tools. I also appreciate the UI, which groups feedback into 3 visually-distinct categories: Code Readability, Refactoring Opportunities, and Warnings [1]. This makes it makes it easy to prioritize your changes.<p>If you'd like more background on Credo, The Elixir Fountain [2] recently hosted a nice podcast with the creator of Credo, René Föhring [3].<p>[1] <a href="http://credo-ci.org/" rel="nofollow">http://credo-ci.org/</a>
[2] <a href="http://elixirfountain.com/" rel="nofollow">http://elixirfountain.com/</a>
[3] <a href="https://soundcloud.com/elixirfountain/elixir-fountain-rene-fohring-2016-06-13" rel="nofollow">https://soundcloud.com/elixirfountain/elixir-fountain-rene-f...</a>