I’m a firm believer in writing code using naming conventions, patterns and style that ensures that the code is human readable, to the point of getting pedantic about function naming even in ways that eliminate a need for comments. Code never lies, comments are thus very much disposable.
That’s why I prefer more verbose code that anyone can read over terse and optimised code that not everyone understands. Advanced code that uses things like maps and reduce and LINQ are chances for people to learn, but should not be over-used if native code will do the same job, because all code maintainers need to be able to be comfortable with your test code. That said, code documentation metadata , and in comment links to help people find supporting spec docs is super useful too.