naming-conventions

I currently use a simple convention for my unit tests. If I have a class named "EmployeeReader", I create a test class named "EmployeeReader.Tests. I then create all the tests for the class in the test class with names such as: Reading_Valid_Employee_Data_Correctly_Generates_Employee_Object Reading_Missing_Employee_Data_Throws_Invalid_Employee_ID_Exception and so on. I have recently been reading about a different type of naming convention used in BDD. I like the readability of this naming, to end up with a list of tests something like: When_Reading_Valid_Employee (fixture) Employee_Object_Is

Is it better not to name list variables "list"? Since it's conflicted with the python reserved keyword. Then, what's the better naming? "input_list" sounds kinda awkward. I know it can be problem-specific, but, say I have a quick sort function, then quick_sort(unsorted_list) is still kinda lengthy, since list passed to sorting function is clearly unsorted by context. Any idea? I like to name it with the plural of whatever's in it. So, for example, if I have a list of names, I call it names , and then I can write: for name in names: which I think looks pretty nice. But generally for your own

Let's suppose that we have this situation: Tables in database: Country (id, country_name), Person (id, login), CountryManager (id_country, id_person), CountryStakeholder (id_country, id_person) If we had to create the model from the database, using Entity Framework Database-First, in VS we'd have a class like this: class Country { int id; string country_name; virtual ICollection<Person> Person1; // Navigation Properties virtual ICollection<Person> Person2; // ---------||---------- } I've simplified the code a lot, but hopefully you got the point. Seems that when Entity Framework deals with

I am deciphering someone else's code and I see the following: def get_set_string(set_): if PY3: return str(set_) else: return str(set_) Does the underscore AFTER the variable mean anything or is this just a part of the variable's name and means nothing? No semantics are associated with a trailing underscore. According to PEP 8 , the style guide for Python, users are urged to use trailing underscores in order to not conflict with Python keywords and/or Python built-ins: single_trailing_underscore_ : used by convention to avoid conflicts with Python keyword, e.g. Tkinter.Toplevel(master, class_=

I want to create an interface for "Items". Typicaly I would name an interface by adding and "I" prefix to a base word. But in this case my base word already starts with an I. Here are a couple ideas I've had IItem : Two I's Iitem : Vary the case ItemInterface : Skip the I prefix and write out Interface What looks the best? Has anyone else run into this problem. If so what did you do? Although hard to read, IItem would be in line with some existing " II " interfaces: IItem in Windows Mobile 6.5 IImplicitResourceProvider IISAPIRuntime Simply IItem . There is no need for an exception. Interfaces

When dealing with MySQL, I typically use the BOOLEAN type, which is equivalent to TINYINT(1), or 1/0 In most languages I work with, true/false is preferred When displaying forms, sometimes "Yes / No" makes more sense enum Bool { True, False, FileNotFound }; http://thedailywtf.com/Articles/What_Is_Truth_0x3f_.aspx In code: true/false. In the UI: Yes/No or OK/Cancel true and false makes a lot more sense to me, in code - partly through familiarity, I'm sure. I suspect I'd get used to yes and no pretty quickly. 1 and 0 really doesn't work for me though. Consider the expression age == 5 It's a test