2 ms·
I think anything that reduces the number of different places that information or discussion may happen is good. The thought of having a mix of code/code review/
by dan-robertson 5y ago
I think anything that reduces the number of different places that information or discussion may happen is good. The thought of having a mix of code/code review/wiki/other wiki/email/chat/list archives/jira/shared inbox/trello is not appealing to me. There’s some continuum where adding a system changes things from good to annoying and I think my own feelings put that place more towards the “fewer systems” end than where other people put it.
- deleted 5y ago[deleted]
- simonw 5y agoTool proliferation is definitely a problem, but at larger organizations I'm not sure how feasible it is to keep everyone using the same small set of tools. At my last large employer I ended up putting together a custom search engine that searched across a bunch of different places where important stuff ended up - Google Docs and GitHub Wikis and Markdown-in-GitHub and Confluence and Salesforce Support and a mailing list archive and a few others. Having a single place to search really helped: I had thought that we had bad documentation, but it turned out we actually had pretty good documentation just distributed across too many different places.
- zikzak 5y agoWe used to use Unfuddle for source control and issues/PM then went to self hosted TFS but kept issues and pm in Unfuddle. Then we decided that was working so well for Dev, everyone should use it. But people didn't like Unfuddle. So now we have Asana. Everyone but Dev likes it, there's no ticket numbers, and it's confusing but at least the stakeholders are using it?
- royandre 5y agoWe have made a solution for assigning task numbers in Asana. Will prioritize us posting how do add it.