Geeks With Blogs
My blog on all kinds of stuff...

Rocky blogs that 98% of the systems being built out there are "trivial" or at least can be solved by "trivial" solutions.  Is this really the case?  He also contends that most applications are a "viewer (form, page, screen)" over data and development tools such automat this, attributing unecessary complexity to tool vendors, framework builders, architects etc.

I actually disagree with his assessment on the distribution of complexity.  My developers spend much more of their time behind the screen than in it.  I've worked on enough projects to know that there are a fair share of applications where more interesting things happen when a user clicks the "Ok" button.

Understanding the business problem that needs to be solved (deployment model, update strategy, functionality, performance requirements, scalability, user interaction, configurability, integration etc) drive the tools and methodologies that should be used.  A decent understanding of tools and methodologies are required in order to effectively use them.  It's not a secret that a lot of software projects fail due to a lack of understanding of both the problem domain and the toolset/methodologies required.

I cringe when folks with influence imply a panacea of sorts for software engineering based on a subset of scenarios.  Each situation has to be studied in isolation. While there may be reusable "patterns and practices", in a lot of cases, these need to be "tweaked" to solve the problem.  If your application is simply forms-over-data, build it in the simplest manner possible!


Posted on Wednesday, May 31, 2006 5:04 AM Design , Architecture | Back to top

Comments on this post: Is Software Development Really Hard?

No comments posted yet.
Your comment:
 (will show your gravatar)

Copyright © Ebenezer Ikonne | Powered by: