Re: Frameworks and versioning
Re: Frameworks and versioning
- Subject: Re: Frameworks and versioning
- From: "Jerry W. Walker" <email@hidden>
- Date: Thu, 5 Jan 2006 12:28:35 -0500
Greetings,
I thought about opening a new thread for this, but it seems a natural
extension to the thread title, so...
I agree with Tonny that there is no right answer, and I personally
agree with Arturo's preferences. However, in reading Arturo's list,
it strikes me that I've never seen a good class (or book) on
"Graduate Studies in WO Development" or something like that.
Chuck and Sacha's Practical WebObjects book comes as close as
anything I've read (and I haven't yet read it all, because I've used
it more as reference to date), but I've never seen a class that
identifies a reasonable complement of the tools Arturo listed and
reviews where they're used, how they're used and, most important, why
they're used.
I'd love to see a class or book directed at WO developers that
clearly reviewed:
* Source code control - CVS or Subversion use as a developer IN A
TEAM (not as an admin)
* Good CVS or Subversion logging messages, why they're important
and when and why they should be read
* Unit testing with JUnit, WOUnitTest, etc.
* Test first development and why that works better than tests
added later or (horrors) not added at all
* Black box testing with JMeter, HTTPUnit, etc.
* Stack trace reading for exceptions including how to glean
important information therefrom
* Debugging app freezes including how to trigger a stack trace and
identify the deadlocked thread and code
* How to resolve missing framework or missing class messages
and so on.
These are the real problems faced by the developers in the field and
they represent knowledge needed beyond the tools classes and courses
that seem to be currently offered.
One could make a good case for this mailing list being a better
vehicle for such issues, but I still feel that a well thought out and
well structured set of material could be invaluable, even (or perhaps
more) for veterans who haven't been appropriately introduced to some
of these concepts.
There are some underlying assumptions in the above list, of course,
such as the software process used. But with the appropriate tools
(such as WO, WOUnitTest, EOF, CVS/Subversion etc.) some of the modern
light methodologies that have failed in earlier system development
efforts, are much more appropriate now.
I'll leave it at that figuring that now that I've stoked the fire,
flames will help elucidate this important issue. :-)
Regards,
Jerry
On Jan 5, 2006, at 11:21 AM, Arturo Perez wrote:
Tonny Staunsbrink wrote:
Hi All
I'm don't think there is a "right" answer on this issue. Embedding
your frameworks solves the problem of breaking API or introducing
bugs. On the other hand it makes it cumbersome to deploy bugfixes
to frameworks (when multiple apps are using the frameworks). It's
the same discussion as dynamic vs. static linking - the same pros
and cons (well, almost) - and i think it's worth to note that
dynamic linking is used alot.
I prefer to have my frameworks deployed seperately from the
applications (due to the ease of deploying updates). The risk of
breaking API should be a matter of developer discipline ;-) and
sometimes biting the bullet (rebuilding and redeploying every app
when some used API fetaure is completly removed).
Cheers
/Tonny
Personally, I've never liked the embedding of frameworks et al into
an application (although I did once work with a group of developers
that almost violently disagreed). I much prefer that all
applications benefit from bugfixes and performance enhancements as
soon as possible. It does require a bit of discipline to not break
things but I think ensuring that apps get the right set of bugfixes
etc is at least as much work. Of course, if your style is deploy-
and-forget then embedding frameworks is definitely the right way to
go.
I believe a healthy combination of CVS-log monitoring (read them
daily and write good ones), JUnit et al, and black-box testing
(JMeter, HTTPUnit, et al) can keep an application functioning
properly in the face of frequently updated frameworks.
Just my 2p
-arturo
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40gmail.com
This email sent to email@hidden
--
__ Jerry W. Walker,
WebObjects Developer/Instructor for High Performance Industrial
Strength Internet Enabled Systems
email@hidden
203 278-4085 office
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden