The cost of software is in MAINTENANCE, not development.
Internal Frameworks, developed correctly and over time begin to save your
company alot of time/money.
OO isn't just
class Bird : IAnimal
There are design patterns used to create a common methodology, and most of
these have maintenance in mind.
The more/better thought you put into an application at the start, even
stand-alone ones, the more it pays off later.
Its NEVER a waste of time to develop good code from the get go. The moment
you gotta go in and tweak something, all that upfront work pays off.
This is why I can't (or choose not to) work for most outsource companies.
The ones I've interviewed with seem more interested in RAPID development,
not good development.
I speak only from the direct experience I've had.
Google "software maintenance costs" and see what you come up with, and how
much of the overall pie it costs.
I would take a look at this book:
http://www.apress.com/book/bookDisplay.html?bID=279
It does a good job of mapping out what Framework pieces are, esp
The Domain-Specific Framework Layer vs
Cross-Domain Framework Layer
framework pieces.
...
"Randy Smith" <rs****@cta.orgwrote in message
news:u9**************@TK2MSFTNGP03.phx.gbl...
Hi ALL,
I was told that most Fortune 500 companies use OOP in conjunction with
ASP.Net 2.0. Personally, I find this hard to believe, unless the class
libraries being created are going to be used over and over. But what
about
instances where the web application is designed to be stand-alone. Isn't
this a waste of effort to create classes, datamappers, etc.??? IMHO, OOP
adds about 50% on to the development time for any given project, with no
obvious payback in increased productivity.
Can someone please set me straight on this?
TIA, Randy Smith
