Well written tests can drive the development of software, serve as a quality control mechanism, and document functionality for other developers working on the same codebase. Style matters when it comes to writing tests specifically because tests are documentation of how your methods and classes are expected to work. Specs that obfuscate the functionality under test are counter productive.
I finished re-tooling my career at the Turing School of Software & Design this past January. Now at roughly six months in the world as a Turing Alum and two months as an engineer at Ibotta, I wanted to share some additional ideas with perspective code school students, current Turing students, and recent graduates.