Just released now…
kokolegorille
sasajuric
Author of Elixir In Action
I’m not sure running it in a pre-commit hook is optimal. Credo isn’t very slow, but IMO it’s not that fast to do it on every commit. Moreover, I wouldn’t even want credo to prevent me from committing some intermediate WIP commits.
I run credo during CI check, and that’s good enough for me. Usually I remember to check credo locally before pushing the code, but even if I don’t, it’s not a big deal. I’ll get a CI error, and fix it.
8
sasajuric
Author of Elixir In Action
Had no problems myself, but if people on the team resisted using credo I’d try to explain them why I think project/company-wide styleguide is important, and if I succeed in that, then credo pretty much becomes a logical consequence, b/c it makes sense to enforce as much of the rules as possible automatically.
1
lawik
Nerves Core Team
I’ve found credo good for enforcing in CI what I may be slacking off on or forgetting to check for.
The only thing I’ve considered turning off is the TODO. But I’m keeping that for now as well.
I could see making a project where I don’t want it just because it can feel a bit like homework and the things it enforces do not matter in all cases (quick things, throwaways, proof-of-concept). I can see entire classes of personalities that don’t like that sort of tooling and I would probably have resisted it a bunch of years back from a combination of not-invented-here, don’t tell me what to do and ugh-process-that-I-must-conform-to. So in any project, team members can have any sort of base viewpoint and I believe its more important to find a sympathetic way to work together rather than having a specific tool in use.
I’ve changed my approach over time. I’m less precious about the specific lines of code I type, I try to automate a base level of quality as far as I find reasonable and focus on more important parts of the craft, thinking, modelling the problem, writing the right tests (so I don’t break the damn thing).
4
ityonemo
I actually am pretty lax with the TODO checking on personal products, but for work products I think TODO checking is fantastic, because it reminds me to add items to milestones for github issue tracking (and sprints for JIRA tracking, which I don’t use anymore). That way you know you there won’t be code with TODOs that other people don’t have eyes on in some persistent list.
1
gshaw
I use Credo for all my projects. I like that removes bike shedding. In code bases lots of small things need decisions. The decision doesn’t really matter but it needs to be made to have consistency.
3
Sanjibukai
Hello, I’m starting with elixir..
And I love to learn about tools not really described in beginners resources but which are used by elixir gurus..
So, besides credo, what else do you use for dev or in prod?
1
lawik
Nerves Core Team
Dialyxir, to get dialyzer warnings in Elixir. It gives you warnings if something is wrong with your types and such. It can be a bit annoying to understand but it should never lie 
Elixir LS Fork for Visual Studio Code, which can give you Dialyzer warnings in your editor. The Fork seems to have resolved some issues I’ve had with the main ElixirLS extension.
Recently got started with “mix xref callers” which is good when figuring out the impact of reworking things.
ExDoc and doctests I really like too and I didn’t get knto them before I tried to set up a library for release but they are useful way before that.
4
