@blakeyrat said:
(Actually he got into that whole, "well I consider IDEs a crutch" attitude which is the most ridiculous thing I've ever heard.)
Next time, say “Yes, yes it’s a crutch, and unless you can remember every parameter for every method for every class in the entire API, then you’re handicapped, so use the crutch instead of dragging yourself around by your fingernails.”
@blakeyrat said:
They're significantly worse for me, since
none integrate with VS. SVN at least has TortoiseSVN, which is a decent
interface, but it doesn't do what TFS does (there's no linkage between
your bug database and TortoiseSVN), and it still doesn't integrate with
VS. (Yes, yes, I know there are VS extensions, yadda yadda.) Why should I
have to leave my IDE to get a quick diff? Why should I have to open up
my web browser to see what bug entry was associated with a code
check-in?
There are
[url=http://ankhsvn.open.collab.net/]AnkhSVN[/url] (free, and a full SCC
provider) and [url=http://www.visualsvn.com/visualsvn/]VisualSVN[/url]
($$, and is just a VS-integrated interface to TSVN).
Look in the
TSVN help file under the “bug tracking” index entry. You can set some
properties and have the log window automatically turn things like
“addresses issue #1234” into a link to the bug tracker. It’s still your
web browser, but you don't have to manually look the issue up.
@ObiWayneKenobi said:
And my whole argument wasn't "DI/IoC is a
golden hammer" it was that .NET guys IN MY EXPERIENCE are more likely
to have no fucking idea what DI/IoC even is, or when it would be useful,
or have any desire at all to broaden their horizons by learning them so
they can apply them IF they have the need.
It sounds like you only ever run into VB6 guys who have learned only enough .NET to make their crufty old shit build again.