Julia Evansthinking today about how much I love Shellcheck's explainer pages for its linter failures https://www.shellcheck.net/wiki/SC2173
every page has:
- problematic code
- correct code
- rationale
- exceptions
Graydon@b0rk Shellcheck's only flaw is not knowing about zsh.
Thom Slattery@b0rk Never seen this before - so cool.
Owen Nelson@b0rk reminds me of that classic format for giving feedback: stop/start/continue.
Stop: things you currently do, but are better to avoid.
Start: missed opportunities, try to leverage them. New ideas.
Continue: the stuff you're doing now which is great, please keep going!
I always liked my managers who used this.
Sandor Szücs@b0rk yeah that's great!
I use a lot of Go and so https://staticcheck.dev/docs/checks/#SA1008 is a great page for me.
I use a lot of Go and so https://staticcheck.dev/docs/checks/#SA1008 is a great page for me.
@sszuecs wait this is so cool, how had I never heard of staticcheck!
Badscrew
Anders Eknert@b0rk I built Regal on similar principles 🙂 https://github.com/StyraInc/regal
My inspiration was mostly Hadolint though. I guess there are a few doing this.
Samantaz Fox@b0rk shellcheck is such a nice tool! It made my day when I discovered it!
Tim WIcinski@b0rk coworkers think i am OCD when i talk shellcheck
Brie 
@b0rk I didn't know about shellcheck, this is really cool!
Wes Jones@b0rk I learned more about writing code for Bash from installing Shellcheck than any tutorial or man page.
Stephen Paulger@b0rk semgrep’s playground is quite nice for that. Most rules have tests for matches and non-matches.
https://semgrep.dev/playground/r/bash.lang.best-practice.useless-cat.useless-cat
Christin White@b0rk @ellotheth it’s so good, I wish every linter had such high quality documentation.
Matt Simerson@b0rk damn straight! Set up shellcheck with your $EDITOR and CI so that a) you know about issues before save and b) in PRs that others submit.
Márton Salomváry@b0rk Definitely one of the best linters out there!