Name your Interface what it is. Truck. Not ITruck because it isn’t an ITruck it is a Truck. An Interface in Java is a Type. Then you have DumpTruck, TransferTruck, WreckerTruck, CementTruck, etc that implements Truck. When you are using the Interface in place of a sub-class you just cast it to Truck. As in … Read more
A ‘$’ in a variable means nothing special to the interpreter, much like an underscore. From what I’ve seen, many people using jQuery (which is what your example code looks like to me) tend to prefix variables that contain a jQuery object with a $ so that they are easily identified and not mixed up … Read more
All three are not the conventions. Use com.stackoverflow.mypackage. The package names do not follow camel casing or underscores or hyphens package naming convention. Also, Google Java Style Guide specifies exactly the same (i.e. com.stackoverflow.mypackage) convention: 5.2.1 Package names Package names are all lowercase, with consecutive words simply concatenated together (no underscores). For example, com.example.deepspace, not … Read more
I’d go for purchase-rest-service. Reasons: What is “pur chase rests ervice”? Long, concatenated words are hard to understand. I know, I’m German. “Donaudampfschifffahrtskapitänspatentausfüllungsassistentenausschreibungsstellenbewerbung.” “_” is harder to type than “-“
The recommended naming and capitalization convention is to use PascalCasing for constants (Microsoft has a tool named StyleCop that documents all the preferred conventions and can check your source for compliance – though it is a little bit too anally retentive for many people’s tastes). e.g. private const int TheAnswer = 42; The Pascal capitalization … Read more
In general, methods that end in ! indicate that the method will modify the object it’s called on. Ruby calls these as “dangerous methods” because they change state that someone else might have a reference to. Here’s a simple example for strings: foo = “A STRING” # a string called foo foo.downcase! # modifies foo … Read more
There isn’t really a standard name for this case convention, and there is disagreement over what it should be called. That said, as of 2019, there is a strong case to be made that kebab-case is winning: https://trends.google.com/trends/explore?date=all&q=kebab-case,spinal-case,lisp-case,dash-case,caterpillar-case spinal-case is a distant second, and no other terms have any traction at all. Additionally, kebab-case has … Read more
Update (Jul 2021) It’s been quite a while since my original answer (almost 12 years) and best practices have been changing a lot during this time. So I feel inclined to update my own answer and offer different naming strategies to the readers. Many comments and answers point out that the naming strategy I propose … Read more
For me is better to have a schema that you can map directly to code (easy to automate), mainly because code is what is going to be at both ends. GET /orders <—> orders POST /orders <—> orders.push(data) GET /orders/1 <—> orders[1] PUT /orders/1 <—> orders[1] = data GET /orders/1/lines <—> orders[1].lines POST /orders/1/lines <—> … Read more
_ has 3 main conventional uses in Python: To hold the result of the last executed expression in an interactive interpreter session (see docs). This precedent was set by the standard CPython interpreter, and other interpreters have followed suit For translation lookup in i18n (see the gettext documentation for example), as in code like raise … Read more