He didn't set out to be a Silicon Valley icon, a business visionary, or even a billionaire. But he became all three. It turns out that business is a mosaic of interesting puzzles like managing risk, developing and reversing strategies, and looking into the future by deconstructing the past. As a founder of NetApp, a data storage firm that began as an idea scribbled on a placemat and now takes in $4 billion a year, Hitz has seen his company go through every major cycle in business--from the Jack-of-All-Trades mentality of a start-up, through the tumultuous period of the IPO and the dot-com bust, and finally to a mature enterprise company. NetApp is one of the fastest-growing computer companies ever, and for six years in a row it has been on Fortune magazine's list of Best Companies to Work For. Not bad for a high school dropout who began his business career selling his blood for money and typing the names of diseases onto index cards.With colorful examples and anecdotes, How to Castrate a Bull is a story for everyone interested in understanding business, the reasons why companies succeed and fail, and how powerful lessons often come from strange and unexpected places.Dave Hitz co-founded NetApp in 1992 with James Lau and Michael Malcolm. He served as a programmer, marketing evangelist, technical architect, and vice president of engineering. Presently, he is responsible for future strategy and direction for the company. Before his career in Silicon Valley, Dave worked as a cowboy, where he got valuable management experience by herding, branding, and castrating cattle.

    Today, twenty million people worldwide are surfing the Net. Where Wizards Stay Up Late is the exciting story of the pioneers responsible for creating the most talked about, most influential, and most far-reaching communications breakthrough since the invention of the telephone. In the 1960's, when computers where regarded as mere giant calculators, J.C.R. Licklider at MIT saw them as the ultimate communications devices. With Defense Department funds, he and a band of visionary computer whizzes began work on a nationwide, interlocking network of computers. Taking readers behind the scenes, Where Wizards Stay Up Late captures the hard work, genius, and happy accidents of their daring, stunningly successful venture.

    Find out how the Swedish police combined XP, Scrum, and Kanban in a 60-person project. From start to finish, you'll see how to deliver a successful product using Lean principles. We start with an organization in desperate need of a new way of doing things and finish with a group of sixty, all working in sync to develop a scalable, complex system. You'll walk through the project step by step, from customer engagement, to the daily "cocktail party," version control, bug tracking, and release. In this honest look at what works--and what doesn't--you'll find out how to: Make quality everyone's business, not just the testers. Keep everyone moving in the same direction without micromanagement. Use simple and powerful metrics to aid in planning and process improvement. Balance between low-level feature focus and high-level system focus. You'll be ready to jump into the trenches and streamline your own development process.ContentsForewordPrefacePART I: HOW WE WORK1. About the Project1.1 Timeline 51.2 How We Sliced the Elephant 61.3 How We Involved the Customer 72. Structuring the Teams3. Attending the Daily Cocktail Party3.1 First Tier: Feature Team Daily Stand-up3.2 Second Tier: Sync Meetings per Specialty3.3 Third Tier: Project Sync Meeting4. The Project Board4.1 Our Cadences4.2 How We Handle Urgent Issues and Impediments5. Scaling the Kanban Boards6. Tracking the High-Level Goal7. Defining Ready and Done7.1 Ready for Development7.2 Ready for System Test7.3 How This Improved Collaboration 8. Handling Tech Stories8.1 Example 1: System Test Bottleneck8.2 Example 2: Day Before the Release8.3 Example 3: The 7-Meter Class9. Handling Bugs9.1 Continuous System Test9.2 Fix the Bugs Immediately9.3 Why We Limit the Number of Bugs in the Bug Tracker9.4 Visualizing Bugs9.5 Preventing Recurring Bugs10. Continuously Improving the Process10.1 Team Retrospectives10.2 Process Improvement Workshops10.3 Managing the Rate of Change11. Managing Work in Progress11.1 Using WIP Limits11.2 Why WIP Limits Apply Only to Features12. Capturing and Using Process Metrics12.1 Velocity (Features per Week)12.2 Why We Don’t Use Story Points12.3 Cycle Time (Weeks per Feature)12.4 Cumulative Flow12.5 Process Cycle Efficiency13. Planning the Sprint and Release13.1 Backlog Grooming13.2 Selecting the Top Ten Features13.3 Why We Moved Backlog Grooming Out of the Sprint Planning Meeting13.4 Planning the Release14. How We Do Version Control14.1 No Junk on the Trunk14.2 Team Branches14.3 System Test Branch15. Why We Use Only Physical Kanban Boards16. What We Learned16.1 Know Your Goal16.2 Experiment16.3 Embrace Failure16.4 Solve Real Problems16.5 Have Dedicated Change Agents16.6 Involve PeoplePART II: A CLOSER LOOK AT THE TECHNIQUES 17. Agile and Lean in a Nutshell17.1 Agile in a Nutshell17.2 Lean in a Nutshell17.3 Scrum in a Nutshell17.4 XP in a Nutshell17.5 Kanban in a Nutshell18. Reducing the Test Automation Backlog18.1 What to Do About It18.2 How to Improve Test Coverage a Little Bit Each Iteration18.3 Step 1: List Your Test Cases18.4 Step 2: Classify Each Test18.5 Step 3: Sort the List in Priority Order18.6 Step 4: Automate a Few Tests Each Iteration18.7 Does This Solve the Problem?19. Sizing the Backlog with Planning Poker19.1 Estimating Without Planning Poker19.2 Estimating with Planning Poker19.3 Special Cards20. Cause-Effect Diagrams20.1 Solve Problems, Not Symptoms20.2 The Lean Problem-Solving Approach: A3 Thinking20.3 How to Use Cause-Effect Diagrams20.4 Example 1: Long Release Cycle20.5 Example 2: Defects Released to Production20.6 Example 3: Lack of Pair Programming20.7 Example 4: Lots of Problems20.8 Practical Issues: How to Create and Maintain the Diagrams20.9 Pitfalls20.10 Why Use Cause-Effect Diagrams?21. Final WordsA1. Glossary: How We Avoid Buzzword BingoIndex

    What makes an operating system modern? According to author Andrew Tanenbaum, it is the awareness of high-demand computer applications--primarily in the areas of multimedia, parallel and distributed computing, and security. The development of faster and more advanced hardware has driven progress in software, including enhancements to the operating system. It is one thing to run an old operating system on current hardware, and another to effectively leverage current hardware to best serve modern software applications. If you don't believe it, install Windows 3.0 on a modern PC and try surfing the Internet or burning a CD. Readers familiar with Tanenbaum's previous text, Operating Systems, know the author is a great proponent of simple design and hands-on experimentation. His earlier book came bundled with the source code for an operating system called Minux, a simple variant of Unix and the platform used by Linus Torvalds to develop Linux. Although this book does not come with any source code, he illustrates many of his points with code fragments (C, usually with Unix system calls). The first half of Modern Operating Systems focuses on traditional operating systems concepts: processes, deadlocks, memory management, I/O, and file systems. There is nothing groundbreaking in these early chapters, but all topics are well covered, each including sections on current research and a set of student problems. It is enlightening to read Tanenbaum's explanations of the design decisions made by past operating systems gurus, including his view that additional research on the problem of deadlocks is impractical except for "keeping otherwise unemployed graph theorists off the streets." It is the second half of the book that differentiates itself from older operating systems texts. Here, each chapter describes an element of what constitutes a modern operating system--awareness of multimedia applications, multiple processors, computer networks, and a high level of security. The chapter on multimedia functionality focuses on such features as handling massive files and providing video-on-demand. Included in the discussion on multiprocessor platforms are clustered computers and distributed computing. Finally, the importance of security is discussed--a lively enumeration of the scores of ways operating systems can be vulnerable to attack, from password security to computer viruses and Internet worms. Included at the end of the book are case studies of two popular operating systems: Unix/Linux and Windows 2000. There is a bias toward the Unix/Linux approach, not surprising given the author's experience and academic bent, but this bias does not detract from Tanenbaum's analysis. Both operating systems are dissected, describing how each implements processes, file systems, memory management, and other operating system fundamentals. Tanenbaum's mantra is simple, accessible operating system design. Given that modern operating systems have extensive features, he is forced to reconcile physical size with simplicity. Toward this end, he makes frequent references to the Frederick Brooks classic The Mythical Man-Month for wisdom on managing large, complex software development projects. He finds both Windows 2000 and Unix/Linux guilty of being too complicated--with a particular skewering of Windows 2000 and its "mammoth Win32 API." A primary culprit is the attempt to make operating systems more "user-friendly," which Tanenbaum views as an excuse for bloated code. The solution is to have smart people, the smallest possible team, and well-defined interactions between various operating systems components. Future operating system design will benefit if the advice in this book is taken to heart. --Pete Ostenson

    In the late 1980s, financier Ronald Perelman, worth billions and riding high after his hostile takeover of the cosmetics firm Revlon, bought Marvel Entertainment–legendary creator of Captain America, the Incredible Hulk, Spider-Man, the X-Men, and other superheroes–and he had big plans. He not only began churning out more comic books, he also acquired sports cards and other subsidiaries, impressing Wall Street so much that after he took the company public, Marvel’s market value ballooned to over $3 billion. Perelman took advantage of the company’s inflated valuation by selling junk bonds, and personally pocketing nearly $500 million. Meanwhile, Marvel’s bank debt rose to more than $600 million. And then came the collapse of the comic-book and trading-card markets.Enter rival corporate raider, Carl Icahn, who sank a fortune into Marvel’s bonds in an effort to wrest away control of Marvel–and to beat Perelman at his own game. As the competing tycoons went head-to-head, Ike Perlmutter and Avi Arad, two entrepreneurs who ran Toy Biz, a company that depended on Marvel superheroes, realized that their fate hung in the balance. They soon put in motion plans to take control themselves.Bunkered in The Townhouse, his high-security Manhattan corporate headquarters, Perelman had Marvel declare bankruptcy. Icahn, an avid poker player, had to figure out if his foe was bluffing; the Toy Biz entrepreneurs needed to find a way to save the company they loved from ruin; and a team of killer lawyers representing the banks was faced with recouping their colossal debt. Thus, in United States Bankruptcy Court, began the comic war–as ferocious and outlandish as any of Marvel’s tales of good vs. evil.Combining meticulous investigative reporting with entertaining storytelling, Comic Wars exposes the actions and motives of two Goliath-style corporate raiders, two innovative Davids, and some of the world’s most prominent banks. It is the rollicking true tale of a unique Wall Street showdown, of Marvel’s surprising emergence from the ashes of bankruptcy, and of its triumphant reinvention as the producer of such hit Hollywood movies as X-Men and Spider-Man.

    In the backseat were three personal computers. Today, he is the chairman and CEO of Dell Computer Corporation, a $30 billion company and the second largest manufacturer and marketer of computers in the world. Founded on a deceptively simple premise-to deliver high-performance computer systems directly to the end user-Dell Computer is the envy of its competition. It has consistently grown at two to three times the industry rate, its stock went up more than 90,000 percent in the last decade, and Dell is now selling more than $35 million worth of systems per day over "In Direct from Dell," you will learn why it's better for any business starting out to have too little capital rather than too muchwhy your people pose a greater threat to the health of your business than your competitionhow you can exploit your competition's weakness by exposing its greatest strengthhow intergrating your business virtually can make the difference between being quick -and being deadand much more

    At under 200 pages it's quick reading too. Makes a great airplane book.

    Do you feel like you could be getting more out of your retrospectives and fuelling continuous improvement in your teams? You may already find retrospectives valuable, but suspect there are ways of making them better.This book condenses down eight years of experience working with the retrospective practice within the context of real agile teams. It offers you practice advice on how to make your retrospectives even more effective including topics such as: Best methods to prepare for a retrospective Picking just the right materials Facilitating retrospectives with ease Dealing with common retrospective smells Retrospectives in different contexts including distributed, large and small groups A checklist for preparation Ensuring retrospectives result in change

    Over the following decade, an army of lawyers, executives, politicians, and judges spent countless hours clashing over what amounted to the biggest corporate breakup in American history. From boardroom to courtroom, Steve Coll untangles the myriad threads of this complex and critical case and gives readers “an excellent behind-the-scenes look” at the human drama involved in the remaking of an entire industry (The Philadelphia Inquirer).   Hailed by the New York Times Book Review as “rich, intricate and convincing,” The Deal of the Century is the definitive narrative of a momentous turning point in the way America does business.    A New York Times–bestselling author’s “superbly reported” account of the dismantling of the world’s largest corporation (The Washington Post). Written by the two-time Pulitzer Prize–winning author of Ghost Wars and Private Empire, The Deal of the Century chronicles the decade-long war for control of AT&T.

    Dominic Frisby has written a great account. Read it and glimpse into the future'—Sir Richard Branson In 2008, while the world was busy panicking about the global financial crisis, a computer programmer called Satoshi Nakamoto posted a message on an out-of-the-way mailing list. ‘I’ve been working on a new electronic cash system,’ he said. ‘It might make sense to get some just in case it catches on.’ Nobody seemed to care. But what he had programmed would become the world’s most famous alternative currency: Bitcoin. Economists, anarchists, speculators, computer coders, libertarians, criminals and entrepreneurs were inspired across the world. Early adopters would make a return two million times larger than their investment. Now it seems that Bitcoin will do to banking and finance what email did to the postal service and what the internet did to publishing: destroy old monopolies and create opportunities for the masses. Some even suggest that the technology behind Bitcoin will usurp our Western systems of representative democracy. In this gripping book, Dominic Frisby sets out to solve the mystery surrounding the identity of Bitcoin’s secretive creator, Satoshi Nakamoto. He shows how Bitcoin will change the world. And, perhaps most importantly of all, he does something nobody else has hitherto been able to do: he explains in layman’s language exactly how it works. 'The book’s outstanding, but the story it tells is even better.’ —Matt Ridley, The Times ‘In this highly readable yet technically accomplished book, Dominic Frisby makes crypto currencies crystal clear. Read it, or fail to understand possibly the most important financial innovation of our time.' —Liam Halligan, Sunday Telegraph 'Despite having an MSc in Computer Science and spending over ten years studying monetary theory, I ignored Bitcoin as hype for too long. You shouldn’t. Read Dominic’s thrilling book and discover the next big thing.’ —Steve Baker, MP

    This book rewrites the history of computer science, arguing that in reality Colossus--the giant computer built by the British secret service during World War II--predates ENIAC by two years.Colossus was built during the Second World War at the Government Code and Cypher School at Bletchley Park. Until very recently, much about the Colossus machine was shrouded in secrecy, largely because the code-breaking algorithms that were employed during World War II remained in use by the British security services until a short time ago. In addition, the United States has recently declassified a considerable volume of wartime documents relating to Colossus. Jack Copeland has brought together memoirs of veterans of Bletchley Park--the top-secret headquarters of Britain's secret service--and others who draw on the wealth of declassified information to illuminate the crucial role Colossus played during World War II. Included here are pieces by the former WRENS who actually worked the machine, the scientist who pioneered the use of vacuum tubes in data processing, and leading authorities on code-breaking and computer science.A must read for anyone curious about code-breaking or World War II espionage, Colossus offers a fascinating insider's account of the world first giant computer, the great great grandfather of the massive computers used today by the CIA and the National Security Agency.

    But developing these systems brings its own set of headaches. With lots of examples and practical advice, this book takes a holistic view of the topics that system architects and administrators must consider when building, managing, and evolving microservice architectures.Microservice technologies are moving quickly. Author Sam Newman provides you with a firm grounding in the concepts while diving into current solutions for modeling, integrating, testing, deploying, and monitoring your own autonomous services. You'll follow a fictional company throughout the book to learn how building a microservice architecture affects a single domain.Discover how microservices allow you to align your system design with your organization's goalsLearn options for integrating a service with the rest of your systemTake an incremental approach when splitting monolithic codebasesDeploy individual microservices through continuous integrationExamine the complexities of testing and monitoring distributed servicesManage security with user-to-service and service-to-service modelsUnderstand the challenges of scaling microservice architectures

    As John invested in these skills his career took off, and he became a highly paid, highly sought-after developer and consultant. Today John helps more than 1.4 million programmers every year to increase their income by developing this unique blend of skills. "If you're a developer, green or a veteran, you owe it to yourself to read The Complete Software Developers Career Guide." - Jason Down, Platform Developer, Ontario, Canada What You Will Learn in This Book How to systematically find and fill the gaps in your technical knowledge so you can face any new challenge with confidence Should you take contract work - or hold out for a salaried position? Which will earn you more, what the tradeoffs are, and how your personality should sway your choice Should you learn JavaScript, C#, Python, C++? How to decide which programming language you should master first Ever notice how every job ever posted requires "3-5 years of experience," which you don't have? Simple solution for this frustrating chicken-and-egg problem that allows you to build legitimate job experience while you learn to code Is earning a computer science degree a necessity - or a total waste of time? How to get a college degree with maximum credibility and minimum debt Coding bootcampssome are great, some are complete scams. How to tell the difference so you don't find yourself cheated out of $10,000 Interviewer tells you, "Dress code is casual around here - the development team wears flipflops." What should you wear? How do you deal with a boss who's a micromanager. Plus how helping your manager with his goals can make you the MVP of your team The technical skills that every professional developer must have - but no one teaches you (most developers are missing some critical pieces, they don't teach this stuff in college, you're expected to just "know" this) An inside look at the recruiting industry. What that "friendly" recruiter really wants from you, how they get paid, and how to avoid getting pigeonholed into a job you'll hate Who Should Read This Book Entry-Level Developers This book will show you how to ensure you have the technical skills your future boss is looking for, create a resume that leaps off a hiring manager's desk, and escape the "no work experience" trap. Mid-Career Developers You'll see how to find and fill in gaps in your technical knowledge, position yourself as the one team member your boss can't live without, and turn those dreaded annual reviews into chance to make an iron-clad case for your salary bump. Senior Developers This book will show you how to become a specialist who can command above-market wages, how building a name for yourself can make opportunities come to you, and how to decide whether consulting or entrepreneurship are paths you should pursue.

    No academic analysis or bystander’s account can capture it. Now Doug Edwards, Employee Number 59, offers the first inside view of Google, giving readers a chance to fully experience the bizarre mix of camaraderie and competition at this phenomenal company. Edwards, Google’s first director of marketing and brand management, describes it as it happened. We see the first, pioneering steps of Larry Page and Sergey Brin, the company’s young, idiosyncratic partners; the evolution of the company’s famously nonhierarchical structure (where every employee finds a problem to tackle or a feature to create and works independently); the development of brand identity; the races to develop and implement each new feature; and the many ideas that never came to pass. Above all, Edwards—a former journalist who knows how to write—captures the “Google Experience,” the rollercoaster ride of being part of a company creating itself in a whole new universe. I’m Feeling Lucky captures for the first time the unique, self-invented, yet profoundly important culture of the world’s most transformative corporation.

    Designed for readers who don't need the academic formality, it's a fast and easy computer science guide. It teaches essential concepts for people who want to program computers effectively. First, it introduces discrete mathematics, then it exposes the most common algorithms and data structures. It also shows the principles that make computers and programming languages work.