tag:blogger.com,1999:blog-697929553688711480.post319772288258656865..comments2007-04-13T00:41:29.643-07:00Ryan Brushhttp://www.blogger.com/profile/14619577469724926326noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-697929553688711480.post-61535025995827967282007-04-13T00:41:00.000-07:002007-04-13T00:41:00.000-07:00Hey Ryan,<BR/><BR/>Your Blog rocks!! Just wanted to share something with ya… one blogger to another…<BR/>There is this amazing site that I came across where u can make money by sharing information…check it out here’s the link http://www.myndnet.com/login.jsp?referral=alpa83&channel=al176<BR/><BR/>The coolest part is…every time ur information gets sold u get paid for it!!<BR/>I signed it for it.. very cool stuff… u can also mail me at barot.alpa@gmail.com <BR/><BR/>Cheers!<BR/>Alpaalpahttp://www.blogger.com/profile/15506932662289231426noreply@blogger.comtag:blogger.com,1999:blog-697929553688711480.post-23463317802631258612006-12-05T17:36:00.000-08:002006-12-05T17:36:00.000-08:00I appreciate the comments. I am hopeful adopting the Jack Reeves view of code as design will lead us to better expectations and practices in software. <br /><br />In regards to James's thoughts: If we can get building and validating software right, collaboration between consumers and developers is the next frontier. I haven't attempted to take on this problem, but I'm glad to see the thoughts on it. <br /><br />Finally, I want to clarify my thoughts on UML based on out-of-band discussions: UML is really an attempt to compensate for some of the shortcomings of current languages. In a better language, the code itself would be sufficient to express the design.<br /><br />The interesting thing is attempts (no matter how bad) to convert UML to code and vice versa suggests people want to view design and code as equivalent artifacts, and for good reason.Ryanhttp://www.blogger.com/profile/14619577469724926326noreply@blogger.comtag:blogger.com,1999:blog-697929553688711480.post-24441135458429508512006-12-05T12:58:00.000-08:002006-12-05T12:58:00.000-08:00One challenge for any software development team is improving the <a href="http://www.ebizq.net/blogs/decision_management/2006/04/concurrent_business_engineerin.php">collaboration</a> between business users and IT. This is a challenge as <a href="http://www.edmblog.com/weblog/2005/08/different_persp.html">business users and IT folks have different perspectives</a>. This can be addressed if the design work is done to empower business users to maintain their own systems but <a href="http://www.edmblog.com/weblog/2006/08/the_secret_of_b.html">business users don't want to maintain code</a> so it requires a certain amount of effort. It pays off in less errors, better collaboration, more agility and less maintenance.<br />JT<br /><a href="http://www.edmblog.com">www.edmblog.com</a>Jameshttp://www.blogger.com/profile/04589456040368641147noreply@blogger.comtag:blogger.com,1999:blog-697929553688711480.post-8396638447366213712006-12-05T12:40:00.000-08:002006-12-05T12:40:00.000-08:00None of these ideas are new, but this post is on record as the first place I saw these recent ideas distilled and laid out all in one place. Bravo.Kartik Agaramhttp://www.blogger.com/profile/14608664977741918006noreply@blogger.com