+1;
They just seems to rename "reuse" to "composition". The gist of the
article seems to
be the followings:
1.SOA promotes software reuse so there would be more people who will
reuse the software.
2. Higher level of abstraction will require different skills from
developers in much
the same way Java developer requires different skill from assembler
developer.
Nevertheless, I think the article did a good job describing the skill
set required
on people reusing a software.
H.Ozawa
Steve Jones wrote:
> The end of development is 3 years away, its as true now as it was when my
> dad got into computing in the 60s.
>
> If you have an "if" statement, state management and choices of sync/async
> processing then you require testing and formalism. So of course its
> development.
>
> Its like saying that Java programming isn't development because you
> aren't using assembler.
>
> Steve
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/service-orientated-architecture/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/service-orientated-architecture/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
