| Company culture was a huge part of it - lack of owner interest, previous architect apathy, intense micromanagement, ticket/maintenance focus encouraged small targeted fixes instead of necessary rewrites, circular DLLs heavily complicated development. And brain drain - not many developers (or engineers or anyone else) willingly stay in environments like this. So the people who have spent years learning the application and how to maintain it find other work, and are replaced by people who have to analyze the system anew. --- A little more targeted: - TFS 2013 has AD integration, but it works in the dumbest way possible - you can't just add someone to an AD security group and they get TFS permissions, nope you have to go into TFS and find their AD account and add them. - It's difficult to debug websites on IE8 because it doesn't have modern debugging tools. Would it be possible at all to have a browser release with the IE8 engine and the IE11 debugging tools? (I'm currently working at a job with an IE8 dependency on a web app, so I understand why it's still around.) - Sharepoint Online is a decent document repository, and TFS is a decent document repository - both have their advantages and disadvantages. But they in no way integrate. This caused major issues when I was providing Ops documentation from a Sharepoint Online site, trying to work with Devs putting their documentation in our local TFS. (Working with either in Jira is beyond painful) --- Unrelated, I wish WDS and WSUS were more integrated - when I push an image from WDS, I want it to have all security patches slipstreamed in from WSUS. Instead, I deploy an image with one and use the other to patch it. |