meta data for this page
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
convention_over_configuration [2020/09/26 22:40] – [Naming and Source Code Organization Conventions in JavaCC21] revusky | convention_over_configuration [2020/10/22 18:19] (current) – revusky | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Convention over Configuration (when possible) ====== | ====== Convention over Configuration (when possible) ====== | ||
- | It is our considered view that a tool having a plethora of configuration options can it make it far less usable. Or, at the very least, if there are a lot of configuration options, the neophyte user should be able to ignore them for the most part. One key aspect of this is having sensible defaults that correspond to the typical usage scenarios. Another aspect is simply having naming conventions so that the tool can infer the names of files and their locations, etcetera. | + | It is our considered view that a tool having a plethora of configuration options can make it far less usable. Or, at the very least, if there are a lot of configuration options, the neophyte user should be able to ignore them for the most part. One key aspect of this is having sensible defaults that correspond to the typical usage scenarios. Another aspect is simply having naming conventions so that the tool can infer the names of files and their locations, etcetera. |
===== Naming and Source Code Organization Conventions in JavaCC21 ===== | ===== Naming and Source Code Organization Conventions in JavaCC21 ===== |