Tweets for 2010-08-15
- @psnively imo design is a relic of activities where apriori modeling using malleable representation was reqd b4 final construcn @debasishg in reply to psnively #
- @psnively In S/w final artifacts continue 2b v malleable unlike builldings n machines, so "formal" design is optional @debasishg in reply to psnively #
- @psnively Given state of design tools vs modern IDEs I suspect code is more malleable than design, thats why I no longer do "formal" design in reply to psnively #
- @psnively I think formal design representations such as UML are more efficient for communication but less at manipulation in detail in reply to psnively #
- @debasishg +1. Better documentation (javadocs), refactoring and reverse engineering tools have made it a reality @psnively @ErikEngbrecht in reply to debasishg #
- @ErikEngbrecht The vocabulary of formal design is documentation eg. UML. Lately for many (and me) the vocabulary of design is the code. in reply to ErikEngbrecht #
- @ErikEngbrecht Hmm, Appropriate stereotypes would b helpful for higher order abstractions, but can't be sure since haven't tried them myself in reply to ErikEngbrecht #
- Map reduce in bash http://ff.im/-pil8G #
- @ErikEngbrecht A metaclass stereotype Model or ActiveRecord wud be helpful I imagine (unless one went beyond OO). Am learning not contesting in reply to ErikEngbrecht #