Here's a cute lint feature I haven't seen before: an estimate of how long an issue would take to fix!
Link: https://codeclimate.com/github/Wilfred/metawiki/issues?category=duplication&engine_name%5B%5D=structure&engine_name%5B%5D=duplication
(It's a really small project, so 2 hours seems pessimistic.)
miniblog.
Related Posts
When I moved back to the UK, I ordered SIMs for both myself and my wife. We ended up with consecutive numbers!
It's really convenient sometimes.
I see people advocating for writing a FAQ, but I really struggle to write one from scratch.
The best FAQs are written as a response to, well, frequent questions.
How do you populate the initial FAQ?
It seems really odd to me that git uses 'cached' terminology for staging. For example, `git add somefile.rs; git diff --cached`.
Caching implies state that you don't mind losing. There's very little state I want to lose in version control!
