This may go over my communication allotment, but if anyone's still reading....
On 4/27/12 11:31 AM, Daniel Parry wrote: > On Fri, Apr 27, 2012 at 09:12:54AM -0700, Ray Davis wrote: >> Going back to my list of recent representative examples, how was a >> client-side developer to know that there was a better way to get >> "related content" tucked away in the Nakamura source tree? > > Documentation? :) I hear a technical writer is still on the wish list. Although I'm doubtful about the technical writer, I agree that improvements such as Chris and Christian recently made to "/system/doc" should help a lot. Mostly, though, I think the best way for developers to communicate is the development process itself. >> The "no redundant wildcards" message pounded like deep dub throughout >> team meetings and emails in late 2010. > > Making it work then making it fast is sometimes better than making it fast > then > making it work. People who can do both get extra karma and/or custard creams > :) Collaboration isn't the same as premature optimization, but I do agree that this can sometimes be a viable custard cream strategy: 1. Making a testable proof-of-concept. (Sling+Jackrabbit seemed pretty good for this; the current OAE less so.) 2. Making similar functionality match user expectations reliably and maintainably. When we're unusually lucky, step 2 might consist of a couple of people (and a lot of tests) looking at step 1 and saying "Oh hey, we're done." Checklist-driven projects sometimes build up a backlog of step 1s, copying-and-pasting from each other along the way, followed by a rushed step 2 effort to fix all the worst problems all at once, leaving damage and debris in its wake. (In the early CLE days, this was called "integration week.") Whereas in my experience, step 2 goes more easily if the team works together on each goal as it gets added. Opinions vary, to put it mildly. But I get a mite frustrated when my preferred approach keeps being interrupted by the other approach's step 2s. Best, Ray _______________________________________________ oae-dev mailing list [email protected] http://collab.sakaiproject.org/mailman/listinfo/oae-dev
