George Shuklin
Jul 21, 2017 · 1 min read

Thank you. Verbosity is a separate issue. It’s the same as for any other text — you may say something in two sentences, or you may spend two pages to say precisely the same.

I’ve tried to to catch differences in approaches toward code. Some guys extremely excited when they could made such complicated thing in such compact way. It’s like ‘∇ ċ B = 0’ in physics. It looks beautiful, but you need to have whole semester to understand it. Others find such approach scary. It’s not about been cryptic or verbose, it’s about attitude toward stanza. Should reader spend significant time on each or not?

P.S. I don’t like this way of test definition. If test is trivial, those descriptions only take time from reader. If test is not trivial, those descriptions wouldn’t be sufficient. Well-documented code will have a big comment or docstring with explanation for complicated test. Well-engineered code wouldn’t have a big comment as it wouldn’t have complicated tests.

)
    George Shuklin

    Written by

    I work at Servers.com, most of my stories are about Ansible, Ceph, Python, Openstack and Linux.