Back to list
Views:   0
Replies:  0
Archived
,
Reply 1
There is always a balance. Too many layers, modules, patterns, indirections, etc. make the application complex.  

But simply coding without any plan or structure is a recipe for failure. particularly when your application is deployed and now your users want changes, enhancements, additions, etc.   If  your code is properly organized and structured, changes and enhancements are much, much easier. 

There is a lot more to this discussion, but I hope this provides a little clarity. 
Jack Poorte, Feb 27, 2014
Reply 2

Hi Thanh,

Their main target is to provide us close to real world examples of patterns and best practices, now these little projects are kind of a full reference at least for me

They have implemented these little projects so that developer community can learn how to build apps utilizing best practices and patterns, its up to us how we implement after learning

Implementing patterns and best practices not at all an easy and straight forward task, it needs good time and efforts to build a good architecture but the benefit is that later you don't need to worry about the change management things and things get easy and under control when business requirements change


Thanks

Khurram Shahzad, Feb 24, 2014
Stay Inspired!
Join other developers and designers who have already signed up for our mailing list.
Terms     Privacy     Licensing       EULA       Sitemap      
© Data & Object Factory, LLC.
Made with    in Austin, Texas