Write READABLE CODE and become a better developer! скачать в хорошем качестве

Write READABLE CODE and become a better developer!

How folks, welcome to Not Only Code! I'm Gregory Witek and in this video I'm talking about readable code: what does it mean that code is readable? How to write readable code? I explain why code readability matters and I present 5 techniques that you can start using today, that will make your code better and will help you to become a better software developer. 🎥 Timeline: 0:00 Introduction 0:45 Why code readability is important 2:40 Using white space 3:40 White space example 6:10 Happy path first 7:40 Happy path example 9:00 Use early returns 9:50 Early return example 11:14 Don't reassign variables 15:30 don't use name "data" 16:20 Summary If you have any questions or comments, drop me a message: ✉️ gregory@notonlycode.org 🌏 https://www.notonlycode.org 🐦 @GregoryWitek 📚Resources: when preparing this episode I started from learning how we, humans, read in general. I've always known that reading is a complicated process, and reading about reading (yup!) helped me to understand both the visual and semantic aspects of readable code. https://en.wikipedia.org/wiki/Subvoca... - most of us have inner monologue (kind of a voice in our head) and when we read, we vocalize the text in our mind; this process is called subvocalization https://en.wikipedia.org/wiki/Saccade - when reading, our eyes do not move smoothly from one word to another, but rather jump and stop between them in so called saccadic movements   / line-of-sight-in-code   - post by Mat Ryer where he explains the idea of aligning the happy path to the left. This concept helped me understand better why early returns improve readability https://www.poodr.com/ - "Practical Object-Oriented Design in Ruby", a book by Sandi Metz. This book is about much more than just readable code, but I recommend it to every developer, even if you do not use Ruby at all