Timeline for How do you normalize coding style among multiple isolated developers?
Current License: CC BY-SA 4.0
23 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 12, 2020 at 1:37 | answer | added | Mecki | timeline score: 0 | |
| Jan 3, 2020 at 6:00 | history | tweeted | twitter.com/StackSoftEng/status/1212977040435093504 | ||
| Dec 26, 2019 at 17:34 | answer | added | Chuck Krutsinger | timeline score: 0 | |
| Dec 26, 2019 at 11:09 | history | protected | gnat | ||
| Dec 26, 2019 at 10:29 | answer | added | lost faith in stackoverflow | timeline score: 0 | |
| Dec 26, 2019 at 7:35 | answer | added | Lie Ryan | timeline score: 3 | |
| Dec 26, 2019 at 2:10 | answer | added | ian | timeline score: 1 | |
| Dec 24, 2019 at 14:02 | answer | added | Manziel | timeline score: 5 | |
| Dec 24, 2019 at 10:32 | vote | accept | Vilx- | ||
| Dec 24, 2019 at 10:07 | answer | added | pjc50 | timeline score: 3 | |
| Dec 24, 2019 at 1:27 | comment | added | Mateen Ulhaq | For code style, configure a formatter. Or use an opinionated formatter like black so that everyone is (un)happy. For other stuff you would probably need to create an internal "coding guidelines" document, preferably democratically written. | |
| Dec 23, 2019 at 23:18 | comment | added | Vilx- | @SrinathGanesh - And who in our little organisation would be competent enough to decide such matters besides us developers? Our management is smart enough not to get involved in such matters. If we need their support, we will ask for it and get it, but otherwise such technical details are our own to sort out. | |
| Dec 23, 2019 at 20:34 | comment | added | Srinath Ganesh | Its NOT developers choice BUT Organisations choice (of code style). | |
| Dec 23, 2019 at 20:01 | comment | added | Vilx- | @Steve - No, no, naming conventions (as in camelCase), spaces, etc. are OK. It's the what to name that gives a problem, not how to spell it. And that's also what I mean by "coding standards" here - not the form, the content. | |
| Dec 23, 2019 at 17:50 | review | Close votes | |||
| Jan 3, 2020 at 3:05 | |||||
| Dec 23, 2019 at 16:51 | history | became hot network question | |||
| Dec 23, 2019 at 15:10 | answer | added | GHP | timeline score: 6 | |
| Dec 23, 2019 at 14:43 | comment | added | Steve | I wonder whether the answer is really "coding standards"? It sounds like what you all really need to do is get to know each other's code. No naming convention or arrangement of code files will really substitute for knowing how the application works - what concepts it employs, and the intricacies of its behaviour. Naming conventions will help a stranger understand an application, about as much as standardising on metric bolts allows the stranger to engineering to understand different types of engines. | |
| Dec 23, 2019 at 13:59 | answer | added | Filip Milovanović | timeline score: 4 | |
| Dec 23, 2019 at 9:09 | answer | added | Pete | timeline score: 13 | |
| Dec 23, 2019 at 8:34 | answer | added | gnasher729 | timeline score: 5 | |
| Dec 23, 2019 at 1:11 | answer | added | Robert Harvey | timeline score: 89 | |
| Dec 23, 2019 at 0:49 | history | asked | Vilx- | CC BY-SA 4.0 |