Designing an application interface in today's world is difficult. Many products offer native implementations for iOS and Android, as well as cross-browser HTML versions.

For nearly two decades, I’ve been writing some form of code. But, the primary reason I code has changed over time. In the beginning, I wrote code simply to make something real.

When you think of baseball parks in the early part of the twentieth century, you might think of Wrigley Field, Fenway Park, Yankee Stadium, or Ebbets Field.

As developers and programmers of all stripes can attest, staying current in our industry is a moving target, and a fast moving one at that.

We recently reached out to our customers with a survey on how and why they use DoneDone. We received lots of informative feedback, but one thing really stood out.

The programming industry is very much about what's new—the hottest language, technique, or framework. But, the best programmers—the ones that are going to stick around for the long haul—rely on a few timeless principles.

Last week we received an email from a DoneDone customer who was experiencing a strange file upload error.

We usually talk about refactoring code with the same kind of pedantic approach we do with all other kinds of software writing.

Over the past few years, we've regularly built new integrations into DoneDone. Most of our integrations use webhooks, which are callbacks sent from a remote third-party service to your application.

There's a benefit to writing strict code. In this post, Ka Wai Cheung, explains why.

In the past, I've often wrestled with designing an optimal relational database model to represent users in a multi-tenant system.

DoneDone is built using ASP.NET, meaning our development environment is Visual Studio on Windows.