Access our documentation and keep up with the DISQO Developer blog to see how we're innovating
At DISQO, the Technical Requirements Document (TRD) forms our path for project development and maintenance. The TRD is a definitive source of truth that bridges the gap between what the business requires and what the engineers will build.
Lead Software Engineer Davit Siradeghyan details how his team adopted SwiftUI for our iOS application. Read how adopting SwiftUI fits in with our striving for engineering excellence, and step-by-step how we went from planning to confronting issues, to applying our findings.
Last year, DISQO started some significant work around defining and acting from our value system. I asked several of my colleagues within our engineering department what experiences come to mind for each of the DISQO values.
DISQO's engineering team engages in the principles of collaborative engineering to build knowledge-sharing, creative solutions, improved internal communication, a sense of product ownership, and trust.
Learn how DISQO adopted a Shift Left Testing mindset, from having a separate QA team to integrating testing into the software engineer role.
DISQO introduced Request for Comments (RFCs) within our engineering department in April 2020. RFCs enable members of our team to propose new products and protocols, and give and receive input on these proposals.
Earlier this year, we all started working exclusively from home. Now, we're checking in with six individuals in the engineering organization to see how it's been for them.
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.
The DISQO Audience API allows you to create, modify, and send surveys to panelists via our endpoints.
The CoReg API verifies if an email address is valid by checking email format, as well as checking if the email address already exists in our system and/or exists on email address lists submitted by CoRegs.