From Java to Ruby: Things Every Manager Should Know
2008-11-03 19:49
513 查看
版权声明:原创作品,允许转载,转载时请务必以超链接形式标明文章原始出版、作者信息和本声明。否则将追究法律责任。http://blog.csdn.net/topmvp - topmvp
As a development team, you want to be productive. You want to write flexible, maintainable web applications. You want to use Ruby and Rails. But can you justify the move away from established platforms such as J2EE? Bruce Tate's From Java to Ruby has the answers, and it expresses them in a language that'll help persuade managers and executives who've seen it all. See when and where the switch makes sense, and see how to make it.
If you're trying to adopt Ruby in your organization and need some help, this is the book for you.
Based on a decision tree (a concept familiar to managers and executives) Java to Ruby stays above the low-level technical debate to examine the real benefits and risks to adoption.
Java to Ruby is packed with interviews of Ruby customers and developers, so you can see what types of projects are likely to succeed, and which ones are likely to fail. Ruby and Rails may be the answer, but first, you need to be sure you're asking the right question. By addressing risk and fitness of purpose, Java to Ruby makes sure you're asking the right questions first.
Because technology adoption is only the beginning, Java to Ruby walks you through the whole lifecycle of prototype, ramp up, and production and deployment.
http://rapidshare.com/files/52626831/0976694093.zip
As a development team, you want to be productive. You want to write flexible, maintainable web applications. You want to use Ruby and Rails. But can you justify the move away from established platforms such as J2EE? Bruce Tate's From Java to Ruby has the answers, and it expresses them in a language that'll help persuade managers and executives who've seen it all. See when and where the switch makes sense, and see how to make it.
If you're trying to adopt Ruby in your organization and need some help, this is the book for you.
Based on a decision tree (a concept familiar to managers and executives) Java to Ruby stays above the low-level technical debate to examine the real benefits and risks to adoption.
Java to Ruby is packed with interviews of Ruby customers and developers, so you can see what types of projects are likely to succeed, and which ones are likely to fail. Ruby and Rails may be the answer, but first, you need to be sure you're asking the right question. By addressing risk and fitness of purpose, Java to Ruby makes sure you're asking the right questions first.
Because technology adoption is only the beginning, Java to Ruby walks you through the whole lifecycle of prototype, ramp up, and production and deployment.
http://rapidshare.com/files/52626831/0976694093.zip
相关文章推荐
- 5 Things Every Manager Should Know about Microsoft SharePoint 关于微软SharePoint每个经理应该知道的五件事
- 10 Things Every Java Programmer Should Know about String
- 5 Things Every Manager Should Know about Microsoft SharePoint 关于微软SharePoint每个经理应该知道的五件事
- 10 Things Every Programmer Should Know For Their First Job(每个人工作必须知道的10件事)
- 97 Things Every Software Architect Should Know
- Top 10 New Things You Need to Know About Java 6
- 97 Things Every Programmer Should Know
- What 10 things should you do every day to improve your life?
- 10 Things Every Senior Flex Developer Should Know
- undefined reference to 'AAssetManager_fromJava'
- What are some of the most basic things every programmer should know?
- What you may need to know while calling Application Module methods from Java EE components such as E
- 97 Things Every Programmer Should Know
- 97 Things Every Programmer Should Know (oreilly.com)
- C# Development 13 Things Every C# Developer Should Know
- 97 Things Every Software Architect Should Know
- 97 things every programmer should know
- Three things everyone should know to improve object retrieval
- 10 things you should know about every Linux installation
- 6 things every IT person should know