<author>/<type>/<ticket>/<title>
revett/feature/24101/skeleton-service-for-email-sender
GitHub username.
bug - Code changes linked to a known issue
feature - New feature
refactor - Code refactoring
spike - Experiments
Ticket/story ID.
- Use
kebab-case
- Keep it concise
wildlyinaccurate just my opinion of course I'll try to back it up with usefulness. I think it is actually very constructive to standardize as much as you can. The first benefit would be that if you do not really KNOW the name of something, if you are intelligent and observant you should be able to guess at a name hence saving you time. Another real benefit is that if people actually name it to what it actually is or does, you don't need to read the entire code base to figure this out, hence saving even more time. (Of course a ton of people are not skilled in reducing the main concept or keywords of an item but this should be improved) Other benefits are more stylistic but have a basis in human nature I believe. If you look at all the names they would be much more uniform and pleasant to look at. The example I will pose is walk into a very organized grocery store in which all the products are lined up and moved to the front of any and all shelves now contrast this against a grocery store that just doesn't give a shit and all the shelves are just in disarray such as your local KMart. I would be curious if I am the only one that would, without a doubt and without any hesitation go ONLY to the organized grocery store instead of the "shit" one. This is one of the perspectives that makes me want to quit computers. There are way too many ways to skin a cat and so many people just ignore standards or don't want to spend the time to figure out the "better" way to accomplish something.