Did you design your system to survivef a sudden rush of visitors from Digg or Slashdot? Or an influx of real world customers from 100 different countries? Are you ready for a world filled with flakey networks, tangled databases, and impatient users?If you're a developer and don't want to be on call for 3AM for the rest of your life, this book will help.In Release It!, Michael T. Nygard shows you how to design and architect your application for the harsh realities it will face. You'll learn how to design your application for maximum uptime, performance, and return on investment.Mike explains that many problems with systems today start with the design.

    His distinctive brand of architecture, usually moulded around local building traditions (especially those of Kerela, his adopted home state in south India), is instantly identifiable and has, unsurprisingly, revolutionized traditional concepts of architecture in India. Baker's architecture is responsive, uses local materials and lays stress on low-cost design.This biograpy of Laurie Baker, like his work, is direct, simple and comprehensive; further embellished with sketches, plans, photographs and some of Baker's own writings, the book offers the professional architect view of the life, methods and thoughts of an unorthodox genius.

    BUILDING CONSTRUCTION BY RANGWALA, 9789385039041

    However, ATDD is still widely misunderstood by many practitioners. "ATDD by Example" is the first practical, entry-level, hands-on guide to implementing and successfully applying it. ATDD pioneer Markus Gartner walks readers step by step through deriving the right systems from business users, and then implementing fully automated, functional tests that accurately reflect business requirements, are intelligible to stakeholders, and promote more effective development. Through two end-to-end case studies, Gartner demonstrates how ATDD can be applied using diverse frameworks and languages. Each case study is accompanied by an extensive set of artifacts, including test automation classes, step definitions, and full sample implementations. These realistic examples illuminate ATDD's fundamental principles, show how ATDD fits into the broader development process, highlight tips from Gartner's extensive experience, and identify crucial pitfalls to avoid. Readers will learn to Master the thought processes associated with successful ATDD implementationUse ATDD with Cucumber to describe software in ways businesspeople can understand Test web pages using ATDD toolsBring ATDD to Java with the FitNesse wiki-based acceptance test framework Use examples more effectively in Behavior-Driven Development (BDD)Specify software collaboratively through innovative workshopsImplement more user-friendly and collaborative test automationTest more cleanly, listen to test results, and refactor tests for greater value If you're a tester, analyst, developer, or project manager, this book offers a concrete foundation for achieving real benefits with ATDD now-and it will help you reap even more value as you gain experience.

    This book will help you get better outcomes from retrospectives and from any continuous improvement initiative. It will help you consider how best to prepare for retrospectives, generate innovative insights, achieve valuable outcomes, improve facilitation techniques, keep things fresh and maybe even how to have a bit of fun whilst doing it. This book is for anyone who undertakes continuous improvement of any sort, especially those looking to get better outcomes from retrospectives, either as a participant, facilitator, coach or manager of teams. We include ideas for people with varying levels of experience. So, whether you are just getting started with Scrum and retrospectives, or a veteran of continuous improvement looking to fine-tune or get new ideas, or if your retrospectives have become a bit stale and need re-invigorating, there are ideas in here to support you.

    So, why does conventional wisdom insist that software engineers focus primarily on the design and development of large-scale computing systems?In this collection of essays and articles, key members of Google's Site Reliability Team explain how and why their commitment to the entire lifecycle has enabled the company to successfully build, deploy, monitor, and maintain some of the largest software systems in the world. You'll learn the principles and practices that enable Google engineers to make systems more scalable, reliable, and efficient--lessons directly applicable to your organization.This book is divided into four sections: Introduction--Learn what site reliability engineering is and why it differs from conventional IT industry practicesPrinciples--Examine the patterns, behaviors, and areas of concern that influence the work of a site reliability engineer (SRE)Practices--Understand the theory and practice of an SRE's day-to-day work: building and operating large distributed computing systemsManagement--Explore Google's best practices for training, communication, and meetings that your organization can use

    This comprehensive textbook uses a building-block approach that starts with the fundamental principles of system operation and progresses gradually to complex diagnostic and service procedures. Short sentences, concise definitions, and thousands of color illustrations help students learn quickly and easily. This newly revised text provides thorough coverage of the latest developments in the automotive field, including hybrid drive systems, computer network communication, and tire pressure monitoring systems. Organized around the eight ASE automobile test areas, Modern Automotive Technology is a valuable resource for students preparing for a career in automotive technology, as well as experienced technicians who are preparing for the ASE certification tests.

    You can think of this problem as a variant of the well known "telephone game", where some trivial rumor is repeated from one person to the next until it has become distorted beyond recognition and blown up out of all proportion.Unfortunately, the objects of this telephone game are generally considered cornerstone truths of the discipline, to the point that their acceptance now seems to hinder further progress.In this short ebook, we will take a look at some of those "ground truths": the claimed 10x variation in productivity between developers; the "software crisis"; the cost-of-change curve; the "cone of uncertainty"; and more. We'll hone our scholarship skills by looking up the original source for these ideas and taking a deep dive in the history of their development. We'll assess the real weight of the evidence behind these ideas.And we'll confront the scary prospect of moving the state of the art forward in a discipline that has had the ground kicked from under it.

    Even if you don't have change management in your job description, your job involves change. Change is a given as modern organizations respond to market and technology advances, make improvements, and evolve practices to meet new challenges. This is not a simple process on any level. Often, there is no indisputable right answer, and responding requires trial and error, learning and unlearning. Whatever you choose to do, it will interact with existing policies and structures in unpredictable ways. And there is, quite simply, a natural human resistance to being told to change.Rather than creating more rigorous preconceived plans or imposing change by decree, agile software developer turned organizational change expert Esther Derby offers change by attraction, an approach that is adaptive and responsive and engages people in learning, evolving, and owning the new way. She presents a set of seven heuristics--guides to problem-solving--that empower people to achieve outcomes within broad constraints using their personal ingenuity and creativity.When you work by attraction, you give space and support for people to feel the loss that comes with change and help them see what is valuable about the future you propose. Resistance fades because people feel there is nothing to push against--only something they want to move toward. Derby's approach clears the fog to provide a new way forward that honors people and creates safety for change.

    And they waste the leadership ability that is present throughout an organization, not just at the top. In this visionary book, Karen and Henry Kimsey-House provide a model that harnesses the possibility of many rather than relying on the power of one. They begin with a new definition of leadership itself: “Leaders are those who are responsible for their world.” Which, of course, we all are, or should be—so everyone is a leader. Co-Active Leadership is a deeply collaborative approach but the first of its five dimensions focuses on the individual: leading from within. We must be fully present and live lives of integrity, openheartedness, and self-awareness if we are to make the kind of conscious, creative choices Co-Active Leadership demands. Each of the remaining four dimensions work together holistically. Depending on the situation, you may lead from the front, offering guidance and inspiration; from behind, supporting and encouraging others; from beside, partnering with and supporting other members of your team; or from the field, drawing on insights and wisdom available beyond the rational mind.Co-Active Leadership is the only model to celebrate and honor these different expressions of leadership. It invites all of us to share our expertise and allows collaborative solutions to emerge that would never have been possible otherwise.

    What he did not expect was a response and the result was Conversations with God Book 1. In Book 2, the dialogue expands to deal with the more global topics of geopolitical and metaphysical life on the planet, and the challenges now facing the world. This incredible series contains answers that will change you, your life, and the way you view other beings.

    If you're one of them, The Scrum Field Guide will give you skills and confidence to adopt Scrum more rapidly, more successfully, and with far less pain and fear. Long-time Scrum practitioner Mitch Lacey identifies major challenges associated with early-stage Scrum adoption, as well as deeper issues that emerge after companies have adopted Scrum, and describes how other organizations have overcome them. You'll learn how to gain "quick wins" that build support, and then use the flexibility of Scrum to maximize value creation across the entire process. In 30 brief, engaging chapters, Lacey guides you through everything from defining roles to setting priorities to determining team velocity, choosing a sprint length, and conducting customer reviews. Along the way, he explains why Scrum can seem counterintuitive, offers a solid grounding in the core agile concepts that make it work, and shows where it can (and shouldn't) be modified. Coverage includes Getting teams on board, and bringing new team members aboard after you've started Creating a "definition of done" for the team and organization Implementing the strong technical practices that are indispensable for agile success Balancing predictability and adaptability in release planning Keeping defects in check Running productive daily standup meetings Keeping people engaged with pair programming Managing culture clashes on Scrum teams Performing "emergency procedures" to get sprints back on track Establishing a pace your team can truly sustain Accurately costing projects, and measuring the value they deliver Documenting Scrum projects effectively Prioritizing and estimating large backlogs Integrating outsourced and offshored components Packed with real-world examples from Lacey's own experience, this book is invaluable to everyone transitioning to agile: developers, architects, testers, managers, and project owners alike.

    This work includes the practices and techniques of Responsibility-Driven Design, and show how to apply them as you develop modern object-based applications. It is suitable for software designers and students.

    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.

    But how much time you actually spend on your projects, and how much time do you spend responding to emergencies? This book will introduce you to different ways of ordering all of the projects you are working on now, and help you figure out how to staff those projects--even when you've run out of project teams to do the work. Once you learn to manage your portfolio better, you'll avoid emergency "firedrills." The trick is adopting lean and agile approaches to projects, whether they are software projects, projects that include hardware, or projects that depend on chunks of functionality from other suppliers. You may be accustomed to spending time in meetings where you still don't have the data you need to evaluate your projects. Here, with a few measures, you'll be able to quickly evaluate each project and come to a decision quickly. You'll learn how to define your team's, group's, or department's mission with none of the buzzwords that normally accompany a mission statement. Armed with the work and the mission, you can make those decisions that define the true leaders in the organization.