On Thu, 30 Jun 2011 20:10:25 +0200 Stephan Beal sgbeal@googlemail.com wrote:
On Thu, Jun 30, 2011 at 7:56 PM, Dimitar Zhekov dimitar.zhekov@gmail.comwrote:
(The "40 years wisdom" which will not allow me to keep an .xml or .sql file from another team permanently open in my session was nice. Should I ask a colleagues of mine, which does have 40 years of experience? :)
By all means - the insights of someone who's been doing this since before StarWars (that's '77, for you young 'uns) are always worth listening to.
Well he's assistand-director (not sure it's the right term), though still doing some programming, so I can't just go and ask him questions from the top of my head. But there can be no doubt that our company's practices were approved, if not heavily influenced, by him, and by our previous (now retired) director, also a former programmer. So let me tell you how we do some things relevant to this discussion:
It's normal to keep integration specs, schemas etc. from other projects open, without copying them under the project tree. In fact, making local copies of some files is explicitly forbiden - I can't say more than that, for obvious reasons.
'tis a practice for each developer to compile the modules (s)he is currently responsible for with debug info, and everything else without. And when developing new functionality, it's often initially under a #define, fully compiled and running only for the respective developers. Both things are managed with the project files, so they are under a separate backup plan, not source control.
As you can see, your views are not universal. Please don't ask me any specific questions, and there's also no need for suggestions about improving out practices.