tag:blogger.com,1999:blog-947357504786991651.post2936834311720783789..comments2014-05-29T18:16:27.809-07:00Comments on Eric Gagnon's Software Engineering Blog: Stakeholders for Military Inventory Issue LogSam Josephhttp://www.blogger.com/profile/10788506730233381803noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-947357504786991651.post-25426735967087868972014-02-18T15:09:11.198-08:002014-02-18T15:09:11.198-08:00Well that's a relief. At times it's hard ...Well that's a relief. At times it's hard for me to visualize how all of these things work together. Anonymoushttps://www.blogger.com/profile/11184616358347748072noreply@blogger.comtag:blogger.com,1999:blog-947357504786991651.post-34877385680170359542014-02-14T07:05:05.263-08:002014-02-14T07:05:05.263-08:00I believe Ruby can talk to MSAccess if it has too,...I believe Ruby can talk to MSAccess if it has too, but I wouldn't worry too much about that. The key value offering of ruby on rails is that once you've mastered the basics you can create a prototype site very fast. What the final solution might be is another matter. What you want is to work quickly through a series of prototypes from paper sketches, html mockups and fast interactive prototypes in ruby on rails in order to really understand how users will interact with your system and make sure it does what they need it to do. Legacy data issues are another concern, but I wouldn't worry about them too much while prototyping - and pretty much any language can talk to any database, or some data conversion mapping can be created when necessary.Sam Josephhttps://www.blogger.com/profile/10788506730233381803noreply@blogger.com