+1 to this.
I once worked on a 500k LOC C++ distributed system for the Telecom industry
that only had new() and delete() calls on six lines. Everything else was done
via the RAII pattern with std:: The net effect was that even in such a large
system, we recorded only three memory leaks in six
While you can debate the "broken windows" theory
(https://en.wikipedia.org/wiki/Broken_windows_theory) I think it has relevance
to code warnings: the more warnings you tolerate, the more likely you are to
end up with other undesirable things in your code. My preference has always
been to treat
My suggestion is that a project should focus its efforts on only those things
where it brings additional value. Creating a custom blog, even with something
simple like Jekyll, adds no value versus using Medium with a cross-post to
WeChat.
CM
--
Cliff McCollum mailto:mccol...@amazon.co.uk>>
Sof
