Timeline for Python - Architecture for related instance attributes
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 11, 2017 at 15:22 | comment | added | enderland | One significant improvement to your dictionary approach would be defining constants for the keys and using them instead of the sting literals. That removes a lot of the negatives associated with that and also makes things easier to test (you could validate all keys are unique in a test, for example). | |
| Feb 3, 2017 at 19:03 | vote | accept | Johndt | ||
| Feb 1, 2017 at 5:10 | history | tweeted | twitter.com/StackSoftEng/status/826658914938843137 | ||
| Jan 31, 2017 at 15:17 | answer | added | Jonathan Eunice | timeline score: 1 | |
| Jan 31, 2017 at 6:52 | history | edited | Johndt | CC BY-SA 3.0 | added 1 character in body |
| Jan 31, 2017 at 5:45 | comment | added | Todor Todorov | Kudos for a well laid out question! But I doubt you will get a satisfactory answer. Form what standpoint should the approach be better or preferred? OOP advocates will probably go with the last one, developers that have spent years in procedural programming will choose something else. In the end the best approach is the one you feel most comfortable with. | |
| Jan 31, 2017 at 4:24 | review | First posts | |||
| Jan 31, 2017 at 9:27 | |||||
| Jan 31, 2017 at 4:21 | history | asked | Johndt | CC BY-SA 3.0 |