Reputation
Top tag
Next privilege 50 Rep.
Comment everywhere
Badges
1 6
Impact
~36k people reached

  • 0 posts edited
  • 0 helpful flags
  • 10 votes cast
May
20
awarded  Popular Question
Jul
29
awarded  Necromancer
Mar
23
comment Why bother with detailed specs?
Software specs are great for programmers to use for themselves, but even better to use for customers such that they define their expectations of the end product concretely... before you start working your magic.
Mar
4
comment How to separate development process and configuration management aspects of SVN?
@Wyatt Well the SCM is for keeping working released ordered. Maybe a new working version isn't acceptable to the customer, so it is necessary to revert back the the previous release.
Mar
3
awarded  Teacher
Mar
3
answered What is the most frequently used design pattern?
Mar
3
revised Is using SVN for development and CM a bad practice?
added 30 characters in body
Mar
3
comment Is using SVN for development and CM a bad practice?
@Anna CM is configuration management. The question body has been edited to reflect this.
Mar
3
revised Is using SVN for development and CM a bad practice?
added 260 characters in body; added 58 characters in body
Mar
3
comment How to separate development process and configuration management aspects of SVN?
@chrisaycock I have edited the question body to answer this.
Mar
3
revised How to separate development process and configuration management aspects of SVN?
added 452 characters in body; deleted 1 characters in body
Mar
3
asked How to separate development process and configuration management aspects of SVN?
Mar
3
revised Is using SVN for development and CM a bad practice?
deleted 443 characters in body
Mar
3
awarded  Scholar
Mar
3
accepted Is using SVN for development and CM a bad practice?
Mar
3
awarded  Supporter
Mar
3
revised Is using SVN for development and CM a bad practice?
added 424 characters in body; added 21 characters in body
Mar
3
awarded  Student
Mar
3
comment Is using SVN for development and CM a bad practice?
Well its not just about me, its about 65% of the company (these people all adhere to our SVN policy, including the person who thinks the current way is wrong). Your comment is along the lines of what I am trying to dig into, though. Since non- "pure SW" people use SVN at our company, is it reasonable to diverge into two separate tools in order to increase simplicity by having two distinct tools with two distinct purposes? Do the pros of this, in your experience, outweigh the cons?
Mar
3
comment Is using SVN for development and CM a bad practice?
He thinks that CM should mean jumping from one working revision to the next. Reverting a file from rev. 143 to rev. 89 introduces guesswork when trying to get a working project (maybe rev. 112 was a mid-stage bug-fix update that would break the runtime .exe).