Exactly. My current team uses TFS for source control, ci builds, tests, work item tracking and reports.
When I first joined, I couldn't believe what a cumbersome mess it was but as I've had to work on some of the infrastructure from time to time I am really impressed how it all fits together and how much can be surfaced right inside Visual Studio. (A separate team maintains our actual instance, thank god.)
The true pain as a developer comes from the poorly thought out UI which makes every little task click heavy. To make things worse, the UI is poorly threaded and seems to prefetch nothing. This means that drilling down into any area, especially the source control view leaves you waiting 1-3 seconds per item you expand.
There's also some weird usability holes, like why after 5+ years is undo unchanged a command still only found in the optional power tools utility?
Right, the UI seems like you're doing work in access and every click opens another tab. Some features are 'nice' (link to workitems etc.), but you have dialogs with tabs with tabcontrols with gazillion other controls and .. yeah. You don't want to use that, basically.
When I first joined, I couldn't believe what a cumbersome mess it was but as I've had to work on some of the infrastructure from time to time I am really impressed how it all fits together and how much can be surfaced right inside Visual Studio. (A separate team maintains our actual instance, thank god.)
The true pain as a developer comes from the poorly thought out UI which makes every little task click heavy. To make things worse, the UI is poorly threaded and seems to prefetch nothing. This means that drilling down into any area, especially the source control view leaves you waiting 1-3 seconds per item you expand.
There's also some weird usability holes, like why after 5+ years is undo unchanged a command still only found in the optional power tools utility?