Clean Code — Naming

  1. “How can you consider yourself to be a professional if you do not know that all your code works?”
  • It’s easy to guess around at an answer to a coding problem and stumble upon the right answer. You shrug and say “well, if it works, it works!”, and move on. As professional developers, we must know how our code works and understand what it’s doing. The best way to do that is to declare the “boundaries” for how the code should operate by writing a test before the production code.
  • As I have said before, I like having processes I can follow in my workflow. The Red/Green/Refactor cycle is a great way to efficiently produce good quality code.
  • Writing tests after you have written the code is just confirming the biases you have already placed into your code. Always write your tests first.

--

--

--

I’m a software developer hanging out in SC

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

Recommended from Medium

Dockerize your Django and React App

Hacking Trakr to track inventory of local toilet papers

Connecting Google Sheet In Loopback 4 to read/write to Google Sheet.

Add / Integrate Jira Service Desk Support Requests in an Ionic Angular App

Simple Design

Why @HRCrossingis different? 🤔

Creating VPC using Terraform

Segment based Notification targeting for millions of users

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
Caleb McQuaid

Caleb McQuaid

I’m a software developer hanging out in SC

More from Medium

Clean code is not a choice

Improving the Usability of Refactoring Tools for Software Change Tasks

Guide to rock solid, bug free, quality software.

My top three technology podcasts