Tags
Language
Tags
May 2025
Su Mo Tu We Th Fr Sa
27 28 29 30 1 2 3
4 5 6 7 8 9 10
11 12 13 14 15 16 17
18 19 20 21 22 23 24
25 26 27 28 29 30 31
    Attention❗ To save your time, in order to download anything on this site, you must be registered 👉 HERE. If you do not have a registration yet, it is better to do it right away. ✌

    ( • )( • ) ( ͡⚆ ͜ʖ ͡⚆ ) (‿ˠ‿)
    SpicyMags.xyz

    From Java to Ruby - Things Every Manager Should Know

    Posted By: doctorvb
    From Java to Ruby - Things Every Manager Should Know

    From Java to Ruby: Things Every Manager Should Know
    Publisher: Pragmatic Bookshelf (June 1, 2006) | Author : Bruce Tate | ISBN: 0976694093 | 160 pages | PDF | Rar Size : 0.99 MB |


    Book Description
    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.

    Table of Contents :
    1 Introduction
    1.1 The Emergence of Ruby
    1.2 The Java Platform Is Weakening
    1.3 Early Adopters Embrace Ruby
    1.4 The Process
    1.5 Moving Ahead
    1.6 Executive Summary
    2 Pain
    2.1 The House of Pain
    2.2 Poor Productivity
    2.3 Long Ramp-Up
    2.4 A Look at Risk
    2.5 Executive Summary
    3 Establishing Your Reward
    3.1 Momentum
    3.2 Productivity
    3.3 Cost
    3.4 Ramp-Up
    3.5 Risk
    3.6 Looking Ahead
    3.7 Executive Summary
    4 Pilot
    4.1 Building Your Plan
    4.2 Scenario 1: Classic Pilot
    4.3 Scenario 2: Trojan Horse
    4.4 Scenario 3: Race
    4.5 Scenario 4: Bet-your-Business: Basecamp
    4.6 Scenario 5: Rescue
    4.7 Making the Choice
    4.8 Executive Summary
    5 On an Island
    5.1 Overview
    5.2 The Basics
    5.3 Web Development
    5.4 Rails
    5.5 Middleware
    5.6 Looking Ahead
    5.7 Executive Summary
    6 Bridges
    6.1 Road Maps
    6.2 Scenarios
    6.3 Ruby to Java Bridges
    6.4 JRuby
    6.5 Service-Oriented Architectures
    6.6 Executive Summary
    7 RampingUp
    7.1 Building Your Staff
    7.2 Building Skills Internally
    7.3 Short-Term Augmentation
    7.4 Preparing the Way
    7.5 A Brief Word about Deployment
    7.6 Executive Summary
    8 Risk
    8.1 Bad Risk
    8.2 Mitigating Technical Risk
    8.3 Mitigating Political Risk
    8.4 What’s Ahead for Ruby?
    9 Bibliography


    Amazon Info



    Password = Password