The * first pillars of application development

When creating an application, you need to do first things first.  But...what are the "first" things?  Architecturally speaking, which are the "load bearing beams" that must absolutely be taken into account upfront and, conversely, which are the flexible items that you can safely incur technical debt in order to meet deadlines, management expectations, cost constraints, etc.?  If you are truly serious about building a robust, practical, maintainable, and praiseworthy enterprise-grade product, I argue the following are critical pillars of success that must be designed into the solution first:


Post a Comment

Keep it clean and professional...