Coding is Easy; Communication is Hard

Takeaways

  1. Every Git commit is an opportunity to communicate your intention. What is the one thing this change does? If you can’t describe it in a single sentence, maybe you need to practice writing your words more, but maybe that commit is doing too much. We don’t want stupid commits that free associate fish and grapefruits.
  2. Names matter. They communicate what something is and does. Choosing a descriptive function or variable name does more for code readability than any comments. Is it a fish or a grapefruit?
  3. File structure matters. The structure communicates expectations. Are you choosing sensible directory- and file-names that accurately describe their purpose and contents? Does this directory contain fish or grapefruits?

--

--

--

Code person.

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Learning Docker — The Command Line Interface

Video@Scale: Playback Innovation

Scrum Guide 2020 — How Radical Is the Change From Self-Organisation To Self-Management?

Building a Raspberry Pi Cluster with Docker

Using bind and map in Our Pipeline

What You Need to Measure About th e Portfolio

images/measures/comparingprojectswithnomultitask.png

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Everett Griffiths

Everett Griffiths

Code person.

More from Medium

Your Software Should be Open-Sourced

Securing open source require better programming languages

Async Superpowers: State Machines

An experience refactoring real world Elixir code