Big Blue, as the company is known, tends to rely for its success on magical thinking but that magic ran out a long time ago. The company got in trouble back in the 1990s and had to hire for the first time an outside CEO, Lou Gerstner, to save the day. Gerstner pushed IBM into services with spectacular results but this hurt the company, too. As services have became commoditized IBM could only compete by offshoring the work and quality suffered. The other negative impact of Gerstner was his compensation which was for the first time in IBM history very high. Only the Watson family had become rich running IBM with later CEOs like John Opel and John Akers living comfortable lives with lots of perks, but they never got BIG RICH. That changed with Gerstner. Sam Palmisano an IBM lifer followed Gerstner as CEO and followed, too, the Gerstner playbook. Palmisano retired three years ago with a retirement package worth $241 million, replaced by IBM's first woman CEO, Ginni Rometty, who certainly expects a comparable golden parachute. In order to achieve these numbers, though, IBM has essentially sacrificed both its customers and employees. In order to have ever growing earnings per share the company has cut labor to the bone, off-shored everything it can, dropped quality, deliberately underbid contracts to win them then not performed. IBM's acquisition policy is one of buying companies to get their sales then cutting costs to the bone and under-delivering. This and share buybacks have kept earnings growing until this house of cards recently began to fall. Ginni Rometty, who will end up taking the fall for Palmisano's flawed strategy, has stated a very specific earnings goal for 2015 that she will destroy the company to achieve if she must. This book how IBM fell from grace, where it is headed, and what specifically can be done to save the company before it is too late.

    This book draws on material Michael created for his renowned Object Mentor seminars, techniques Michael has used in mentoring to help hundreds of developers, technical managers, and testers bring their legacy systems under control. The topics covered include: Understanding the mechanics of software change, adding features, fixing bugs, improving design, optimizing performance Getting legacy code into a test harness Writing tests that protect you against introducing new problems Techniques that can be used with any language or platform, with examples in Java, C++, C, and C# Accurately identifying where code changes need to be made Coping with legacy systems that aren't object-oriented Handling applications that don't seem to have any structureThis book also includes a catalog of twenty-four dependency-breaking techniques that help you work with program elements in isolation and make safer changes.

    Everybody wants to learn them. You're not a programmer though. How is a non technical user going to learn how to program? You do want to use macros to make your work easier but are you really going to sit down with a huge programming textbook and work your way through every. single. boring. page? Like most people, you'll start with great enthusiasm and vigor but after a few chapters, the novelty wears off. It gets boring. I'm going to try and change that and make learning macro programming entertaining and accessible to non-techies. First of all, programming Excel macros is a huge topic. Let's eat the elephant one bite at a time. Instead of sitting down with a dry, heavy text, you will read very focused, to the point topics. You can then immediately use what you learned in the real world. This is the first lesson in the series. You will learn what macros are, how to access them, a tiny bit of programming theory (just so you have a clue as to what's going on) and how to record macros. As with all my other lessons, this one has a follow along workbook that you can use to work through the exercises. The images in the lessons are based on Excel 2013 for Windows.

    These tools help programmers build compilers and interpreters, but they also have a wider range of applications.The second edition contains completely revised tutorial sections for novice users and reference sections for advanced users. This edition is twice the size of the first and has an expanded index.The following material has been added:Each utility is explained in a chapter that covers basic usage and simple, stand-alone applications How to implement a full SQL grammar, with full sample code Major MS-DOS and Unix versions of lex and yacc are explored in depth, including AT&T lex and yacc, Berkeley yacc, Berkeley/GNU Flex, GNU Bison, MKS lex and yacc, and Abraxas PCYACC

    This book will have you on your way to reading all types of music for guitar and piano. How to Read Music: Beginner Fundamentals of Music and How to Read Musical Notation is written by the #1 Amazon.com Bestselling author Erich Andreas. Erich's easy-to-understand teaching style has been known to get beginners on their way to mastering music reading. Inside the Book You Will Discover: - Everything to Reading Music - Musical Notation - Physics to Sound - Music theory for Beginners - Use the "Click to Look Inside" feature to check out the first few pages Scroll up and click on the "Buy Now" button to receive your How to Read Music book today.

    It has become popular in recent years because of its simplicity, conciseness, and clarity. This book teaches functional programming as a way of thinking and problem solving, using Haskell, the most popular purely functional language. Rather than using the conventional (boring) mathematical examples commonly found in other programming language textbooks, the author uses examples drawn from multimedia applications, including graphics, animation, and computer music, thus rewarding the reader with working programs for inherently more interesting applications. Aimed at both beginning and advanced programmers, this tutorial begins with a gentle introduction to functional programming and moves rapidly on to more advanced topics. Details about progamming in Haskell are presented in boxes throughout the text so they can be easily found and referred to.

    

    This guidebook is aimed clearly at the needs of the student, with a thorough understanding of, and provision for, the potential conceptual difficulties he or she is likely to encounter.

    But if code isn't clean, it can bring a development organization to its knees. Every year, countless hours and significant resources are lost because of poorly written code. But it doesn't have to be that way. Noted software expert Robert C. Martin presents a revolutionary paradigm with Clean Code: A Handbook of Agile Software Craftsmanship . Martin has teamed up with his colleagues from Object Mentor to distill their best agile practice of cleaning code on the fly into a book that will instill within you the values of a software craftsman and make you a better programmer but only if you work at it. What kind of work will you be doing? You'll be reading code - lots of code. And you will be challenged to think about what's right about that code, and what's wrong with it. More importantly, you will be challenged to reassess your professional values and your commitment to your craft. Clean Code is divided into three parts. The first describes the principles, patterns, and practices of writing clean code. The second part consists of several case studies of increasing complexity. Each case study is an exercise in cleaning up code - of transforming a code base that has some problems into one that is sound and efficient. The third part is the payoff: a single chapter containing a list of heuristics and "smells" gathered while creating the case studies. The result is a knowledge base that describes the way we think when we write, read, and clean code. Readers will come away from this book understanding ‣ How to tell the difference between good and bad code‣ How to write good code and how to transform bad code into good code‣ How to create good names, good functions, good objects, and good classes‣ How to format code for maximum readability ‣ How to implement complete error handling without obscuring code logic ‣ How to unit test and practice test-driven development This book is a must for any developer, software engineer, project manager, team lead, or systems analyst with an interest in producing better code.

    One minute we were living life and doing our thing, the next, most of us were advised to stay at home for a month or more.

    It gives an overview of every learning objective for the TOGAF 9 Foundation Syllabus and in-depth coverage on preparing and taking the TOGAF 9 Part 1 Examination. It is specifically designed to help individuals prepare for certification.This Study Guide is excellent material for:a) Individuals who require a basic understanding of TOGAF 9b) Professionals who are working in roles associated with an architecture project such as those responsible for planning, execution, development, delivery, and operationc) Architects who are looking for a first introduction to TOGAF 9d) Architects who want to achieve Level 2 certification in a stepwise manner and have not previously qualified as TOGAF 8 CertifiedA prior knowledge of enterprise architecture is advantageous but not required. While reading this Study Guide, the reader should also refer to the TOGAF Version 9.1 documentation available online at www.opengroup.org and also available as hard copy from www.vanharen.net and online booksellers

    Learn You a Haskell for Great Good! introduces programmers familiar with imperative languages (such as C++, Java, or Python) to the unique aspects of functional programming. Packed with jokes, pop culture references, and the author's own hilarious artwork, Learn You a Haskell for Great Good! eases the learning curve of this complex language, and is a perfect starting point for any programmer looking to expand his or her horizons. The well-known web tutorial on which this book is based is widely regarded as the best way for beginners to learn Haskell, and receives over 30,000 unique visitors monthly.

    Salesforce.com (more than 50%) and Twitter (more than 75% fall into this category. Ebay gets more than 8 billion API calls a month. Facebook and Google, have dozens of APIs that enable both free services and e-commerce, get more than 5 billion API calls each day. Other companies like NetFlix have expanded their service of streaming movies over the the web to dozens of devices using API. At peak times, more than 20 percent of all traffic is accounted for by Netflix through its APIs. Companies like Sears and E-Trade are opening up their catalogs and other services to allow developers and entrepreneurs to create new marketing experiences. Making an API work to create a new channel is not just a matter of technology. An API must be considered in terms of business strategy, marketing, and operations as well as the technical aspects of programming. This book, written by Greg Brail, CTO of Apigee, and Brian Mulloy, VP of Products, captures the knowledge of all these areas gained by Apigee, the leading company in supporting the rollout of high traffic APIs.

    New York Times bestselling historian and novelist Thomas Fleming takes us back to the days of the founders, detailing the surprising facts of American life in 1776 - including its resemblance to today.

    While these are essential, many young ecologists need to figure out how to actually do research themselves. How to Do Ecology provides nuts-and-bolts advice on how to develop a successful thesis and research program. This book presents different approaches to posing testable ecological questions. In particular, it covers the uses, strengths, and limitations of manipulative experiments in ecology. It will help young ecologists consider meaningful treatments, controls, replication, independence, and randomization in experiments, as well as where to do experiments and how to organize a season of work. This book also presents strategies for analyzing natural patterns, the value of alternative hypotheses, and what to do with negative results.Science is only part of being a successful ecologist. This engagingly written book offers students advice on working with other people and navigating their way through the land mines of research. Findings that don't get communicated are of little value. How to Do Ecology suggests effective ways to communicate information in the form of journal articles, oral presentations, and posters. Finally, it outlines strategies for developing successful grant and research proposals. Numerous checklists, figures, and boxes throughout the book summarize and reinforce the main points. In short, this book makes explicit many of the unspoken assumptions behind doing good research in ecology, and provides an invaluable resource for meaningful conversations among ecologists.