public

Consider the concepts you learned to write this code, and try to capture that in names. Consider the <em>why</em> or <em>how</em> something is used instead of <em>what</em> it is. <code>initial_sign_up_profile</code> says a lot more than <code>profile</code>, and <code>lock_stats_table_for_data_export</code> says more than <code>lock_db</code>.

It’s our job to translate between those <a href="https://thoughtbot.com/blog/acceptance-tests-at-a-single-level-of-abstraction">levels of abstraction</a>.

A good name allows you to describe the functionality in a way that doesn’t require the user to know every internal piece of the system.

A good test <a href="https://thoughtbot.com/blog/the-self-contained-test/">tells a story</a>.

Keeping all of that setup inline makes that test much more readable. It’s staggeringly not DRY, but <a href="https://thoughtbot.com/blog/the-case-for-wet-tests/">DRY isn’t a useful goal for tests</a>.

The goal is code that we can easily understand and confidently change to give users the best possible software.

With more than 10,000 Shopify employees,