According to the August Forrester Report, 56 percent of IT managers interviewed at Global 2,500 companies are already using some type of open source software in their infrastructure and another 6 percent will install it in the next two years. This revolutionary model for collaborative software development is being embraced and studied by many of the biggest players in the high-tech industry, from Sun Microsystems to IBM to Intel.The Cathedral & the Bazaar is a must for anyone who cares about the future of the computer industry or the dynamics of the information economy. Already, billions of dollars have been made and lost based on the ideas in this book. Its conclusions will be studied, debated, and implemented for years to come. According to Bob Young, "This is Eric Raymond's great contribution to the success of the open source revolution, to the adoption of Linux-based operating systems, and to the success of open source users and the companies that supply them."The interest in open source software development has grown enormously in the past year. This revised and expanded paperback edition includes new material on open source developments in 1999 and 2000. Raymond's clear and effective writing style accurately describing the benefits of open source software has been key to its success. With major vendors creating acceptance for open source within companies, independent vendors will become the open source story in 2001.

    This book explains the technical aspects of hacking, including stack based overflows, heap based overflows, string exploits, return-into-libc, shellcode, and cryptographic attacks on 802.11b.

    But Don Casey shows us that it doesn't need to be that way. You can learn what you need to know by rapping,poking,looking,and listening. But you must be able to recognize problem symptoms when they arise. This book shows you how. Hull,deck,rig,interior,engine,electrical system—it's all here. You'll still want to hire a surveyor before buying a boat,and Casey guides you through that,too. In the meantime,though,whether you're maintaining or shopping,you can save hundreds,even thousands of dollars in survey fees. The Tolerance of Fiberglass For Neglect And Abuse Is Legendary—And An Astounding Number Of Sailboats Built In The Last 35 Years Are Still Around. There Are Bargains Aplenty—And The Best One Of All,With Some Overdue Attention,Just Might Be The Boat You Already Own Are those cracks in the gelcoat? Should the deck yield underfoot like that? Are those rivets in the toerail,and why are they loose? Why doesn't the head door close? Should there be rust on the keel bolts? What is that bulge in the hull? If any of these indicate real trouble,it is or could become your trouble. Here is all you'll need to learn where to look and what to look for. Whether you're shopping or prioritizing maintenance tasks,this book will save you money and perhaps even disaster.

    Previously undocumented, these 23 patterns allow designers to create more flexible, elegant, and ultimately reusable designs without having to rediscover the design solutions themselves.The authors begin by describing what patterns are and how they can help you design object-oriented software. They then go on to systematically name, explain, evaluate, and catalog recurring designs in object-oriented systems. With Design Patterns as your guide, you will learn how these important patterns fit into the software development process, and how you can leverage them to solve your own design problems most efficiently. Each pattern describes the circumstances in which it is applicable, when it can be applied in view of other design constraints, and the consequences and trade-offs of using the pattern within a larger design. All patterns are compiled from real systems and are based on real-world examples. Each pattern also includes code that demonstrates how it may be implemented in object-oriented programming languages like C++ or Smalltalk.

    The author successfully introduces Maxwell's equations, wave propagation, network analysis, and design principles as applied to modern microwave engineering. A considerable amount of material in this book is related to the design of specific microwave circuits and components, for both practical and motivational value. It also presents the analysis and logic behind these designs so that the reader can see and understand the process of applying the fundamental concepts to arrive at useful results. The derivations are well laid out and the majority of each chapter's formulas are displayed in a nice tabular format every few pages. This Third Edition offers greatly expanded coverage with new material on: Noise; Nonlinear effects; RF MEMs; transistor power amplifiers; FET mixers; oscillator phase noise; transistor oscillators and frequency multiplier.

    

    It is the journey of a young woman who discovers herself in the stories of other women who share her same name and coincidentally share experiences of violence and abuse that plagued her own childhood. Through her physical journey across the country she is thrust into her own emotional journey. She embraces each woman she meets, is strengthened by their connections, confronts the father that molested her, and ultimately finds faith, divine purpose, and wholeness.

    By scale, we mean having numbers of users in the millions and being built by large engineering teams.For mobile engineers, this book is a blueprint for modern app engineering approaches. For non-mobile engineers and managers, it is a resource with which to build empathy and appreciation for the complexity of world-class mobile engineering.

    This is the undisputed go-to guide to Rust, written by two members of the Rust core team, with feedback and contributions from 42 members of the community. The book assumes that you’ve written code in another programming language but makes no assumptions about which one, meaning the material is accessible and useful to developers from a wide variety of programming backgrounds.Known by the Rust community as "The Book," The Rust Programming Language includes concept chapters, where you’ll learn about a particular aspect of Rust, and project chapters, where you’ll apply what you’ve learned so far to build small programs.The Book opens with a quick hands-on project to introduce the basics then explores key concepts in depth, such as ownership, the type system, error handling, and fearless concurrency. Next come detailed explanations of Rust-oriented perspectives on topics like pattern matching, iterators, and smart pointers, with concrete examples and exercises--taking you from theory to practice.The Rust Programming Language will show you how to: Grasp important concepts unique to Rust like ownership, borrowing, and lifetimes Use Cargo, Rust’s built-in package manager, to build and maintain your code, including downloading and building dependencies Effectively use Rust’s zero-cost abstractions and employ your ownYou’ll learn to develop reliable code that’s speed and memory efficient, while avoiding the infamous and arcane programming pitfalls common at the systems level. When you need to dive down into lower-level control, this guide will show you how without taking on the customary risk of crashes or security holes and without requiring you to learn the fine points of a fickle toolchain.You’ll also learn how to create command line programs, build single- and multithreaded web servers, and much more.The Rust Programming Language fully embraces Rust’s potential to empower its users. This friendly and approachable guide will help you build not only your knowledge of Rust but also your ability to program with confidence in a wider variety of domains.

    In this book, experts from Google share best practices to help your organization design scalable and reliable systems that are fundamentally secure.Two previous O'Reilly books from Google--Site Reliability Engineering and The Site Reliability Workbook--demonstrated how and why a commitment to the entire service lifecycle enables organizations to successfully build, deploy, monitor, and maintain software systems. In this latest guide, the authors offer insights into system design, implementation, and maintenance from practitioners who specialize in security and reliability. They also discuss how building and adopting their recommended best practices requires a culture that is supportive of such change.You'll learn about secure and reliable systems through:Design strategiesRecommendations for coding, testing, and debugging practicesStrategies to prepare for, respond to, and recover from incidentsCultural best practices that help teams across your organization collaborate effectively

    We dive down to see coral reefs, not realizing that an ingredient in our sunscreen feeds a virus that kills the reef. We wear organic cotton t-shirts, but don’t know that its dyes may put factory workers at risk for leukemia. In Ecological Intelligence, Daniel Goleman reveals why so many of the products that are labeled green are a “mirage,” and illuminates our wild inconsistencies in response to the ecological crisis.Drawing on cutting-edge research, Goleman explains why we as shoppers are in the dark over the hidden impacts of the goods and services we make and consume, victims of a blackout of information about the detrimental effects of producing, shipping, packaging, distributing, and discarding the goods we buy.But the balance of power is about to shift from seller to buyer, as a new generation of technologies informs us of the ecological facts about products at the point of purchase. This “radical transparency” will enable consumers to make smarter purchasing decisions, and will drive companies to rethink and reform their businesses, ushering in, Goleman claims, a new age of competitive advantage.

    While no two are identical, Brandel Chamblee, the highly regarded television analyst and former PGA Tour professional, once noticed that the best players of all time have shared similar positions in each part of the swing, from the grip and setup to the footwork, backswing, and follow-through. Since then, Chamblee, a student of the game’s history, has used scientific precision and thoroughness to make a study of the common swing positions of the greats. Now, in The Anatomy of Greatness, he shares what he has learned, offering hundreds of photographs as proof, to show us how we can easily incorporate his findings into our own swings to hit the ball farther, straighter, and more consistently. What does it tell us that the majority of the greats—from Jack Nicklaus and Byron Nelson to modern masters like Tiger Woods—employ a “strong” grip on the club? How did legends like Ben Hogan, Sam Snead, Mickey Wright, and Gary Player unlock hidden power and control by turning in the right knee at address? Why are some modern teachers preaching quiet footwork when forty-eight of the top fifty golfers of all time lifted their left heels on the backswing, allowing them to build power? At the same time that Chamblee is encouraging certain swing virtues, he also debunks a number of popular—but misguided—swing philosophies that have been hindering golfers for years. The result is perhaps the best and clearest explanation of how to hit a golf ball ever published. Golfers can take The Anatomy of Greatness to the driving range and use Chamblee’s clear explanations to build better swings—and get more speed and consistency into their swings—immediately. This book is like having a series of private lessons from the best golfers of all time, and it will help golfers build swings that make the game easier and more fun.

    Crafting an engrossing journey from the gushing Pennsylvania oil fields of the 1860s to today's fraught and fractious Middle East, Crude Volatility explains how past periods of stability and volatility in oil prices help us understand the new boom-bust era. Oil's notorious volatility has always been considered a scourge afflicting not only the oil industry but also the broader economy and geopolitical landscape; Robert McNally makes sense of how oil became so central to our world and why it is subject to such extreme price fluctuations.Tracing a history marked by conflict, intrigue, and extreme uncertainty, McNally shows how--even from the oil industry's first years--wild and harmful price volatility prompted industry leaders and officials to undertake extraordinary efforts to stabilize oil prices by controlling production. Herculean market interventions--first, by Rockefeller's Standard Oil, then, by U.S. state regulators in partnership with major international oil companies, and, finally, by OPEC--succeeded to varying degrees in taming the beast. McNally, a veteran oil market and policy expert, explains the consequences of the ebbing of OPEC's power, debunking myths and offering recommendations--including mistakes to avoid--as we confront the unwelcome return of boom and bust oil prices.

    The Productive Programmer offers critical timesaving and productivity tools that you can adopt right away, no matter what platform you use. Master developer Neal Ford not only offers advice on the mechanics of productivity-how to work smarter, spurn interruptions, get the most out your computer, and avoid repetition-he also details valuable practices that will help you elude common traps, improve your code, and become more valuable to your team. You'll learn to:Write the test before you write the codeManage the lifecycle of your objects fastidiously Build only what you need now, not what you might need later Apply ancient philosophies to software development Question authority, rather than blindly adhere to standardsMake hard things easier and impossible things possible through meta-programming Be sure all code within a method is at the same level of abstraction Pick the right editor and assemble the best tools for the job This isn't theory, but the fruits of Ford's real-world experience as an Application Architect at the global IT consultancy ThoughtWorks. Whether you're a beginner or a pro with years of experience, you'll improve your work and your career with the simple and straightforward principles in The Productive Programmer.

    What has been missing from the agile literature is a solid, practical book on the specifics of developing large projects in an agile way. Dean Leffingwell's book Scaling Software Agility fills this gap admirably. It offers a practical guide to large project issues such as architecture, requirements development, multi-level release planning, and team organization. Leffingwell's book is a necessary guide for large projects and large organizations making the transition to agile development." -Jim Highsmith, director, Agile Practice, Cutter Consortium, author of Agile Project Management "There's tension between building software fast and delivering software that lasts, between being ultra-responsive to changes in the market and maintaining a degree of stability. In his latest work, Scaling Software Agility, Dean Leffingwell shows how to achieve a pragmatic balance among these forces. Leffingwell's observations of the problem, his advice on the solution, and his description of the resulting best practices come from experience: he's been there, done that, and has seen what's worked." -Grady Booch, IBM Fellow Agile development practices, while still controversial in some circles, offer undeniable benefits: faster time to market, better responsiveness to changing customer requirements, and higher quality. However, agile practices have been defined and recommended primarily to small teams. In Scaling Software Agility, Dean Leffingwell describes how agile methods can be applied to enterprise-class development. Part I provides an overview of the most common and effective agile methods. Part II describes seven best practices of agility that natively scale to the enterprise level. Part III describes an additional set of seven organizational capabilities that companies can master to achieve the full benefits of software agility on an enterprise scale. This book is invaluable to software developers, testers and QA personnel, managers and team leads, as well as to executives of software organizations whose objective is to increase the quality and productivity of the software development process but who are faced with all the challenges of developing software on an enterprise scale. Foreword Preface Acknowledgments About the Author Part I: Overview of Software Agility Chapter 1: Introduction to Agile Methods Chapter 2: Why the Waterfall Model Doesn't Work Chapter 3: The Essence of XP Chapter 4: The Essence of Scrum Chapter 5: The Essence of RUP Chapter 6: Lean Software, DSDM, and FDD Chapter 7: The Essence of Agile Chapter 8: The Challenge of Scaling Agile Part II: Seven Agile Team Practices That Scale Chapter 9: The Define/Build/Test Component Team Chapter 10: Two Levels of Planning and Tracking Chapter 11: Mastering the Iteration Chapter 12: Smaller, More Frequent Releases Chapter 13: Concurrent Testing Chapter 14: Continuous Integration Chapter 15: Regular Reflection and Adaptation Part III: Creating the Agile Enterprise Chapter 16: Intentional Architecture Chapter 17: Lean Requirements at Scale: Vision, Roadmap, and Just-in-Time Elaboration Chapter 18: Systems of Systems and the Agile Release Train Chapter 19: Managing Highly Distributed Development Chapter 20: Impact on Customers and Operations Chapter 21: Changing the Organization Chapter 22: Measuring Business Performance Conclusion: Agility Works at Scale Bibliography Index