Awesome. Thanks for the tips on the use of Crucible.
As far as losing comments in our VCS goes, we don't. What we are going to lose is ALL of the history because someone decided to change from SVN to Jira (I don't know if there's a migration path there but the people "in charge" said no attempt will be made). Only comments in the code will survive the onslaught. The same goes with our ticketing system. This will be the 3rd time they've changed it and the information in the tickets important... and yet they'll be making no migration attempt there, either.
The fortunate thing on that latter part about the ticketing system is that it is SQL Server based. You can bet that I'll be preserving that little database for a long time to come.
Also, totally agreed that a DIFF on an SP to see what the changes were is the absolute best but, like I said, when people change VCSs, it's a bit difficult to do for anything that straddles the change. Of course, that's only a temporary issue but, again, any notes from the previous VCS will be lost and the comments in the code will not. And, yeah... sometimes it is actually important to know what a ticket number from 28 changes ago actually was. Of course, they've also shot that to hell by changing ticketing systems for a 3rd time in less than 7 years, all without any migration effort.
is pronounced "ree-bar
" and is a "Modenism
" for R
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
"Change is inevitable... change for the better is not".
"If "pre-optimization" is the root of all evil, then what does the resulting no optimization lead to?"
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)