David Flynn

We use this to collaborate on technical debt / refactoring tasks before they get officially added to TFS. Trello

We use this as it has some great text editing capabilities and a real time saver for when working on various data related tasks. This is simply a great text editor. Sublime Text

Our core systems that we integrate with are using SQL Server 2012 / 2016 database servers. We use database views on core system databases to help build our domain model. Microsoft SQL Server

We use this to collaborate with the DLX team. Our deployment pipeline (Octopus Deploy) sends release notifications to the team on Slack. Slack

We use Postman for all our API testing. Postman is invaluable. We would like to have a team licence so that we can use shared work spaces and test collections. Postman

This is our CD platform. We use TFS for gated-checks and release builds. A release build packages all our components, pushes these packages to Octopus and triggers a release into our Development environment. A suite of integration tests are run and finally if all is successful the team gets a notification on Slack that a new release is available. This can then get promoted through all our non-production environments, Finally, we use offline deployments as we are not yet allowed to promote all the way to production from Octopus. Offline deployments are great as they allow us to retain our tried and tested deployment process but instead, humans become the tentacles when deploying in prod and pre-prod. Octopus Deploy

We use a combination of .NET Core and .NET Framework for our ASP.NET Core APIs. .NET

Increasingly we are using VS Code more and more. It is very handy for working on Javascript, Powershell scrips, TSQL, markdown etc. Often use it's integrated terminals for spinning up APIs, running off tests and running various scripts. Visual Studio Code