![]() As code reviews and new hires are a constant, this savings in developer time translates to real cost savings for the business over time.Īt the very least, a project in any language should add an EditorConfig. For maintenance, code reviews are simpler, as there are less stylistic changes from developer to developer. It increases the chances the new developer has previous experience developing, reading and writing code in that format. New hire ramp-up time can be reduced if your codebase is in a popular format. Save time in both new developer on-boarding, as well as on code maintenance. Time is money, whether it’s your time or the company’s. I had noticed the benefits of this before, but had a hard time putting it into words what an excellent way to demonstrate it! He illustrates this by showing that if all the characters were replaced with X’s, when code is formatted properly, you can still recognize what’s happening. ![]() It’s the concept that you should be able to generally tell what’s happening in a function just by the shape of the code blocks. ![]() In Jason McCreary’s book Basecode, he does an excellent job of explaining a concept which Kevlin Henney has coined “ visual honesty”. Your brain isn’t distracted by the personal preferences of the previous developer. – Spacing that could go anywhere and everywhereĮasier to read code comes from using a consistent code style. – Opening brackets on new line or same line Focus on what’s important (getting things done) and stop debating: If you’ve ever worked with another developer or worked on a team, no doubt you’ve debated coding styles. Let’s go over the benefits of following a coding standard, how to enforce it, and look at how modern tooling and new features in IDE’s like PHPStorm makes it nicer than ever before. Following coding standards in PHP is now easier than ever.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |