It stands for Implementation. It’s a Java convention. Often in java (particularly J2EE) you will get an object from some factory, and then use it. That object’s type is often given to you as an interface, so that you don’t need to know the actual class, just its methods. An impl class is usually a … Read more
In “Code Complete,” Steve McConnell notes that “Number” is ambiguous. It could be a count, or an index, or some other number. “But, because using Number so often creates confusion, it’s probably best to sidestep the whole issue by using Count to refer to a total number of sales and Index to refer to a … Read more
I believe there is a continuum of complexity, therefore corresponding organizations. Examples follow, choose depending of the complexity of your project and your utilities, and adapt to other constraints : One class (called Helper), with a few methods One package (called helper), with a few classes (called XXXHelper), each class with a few methods. Alternatively, … Read more
As with most things in programming, you can use any name you like. But, as with most things in programming, names matter and good names are hard. Here’s how I name segues… Good segue names Name segues as you would name action methods. Name segues by what they will do. Good segue name examples: addUser … Read more
As noone has yet answered the question, I’ll post on what I have decided in the meantime. Just for the record, I have pretty much decided on calling most data store classes repositories. First, it appears to be the most neutral, non-technical term from the list I suggested, and it seems to be well in … Read more
To remember camel case you have to think about the shape of the capital letters. They are like the humps of a camel as you can see in this image. Pascal Casing – capitalizes each word: ThisShouldBePascalCase Camel Casing – is similiar to pascal case but the first word is not capitalized: thisShouldBeCamelCase You can … Read more
Swift 3 API guidelines state that “Names of types and protocols are UpperCamelCase. Everything else is lowerCamelCase.” https://swift.org/documentation/api-design-guidelines/ Ideally your global constants will be located within an enum, extension, or struct of some sort, which would be UpperCamelCase, and all properties in that space would be lowerCamelCase. struct LoginConstants { static let maxAttempts = 10 … Read more
I would suggest using “toggle” as although it doesn’t exactly mean Enable/Disable it is commonly used as such in the context of user interfaces (as @Pekka mentioned).
In most cases a simple GetFoo suffices as the caller doesn’t need to know that you are creating and caching it. That’s what encapsulation is all about. However, in some circumstances, creating is an expensive operation, so it’s useful to know that you may be creating something on demand and in some cases it will … Read more
I’ve noticed a lot of frontend developers are moving away from css and js in favor of styles and scripts because there is generally other stuff in there, such as .less, .styl, and .sass as well as, for some, .coffee. Fact is, using specific technology selections in your choice of folder organization is a bad … Read more