On clean code

I took the opportunity to read through some of Clean Code: A Handbook of Agile Software Craftsmanship. There was a lot of discussion on different perspectives regarding “clean code”. Some mentioned that clean code is “enjoyable” and “pleasant to look at” while others focused on readability and how fast a new developer could understand what the code does. Another perspective was that clean code means minimum duplication and entities, while ensuring objects and functions clearly do only one thing instead of several.

Following that reading, as an actionable decision I will try to stick to better naming conventions and try to make a key for myself at the top of my code. I sometimes am guilty of getting lost in using verbs or switching to snake case. What I definitely now want to avoid is having functions do more than one clearly named task. I sometimes find myself rereading my functions to understand what they do.

Published by

Zoha Zainab Akbarzadeh

Interest in LMS, game development, and health. (If you have a project that combines any of the two, shoot me an email. I'd love to discuss!) Environment and sustainability enthusiast. Gardener, artist, and computer scientist.

Leave a Reply

Your email address will not be published. Required fields are marked *