While it’s great to be fast and agile with code, you need to get the design right early on. Without it, your great products are merely good.

Bob Kruger, our SVP Engineering, provides actionable advice to software developers. Read Bob's post to learn more.

The DNN product team is a distributed organization, described in a previous blog post. While desirable to have all development and QA done in a single location, we found good alternatives in the hiring of topnotch people in various other geographies. …

Periodically, while in the midst of our many projects at DNN Corp., I think about how the Engineering organization is performing. We don’t have a very big team, but we are quite effective despite areas in which we can definitely improve. How things have changed since I started in tech in 1977. At that time, we all wanted development centralized. We had email for communications and multi-user systems which enabled concurrent access to code, specs, and tests. However, white-boarding was not yet in vogue, nor were convenient online meeting rooms, and VoIP services for low-cost calling and more. We had to relocate smart engineers or create local offices to enable their integration into the company.

I’m frequently asked about the DNN Corp development process. The “great debate” started when interviewing for the job of SVP Engineering as I was asked: “How familiar are you with Agile Scrum”? “Do you subscribe to Waterfall?” “What do you think of Kanban?” You’d be surprised how much interviewers focused on these sorts of questions rather than the results I had overseen. Sheesh!