Timeline for What Part of Your Project Should be in Source Code Control?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 19, 2011 at 3:46 | history | made wiki | Post Made Community Wiki by bstpierre | ||
| Nov 19, 2011 at 1:55 | comment | added | Zach | My point is, even if you're only using it for some things (cough source code cough), your colleagues should already know how to use it, so training them shouldn't be increased overhead in using it for something else. | |
| Nov 19, 2011 at 1:51 | comment | added | Andomar | Hehe I'm not arguing against source control, just against blindly using source control for everything. If source control has a very complex workflow and that doesn't add value, I would prefer not to use it. | |
| Nov 19, 2011 at 1:40 | comment | added | Zach | Are you serious? Source control is bad because it requires training for new colleagues? Are you actually saying you'd prefer to work long-term with people who don't know how to use source control and aren't willing to learn? Personally I'd rather flip burgers. | |
| Nov 18, 2011 at 23:51 | history | answered | Andomar | CC BY-SA 3.0 |