This post originated from an RSS feed registered with Agile Buzz
by James Robertson.
Original Post: Problems with Demos
Feed Title: Cincom Smalltalk Blog - Smalltalk with Rants
Feed URL: http://www.cincomsmalltalk.com/rssBlog/rssBlogView.xml
Feed Description: James Robertson comments on Cincom Smalltalk, the Smalltalk development community, and IT trends and issues in general.
The BC4J blog points out some issues with stock vendor demos. The poster states that many client apps he's seen show that developers haven't looked at the demos - and the post actually explains why, without realizing it:
Some time ago, one of our developers on the JClient team took a similar amount of time and built a demo that illustrates virtually all of the different kinds of JClient bindings for Swing-based UI's that we support.
This is a common thing for developers to do - create the kitchen sink demo that shows off every feature. The trouble is, most developers open those demos once, say something like "wow, that looks like too much to digest", and then run off and just wade through the code as best as they can. This is an industry problem; I've seen it as often in Smalltalk demos as I've seen it elsewhere. What developers really need is short, simple demonstrations of common things they'll use, not baroque examples of every possible use. The former will get looked at and digested; the latter will get ignored.
Previous Topic
