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
I go for fooCount because it is straightforward, and I think the word “count” is the shortest and the best that describes it, not “number of” or the like. I go for FOO_COUNT if it you need to store it final and static(if you don’t need to change it/if it is a constant). (all caps … Read more
It is all about consistent semantics; In your question title you use getting data. This is extremely general in a sense that you need to define what getting means semantically significantly unambiguous way. I offer the follow examples to hopefully put you on the right track when thinking about naming things. getBooks() is when you … Read more
public boolean userExists(…) Would be my prefered. As it makes your conditional checks far more like natural english: if userExists … But I guess there is no hard and fast rule – just be consistent
IMO: status == how are you? [good/bad] state == what are you doing? [resting/working]
What you are doing now is fine, and I highly recommend you stick with your current syntax, being: context + verb + how I use this method to name functions/methods, SQL stored procs, etc. By keeping with this syntax, it will keep your Intellisense/Code Panes much more neat. So you want EmployeeGetByID() EmployeeAdd(), EmployeeDeleteByID(). When … Read more