![]() ![]() “Indeed, the ratio of time spent reading versus writing is well over 10 to 1. This improves the maintainability of the project, and the speed that people can work. Making code more readable is by far the most important reason to use it. There are namely three ways it saves time. ![]() So, how about a vendor-agnostic solution where editors are responsible for utilizing a shared configuration instead? How EditorConfig Helpsĭefining conventions helps everyone throughout a project's life-cycle. You'll bloat your project with unrelated files if you add the configuration for every editor someone might use. mixes tabs and spaces, here's how it looks on GitHub with a tab size of 8.Ī common solution is to share editor settings as part of the project, but this assumes all committers are using the same editor as you, which probably isn't the case.įor Java development alone, the following are all popular choices: ![]() Without consistency, the code can appear untidy and be a pain to read, depending on a user's development environment.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |