Day 2 - Session 6 - Case Study for HarrisData

So this is extremely far from a technical discussion, but important in our industry none-the-less... It's often we only look at architecture, proper ways of developing, and of course, patterns. We normally forget the entire user experience, and sales aspect, and this is a tribute to that in the form of a case study.

Talking about customer retention, and how it's very important to show added value for upgrades, as well as a comfort level of upgrading with minimal effort.

It's also important internally to figure out what caused the upgrade to take place to begin with. This also helps with sales.

Why HarrisData chose PHP:

• Obligitory PHP answers (price, ease of use, etc).
• Can do procedural (for legacy developers), or OOP. Java would have destroyed setups and developer ramp-ups.
• Professional IDE improving productivity and quality
• Market acceptance (many people already using PHP and understand it).
• Ideal application arch (server-centric vs desktop, reliable, secure, flexible)