If you're a developer familiar with Go, this practical book demonstrates best practices and patterns to help you incorporate concurrency into your systems.Author Katherine Cox-Buday takes you step-by-step through the process. You'll understand how Go chooses to model concurrency, what issues arise from this model, and how you can compose primitives within this model to solve problems. Learn the skills and tooling you need to confidently write and implement concurrent systems of any size.Understand how Go addresses fundamental problems that make concurrency difficult to do correctlyLearn the key differences between concurrency and parallelismDig into the syntax of Go's memory synchronization primitivesForm patterns with these primitives to write maintainable concurrent codeCompose patterns into a series of practices that enable you to write large, distributed systems that scaleLearn the sophistication behind goroutines and how Go's runtime stitches everything together

    Multi-tiered object-oriented platforms, such as Java and .NET, have become commonplace. These new tools and technologies are capable of building powerful applications, but they are not easily implemented. Common failures in enterprise applications often occur because their developers do not understand the architectural lessons that experienced object developers have learned. Patterns of Enterprise Application Architecture is written in direct response to the stiff challenges that face enterprise application developers. The author, noted object-oriented designer Martin Fowler, noticed that despite changes in technology--from Smalltalk to CORBA to Java to .NET--the same basic design ideas can be adapted and applied to solve common problems. With the help of an expert group of contributors, Martin distills over forty recurring solutions into patterns. The result is an indispensable handbook of solutions that are applicable to any enterprise application platform. This book is actually two books in one. The first section is a short tutorial on developing enterprise applications, which you can read from start to finish to understand the scope of the book's lessons. The next section, the bulk of the book, is a detailed reference to the patterns themselves. Each pattern provides usage and implementation information, as well as detailed code examples in Java or C#. The entire book is also richly illustrated with UML diagrams to further explain the concepts. Armed with this book, you will have the knowledge necessary to make important architectural decisions about building an enterprise application and the proven patterns for use when building them. The topics covered include - Dividing an enterprise application into layers - The major approaches to organizing business logic - An in-depth treatment of mapping between objects and relational databases - Using Model-View-Controller to organize a Web presentation - Handling concurrency for data that spans multiple transactions - Designing distributed object interfaces

    Some books try to give you copy-and-paste instructions for how to deal with every single system issue that may arise, but How Linux Works actually shows you how the Linux system functions so that you can come up with your own solutions. After a guided tour of filesystems, the boot sequence, system management basics, and networking, author Brian Ward delves into open-ended topics such as development tools, custom kernels, and buying hardware, all from an administrator's point of view. With a mixture of background theory and real-world examples, this book shows both "how" to administer Linux, and "why" each particular technique works, so that you will know how to make Linux work for you.

    "His book is very compatible with XP. It is not about drawing pictures of a domain; it is about how you think of it, the language you use to talk about it, and how you organize your software to reflect your improving understanding of it. Eric thinks that learning about your problem domain is as likely to happen at the end of your project as at the beginning, and so refactoring is a big part of his technique. "The book is a fun read. Eric has lots of interesting stories, and he has a way with words. I see this book as essential reading for software developers--it is a future classic." --Ralph Johnson, author of Design Patterns "If you don't think you are getting value from your investment in object-oriented programming, this book will tell you what you've forgotten to do. "Eric Evans convincingly argues for the importance of domain modeling as the central focus of development and provides a solid framework and set of techniques for accomplishing it. This is timeless wisdom, and will hold up long after the methodologies du jour have gone out of fashion." --Dave Collins, author of Designing Object-Oriented User Interfaces "Eric weaves real-world experience modeling--and building--business applications into a practical, useful book. Written from the perspective of a trusted practitioner, Eric's descriptions of ubiquitous language, the benefits of sharing models with users, object life-cycle management, logical and physical application structuring, and the process and results of deep refactoring are major contributions to our field." --Luke Hohmann, author of Beyond Software Architecture "This book belongs on the shelf of every thoughtful software developer." --Kent Beck "What Eric has managed to capture is a part of the design process that experienced object designers have always used, but that we have been singularly unsuccessful as a group in conveying to the rest of the industry. We've given away bits and pieces of this knowledge...but we've never organized and systematized the principles of building domain logic. This book is important." --Kyle Brown, author of Enterprise Java(TM) Programming with IBM(R) WebSphere(R) The software development community widely acknowledges that domain modeling is central to software design. Through domain models, software developers are able to express rich functionality and translate it into a software implementation that truly serves the needs of its users. But despite its obvious importance, there are few practical resources that explain how to incorporate effective domain modeling into the software development process. Domain-Driven Design fills that need. This is not a book about specific technologies. It offers readers a systematic approach to domain-driven design, presenting an extensive set of design best practices, experience-based techniques, and fundamental principles that facilitate the development of software projects facing complex domains. Intertwining design and development practice, this book incorporates numerous examples based on actual projects to illustrate the application of domain-driven design to real-world software development. Readers learn how to use a domain model to make a complex development effort more focused and dynamic. A core of best practices and standard patterns provides a common language for the development team. A shift in emphasis--refactoring not just the code but the model underlying the code--in combination with the frequent iterations of Agile development leads to deeper insight into domains and enhanced communication between domain expert and programmer. Domain-Driven Design then builds on this foundation, and addresses modeling and design for complex systems and larger organizations.Specific topics covered include:Getting all team members to speak the same language Connecting model and implementation more deeply Sharpening key distinctions in a model Managing the lifecycle of a domain object Writing domain code that is safe to combine in elaborate ways Making complex code obvious and predictable Formulating a domain vision statement Distilling the core of a complex domain Digging out implicit concepts needed in the model Applying analysis patterns Relating design patterns to the model Maintaining model integrity in a large system Dealing with coexisting models on the same project Organizing systems with large-scale structures Recognizing and responding to modeling breakthroughs With this book in hand, object-oriented developers, system analysts, and designers will have the guidance they need to organize and focus their work, create rich and useful domain models, and leverage those models into quality, long-lasting software implementations.

    In this book, you'll learn how to become an entrepreneur, driving your career in the direction of your choosing. You'll learn how to build your software development career step by step, following the same path that you would follow if you were building, marketing, and selling a product. After all, your skills themselves are a product. The choices you make about which technologies to focus on and which business domains to master have at least as much impact on your success as your technical knowledge itself--don't let those choices be accidental. We'll walk through all aspects of the decision-making process, so you can ensure that you're investing your time and energy in the right areas. You'll develop a structured plan for keeping your mind engaged and your skills fresh. You'll learn how to assess your skills in terms of where they fit on the value chain, driving you away from commodity skills and toward those that are in high demand. Through a mix of high-level, thought-provoking essays and tactical "Act on It" sections, you will come away with concrete plans you can put into action immediately. You'll also get a chance to read the perspectives of several highly successful members of our industry from a variety of career paths. As with any product or service, if nobody knows what you're selling, nobody will buy. We'll walk through the often-neglected world of marketing, and you'll create a plan to market yourself both inside your company and to the industry in general. Above all, you'll see how you can set the direction of your career, leading to a more fulfilling and remarkable professional life.

    A love against all odds…Elizabeth Gladstone has always been- and always will be- a wild lady. People would expect the daughter of the Earl of Waymouth to be a well-mannered lady, but she keeps finding new ways to shock the ton.James Graham, the widowed Duke of Darrington, has the exact same reaction at first. Later he will come to realize that she may be the one to end his loneliness.But there is someone that will not tolerate their union, someone dangerous that will do anything to further their nefarious goals…James will have to beat the enemy in their own game if he wishes to save the fierce lady that now holds his heart…

     At any given moment, somewhere in the world someone struggles with the same software design problems you have. You know you don't want to reinvent the wheel (or worse, a flat tire), so you look to Design Patterns--the lessons learned by those who've faced the same problems. With Design Patterns, you get to take advantage of the best practices and experience of others, so that you can spend your time on...something else. Something more challenging. Something more complex. Something more fun. You want to learn about the patterns that matter--why to use them, when to use them, how to use them (and when NOT to use them). But you don't just want to see how patterns look in a book, you want to know how they look "in the wild". In their native environment. In other words, in real world applications. You also want to learn how patterns are used in the Java API, and how to exploit Java's built-in pattern support in your own code. You want to learn the real OO design principles and why everything your boss told you about inheritance might be wrong (and what to do instead). You want to learn how those principles will help the next time you're up a creek without a design pattern. Most importantly, you want to learn the "secret language" of Design Patterns so that you can hold your own with your co-worker (and impress cocktail party guests) when he casually mentions his stunningly clever use of Command, Facade, Proxy, and Factory in between sips of a martini. You'll easily counter with your deep understanding of why Singleton isn't as simple as it sounds, how the Factory is so often misunderstood, or on the real relationship between Decorator, Facade and Adapter. With Head First Design Patterns, you'll avoid the embarrassment of thinking Decorator is something from the "Trading Spaces" show. Best of all, in a way that won't put you to sleep! We think your time is too important (and too short) to spend it struggling with academic texts. If you've read a Head First book, you know what to expect--a visually rich format designed for the way your brain works. Using the latest research in neurobiology, cognitive science, and learning theory, Head First Design Patterns will load patterns into your brain in a way that sticks. In a way that lets you put them to work immediately. In a way that makes you better at solving software design problems, and better at speaking the language of patterns with others on your team.

    Providing strategies and solutions for the managers of today, this book offers answers for improving employee commitment and profitability by strategically acknowledging employee effort. How is it done? The deceptively simply answer: with carrots.

    The book transported my imagination where I was right inside a courtroom drama…. Fantastic, thoroughly recommend this book!” “Both educational and entertaining …I thought the author did an excellent job of introducing Americans to the British legal system (which bemuses many of us as much as cricket). I always love good summations, and these were of high calibre… The author demonstrated a mastery of providing meaningful snippets of personal life essentially in textual asides.”“Author John Burton, Q.C. knows of whereof he writes, and his book, as well as being a well plotted, well written and highly enjoyable murder trial novel, is an education in the English criminal justice system, warts and all… There is also a fascinating subplot about the business of English criminal lawyers and the intrigues of the “Chambers” in which Brant practices.”“…..the skills of both the Prosecution, Joanna Glass QC and the Defence are on display. The reader is made to feel part of the Defence team.”David Brant QC is a newly appointed Queen’s Counsel, a “Silk”, a Criminal Barrister struggling against ever-dwindling legal aid funds and a lack of work. His Chambers is also suffering internal and external pressures and his Senior Clerk seems to only serve a select few. Life at the Bar is more challenging than ever before. His personal life is not much better. Having faced an acrimonious divorce after an inadvisable liaison with a female Solicitor, his life has become a mixture of enforced rest and ever increasing consumption of Claret and Rioja Reserva. However, after a night out with his Senior Clerk, he is instructed to defend in a Murder trial, leading one of the instructing solicitor’s firm’s In-House Barristers.The client is a Mr Damien Clarke, a cocaine addict charged with killing a known associate, Usman Hussain, after a night of smoking crack together in Hussain’s flat. The evidence against Damien appears almost overwhelming and as the case progresses towards trial it is strengthened by further forensic scientific evidence.David Brant QC must use all his forensic skill to combat the array of damning evidence against Damien and to pit his wits against a highly competent Prosecutor and a Judge who has a personal dislike for him. The Silk Brief takes us from before David Brant QC is instructed, through his early preparation of the case and conferences with the client in the High Security Belmarsh prison, through to the trial and verdict. It provides the day by day record of a murder trial including the examination and cross-examination of lay and expert witnesses, Counsel’s speeches, the Judges summing up and finally the jury’s deliberations and verdict. Although a work of fiction, the author draws extensively on his knowledge of the Criminal Bar of England and Wales, having practiced as a Criminal Barrister for over thirty years, latterly as Queen’s Counsel, conducting many trials, including murder trials in the Central Criminal Court, known colloquially and fondly as “The Old Bailey”.

    In 1964, I embarked on a journey that was to be my life's adventure.  I hired on as a pilot for Air America and its clandestine operations in Southeast Asia.      Flying for the CIA's secret airline was a dream come true.  Air America's operations were unknown.  Its schedules were irregular.  Its pilots were shadow people.  It was the world of spooks, covert air ops and adventure.  I had already been a pilot for more than half of my life when I left my home in Detroit for the wild escapades that awaited me in Southeast Asia.  Air America had been the pinnacle of my life and, had the trajectory remained steady, my world and my career should have gone onward and upward from that point.      The intent of telling my story is to take the reader on an historical journey of a little-known place in time through my own personal account.  Within the context of history, my narrative is not to be considered anything but my own experience.     The ranks of Air America were comprised of a host of patriotic professionals who deserve a place of honor in the annals of history.  However, many colorful characters wore the Air America wings, and inside the course of my narrative, the reader will be subjected to people and situations that cannot be filed neatly under anything resembling normal sanity.      Most names, except those of a known or high-ranking or public nature, and those I wish to recognize for heroic performances, have been changed to protect the innocent and guilty alike.

    

    For Alex Troutt, a trip back home for a much-needed summer vacation proves only one thing: greed rules. But how it takes root could destroy her world. Fueled by the lust of power and money, the shadow of death envelopes her seaside hometown, including those closest to Alex. But as disconnected investigations converge into one focal point, Alex will stop at nothing to blow the entire crime ring straight to hell—even if she has to make the ultimate sacrifice…her life. AT Dusk (Book 5) Eyes are the window to the soul…unless there isn't a soul to be found.  A little boy makes his first kill—and he likes it. He is cunning, charming, and without remorse.      He is a sociopath.     As boy turns to man, what lies inside takes root. He will make a mark on Boston unlike any other, and FBI Special Agent Alex Troutt must figure out how to stop him.     But when she and her close-knit team move in closer, the stakes become much higher as the case takes on a more personal tone. It’s a frantic race to stop a manipulative killer before his web of deceit and destruction escalates into a blood bath of haunting proportions.  AT Last (Book 6) Thirty years after losing a parent to a hit-and-run drunk driver, FBI agent Alex Troutt finally confronts the killer--the same man who just murdered the Boston police chief. And what Alex pulls from him shatters her core. Armed with little more than hope and a shred of decades-old evidence, Alex chases a memory from her past, hoping that she'll find the mother she never really had. With her old buddy Archie on board --as much as ever can be -- the hunt takes her deep into the foothills of West Virginia. A fanatical religious cult has created its own society. Clinging to a whisper of hope, Alex must out-think and out-duel everyone in her path to right a thirty-year wrong. Will Alex’s quest to find the truth destroy her life all over again?

    By using the Framework you will learn architectural best practices for designing and operating reliable, secure, efficient, and cost-effective systems in the cloud.

    While some fear is healthy (often viewed as a conscience that tells programmers to be careful!), the author believes that byproducts of fear include tentative, grumpy, and uncommunicative programmers who are unable to absorb constructive criticism. When programming teams buy into TDD, they immediately see positive results. They eliminate the fear involved in their jobs, and are better equipped to tackle the difficult challenges that face them. TDD eliminates tentative traits, it teaches programmers to communicate, and it encourages team members to seek out criticism However, even the author admits that grumpiness must be worked out individually! In short, the premise behind TDD is that code should be continually tested and refactored. Kent Beck teaches programmers by example, so they can painlessly and dramatically increase the quality of their work.

    Every integrated software development environment in the world--open-source, standards-based, and proprietary--now supports UML and, more importantly, the model-driven approach to software development. This makes learning the newest UML standard, UML 2.0, critical for all software developers--and there isn't a better choice than this clear, step-by-step guide to learning the language."--Richard Mark Soley, Chairman and CEO, OMGIf you're like most software developers, you're building systems that are increasingly complex. Whether you're creating a desktop application or an enterprise system, complexity is the big hairy monster you must manage.The Unified Modeling Language (UML) helps you manage this complexity. Whether you're looking to use UML as a blueprint language, a sketch tool, or as a programming language, this book will give you the need-to-know information on how to apply UML to your project. While there are plenty of books available that describe UML, Learning UML 2.0 will show you how to use it. Topics covered include:Capturing your system's requirements in your model to help you ensure that your designs meet your users' needsModeling the parts of your system and their relationshipsModeling how the parts of your system work together to meet your system's requirementsModeling how your system moves into the real world, capturing how your system will be deployedEngaging and accessible, this book shows you how to use UML to craft and communicate your project's design. Russ Miles and Kim Hamilton have written a pragmatic introduction to UML based on hard-earned practice, not theory. Regardless of the software process or methodology you use, this book is the one source you need to get up and running with UML 2.0.Russ Miles is a software engineer for General Dynamics UK, where he works with Java and Distributed Systems, although his passion at the moment is Aspect Orientation and, in particular, AspectJ. Kim Hamilton is a senior software engineer at Northrop Grumman, where she's designed and implemented a variety of systems including web applications and distributed systems, with frequent detours into algorithms development.