Laravel has its own naming convention. For example, if your model name is User.php then Laravel expects class ‘User’ to be inside that file. It also expects users table for User model. However, you can override this convention by defining a table property on your model like, class User extends Eloquent implements UserInterface, RemindableInterface { … Read more
I always use a meaningful name unless it’s a single-level loop and the variable has no meaning other than “the number of times I’ve been through this loop”, in which case I use i. When using meaningful names: the code is more understandable to colleagues reading your code, it’s easier to find bugs in the … Read more
For package design, I first divide by layer, then by some other functionality. There are some additional rules: layers are stacked from most general (bottom) to most specific (top) each layer has a public interface (abstraction) a layer can only depend on the public interface of another layer (encapsulation) a layer can only depend on … Read more
I always prefered ID to TableName + ID for the id column and then TableName + ID for a foreign key. That way all tables have a the same name for the id field and there isn’t a redundant description. This seems simpler to me because all the tables have the same primary key field … Read more
I would say that first and foremost: be consistent. I reckon you are almost there with the conventions that you have outlined in your question. A couple of comments though: Points 1 and 2 are good I reckon. Point 3 – sadly this is not always possible. Think about how you would cope with a … Read more
I think you should avoid camel caps. The norm is to use lower case letters. I would also avoid underscores and use dashes instead So your URL should look like this (ignoring the design issues as you requested :-)) api.service.com/hello-world/user-id/x
It comes from the original sql standards, which through several layers of indirection eventually get to an identifier start block, which is one of several things, but primarily it is “a simple latin letter”. There are other things too that can be used, but if you want to see all the details, go to http://en.wikipedia.org/wiki/SQL-92 … Read more
As you noticed, these are Makefile {macros or variables}, not compiler options. They implement a set of conventions. (Macros is an old name for them, still used by some. GNU make doc calls them variables.) The only reason that the names matter is the default make rules, visible via make -p, which use some of … Read more
I suspect the most common values would be camelCased – i.e. <myTag someAttribute=”someValue”/> In particular, the spaces cause a few glitches if mixed with code-generators (i.e. to [de]serialize xml to objects), since not many languages allow enums with spaces (demanding a mapping between the two).
It stands for member. I personally find this convention unhelpful, but it’s subjective.