In the past couple of months, DISQO has made efforts to address the racial technology terminology in our documentation and code bases. Learn why and how we're executing these efforts.

When documentation is difficult to locate, it's a near-guarantee few (if any) will use it. Last year, we devised a plan to bring documentation into immediate accessibility to all tech team members.

In breaking up our monolith application into microservices, we've had a lot more ground to cover with monitoring. In this article, we discuss all of the ways in which we monitor our microservices.

Retros are part of our DISQTECH Agile process. Learn more about our retros, including active participation, transparency, understanding the purpose of the retro, and keeping open discussion.

Data-informed tech culture enables teams to standardized processes, make decisions faster, and reduce risk. In this article, we'll talk about the ways that DISQO practices this type of culture.

API consumers succeed when there is robust documentation, as we'll cover here. This article is the first of several that will tackle API design topics in depth.

DISQO has a culture of using data-driven design to inform our business decisions. In this article, we walk through the steps we take to run tests on our primary platform, surveyjunkie.com.

Learn how our mandatory WFH policy is not slowing us down, and how we're using this time to push ourselves to be better communicators and colleagues. We'll also touch on how to avoid burnout during this trying time.

The daily standup is an integral part of our agile process at DISQO. Learn more about our daily meetings here.

This step-to-step guide walks you through how to set up JaCoCo and SonarQube for an Android project.