Team Foundation Server

Raised as a usability problem by 14 people on Hacker News over 11 years (2010–2020), in 13 threads.

People raised many different problems with Team Foundation Server, but no single problem has yet been raised by 3 people in 3 different months and threads.

Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.

The newest 15 complaints

Source control server is so slow it is unbearable to use2020-11-24
Forced embedding in Visual Studio adds frustration to daily use2020-10-12
Constant edits to project and team paths make the setup a pain to manage2018-10-05
UI is busy, slow, and takes many clicks to reach anything2018-03-29
Bugs block all developers from committing; workarounds replace patches, and commits take minutes2017-09-22
Sends far too many files constantly; branching and merging are expensive2016-03-09
Slow operations, painful merges and conflicts, and a terrible UI2015-06-05
Simple file operations like rename, add and delete take 20-30 seconds or more2014-06-04
Hard to find changed files and unclear what is being committed2014-01-28
Viewing a file's history requires opening each changeset individually2013-07-17
Programmers had to update ticket hours several times a day, which was tedious and often forgotten2011-12-01
Offline mode works differently across versions and reconnecting causes lost local changes2011-09-12
Offline mode is unintuitive and hard to work through when the server goes down2011-09-12
Software is very slow, hard to script, and confusing to use2011-09-11
Files stay read-only and Pending Changes goes stale or confusing across Visual Studio instances2010-06-26