Grady Booch

Grady Booch

scientist, storyteller, philosopher

110+ Book Recommendations by Grady Booch

  • @fredzannarbor @SpaceForceCSO See The First Information War: The Story of Communications, Computers, and Intelligence Systems in the Persian Gulf War https://t.co/1sAbTdhtW2

  • Introduction. Architectural styles. Case studies. Shared information systems. Architectural design guidance. Formal models and specifications. Linguistics issues. Tools for architectural design. Education of software architects.

    @stewartbrand @patrickbourke There are many ways one could divide software systems: domain and architectural style are the two dimensions I find most interesting. As for style, Mary Shaw/David Garland’s book (Software Architecture) started it all, and you’ll find other resources here https://t.co/O5iuSX3g2K

  • The approach to and understanding of software engineering at Google is unlike any other company. With this book, you'll get a candid and insightful look at how software is constructed and maintained by some of the world's leading practitioners. Titus Winters, Tom Manshreck, and Hyrum K. Wright, software engineers and a technical writer at Google, reframe how software engineering is practiced and taught: from an emphasis on programming to an emphasis on software engineering, which roughly translates to programming over time. You'll learn: Fundamental differences between software engineering and programming How an organization effectively manages a living codebase and efficiently responds to inevitable change Why culture (and recognizing it) is important, and how processes, practices, and tools come into play.

    Signal boost for their book! https://t.co/OMrD2QIFV9 https://t.co/XtIQC0GpWy

  • "People sometimes ask me what they should read to find out about artificial intelligence. Herbert Simon's book The Sciences of the Artificial is always on the list I give them. Every page issues a challenge to conventional thinking, and the layman who digests it well will certainly understand what the field of artificial intelligence hopes to accomplish. I recommend it in the same spirit that I recommend Freud to people who ask about psychoanalysis, or Piaget to those who ask about child psychology: If you want to learn about a subject, start by reading its founding fathers." -- George A. Miller, "Complex Information Processing" Continuing his exploration of the organization of complexity and the science of design, this new edition of Herbert Simon's classic work on artificial intelligence adds a chapter that sorts out the current themes and tools -- chaos, adaptive systems, genetic algorithms -- for analyzing complexity and complex systems.

    @jon_moore @mtnygard All that is old is new again. I don't think those concepts ever went out of style; the were always there, but just hidden by the latest shiny thing. https://t.co/U26JUtI6Xk https://t.co/8qY5EHIA27

  • Today's programmers don't develop software systems from scratch. Instead, they spend their time fixing, extending, modifying, and enhancing existing software. Legacy systems often turn into an unwieldy mess that becomes increasingly difficult to modify, and with architecture that continually accumulates technical debt. Carola Lilienthal has analyzed more than 300 software systems written in Java, C#, C++, PHP, ABAP, and TypeScript and, together with her teams, has successfully refactored them. This book condenses her experience with monolithic systems, architectural and design patterns, layered architectures, domain-driven design, and microservices. With more than 200 color images from real-world systems, good and sub-optimal sample solutions are presented in a comprehensible and thorough way, while recommendations and suggestions based on practical projects allow the reader to directly apply the author's knowledge to their daily work.. "Throughout the book, Dr. Lilienthal has provided sound advice on diagnosing, understanding, disentangling, and ultimately preventing the issues that make software systems brittle and subject to breakage. In addition to the technical examples that you'd expect in a book on software architecture, she takes the time to dive into the behavioral and human aspects that impact sustainability and, in my experience, are inextricably linked to the health of a codebase. She also expertly zooms out, exploring architecture concepts such as domains and layers, and then zooms in to the class level where your typical developer works day-to-day. This holistic approach is crucial for implementing long-lasting change." From the Foreword of Andrea Goulet CEO, Corgibytes Founder, Legacy Code Rocks

    @dsp_de @Cairolali @einarwh The book, for those who wish to buy it: https://t.co/eIaj0zqe7w (I enjoyed it!)

  • Systemantics

    John Gall

    @adymitruk See this classic book: https://t.co/MqWWmTcJiM

  • In Cognitive Architecture, the authors review new findings in psychology and neuroscience to help architects and planners better understand their clients as the sophisticated mammals they are, arriving in the world with built-in responses to the environment that have evolved over millennia. The book outlines four main principles---Edges Matter, the fact people are a thigmotactic or a 'wall-hugging' species; Patterns Matter, how we are visually-oriented; Shapes Carry Weight, how our preference for bilateral symmetrical forms is biological; and finally, Storytelling is Key, how our narrative proclivities, unique to our species, play a role in successful place-making. The book takes an inside-out approach to design, arguing that the more we understand human behavior, the better we can design for it. The text suggests new ways to analyze current designs before they are built, allowing the designer to anticipate a user's future experience. More than one hundred photographs and drawings illustrate its key concepts. Six exercises and additional case studies suggest particular topics - from the significance of face-processing in the human brain to our fascination with fractals - for further study.

    Today's light reading: https://t.co/EPZg34QXeS https://t.co/lHohxnjkGz

  • Fractals are characterized by the repetition of similar patterns at ever-diminishing scales. Fractal geometry has emerged as one of the most exciting frontiers on the border between mathematics and information technology and can be seen in many of the swirling patterns produced by computer graphics. It has become a new tool for modeling in biology, geology, and other natural sciences. Anthropologists have observed that the patterns produced in different cultures can be characterized by specific design themes. In Europe and America, we often see cities laid out in a grid pattern of straight streets and right-angle corners. In contrast, traditional African settlements tend to use fractal structures-circles of circles of circular dwellings, rectangular walls enclosing ever-smaller rectangles, and streets in which broad avenues branch down to tiny footpaths with striking geometric repetition. These indigenous fractals are not limited to architecture; their recursive patterns echo throughout many disparate African designs and knowledge systems. Drawing on interviews with African designers, artists, and scientists, Ron Eglash investigates fractals in African architecture, traditional hairstyling, textiles, sculpture, painting, carving, metalwork, religion, games, practical craft, quantitative techniques, and symbolic systems. He also examines the political and social implications of the existence of African fractal geometry. His book makes a unique contribution to the study of mathematics, African culture, anthropology, and computer simulations.

    @MCHammer Also, please meet @roneglash and check out his remarkable book "African Fractals: Modern Computing and Indigenous Design". https://t.co/5K9I0dtcQb

  • Digitizing Race

    Lisa Nakamura

    Lisa Nakamura refers to case studies of popular yet rarely evaluated uses of the Internet, such as pregnancy websites, instant messaging, and online petitions and quizzes, to look at the emergence of race-, ethnic-, and gender-identified visual cultures.

    @GreggleP @unclebobmartin https://t.co/H9vvt2mwU1

  • "Digital media technologies like the Internet create and host the social networks, virtual worlds, online communities, and media texts where it was once thought that we would all be the same, anonymous users with infinite powers. Instead, the essays in Race After the Internet show us that the Internet and other computer-based technologies are complex topographies of power and privilege, made up of walled gardens, new (plat)forms of economic and technological exclusion, and both new and old styles of race as code, interaction, and image. Investigating how racialization and racism are changing in web 2.0 digital media culture, Race After the Internet contains interdisciplinary essays on the shifting terrain of racial identity and its connections to digital media, including Facebook and MySpace, YouTube and viral video, WiFi infrastructure, the One Laptop Per Child (OLPC) program, genetic ancestry testing, DNA databases in health and law enforcement, and popular online games like World of Warcraft. Ultimately, the collection broadens the definition of the "digital divide" in order to convey a more nuanced understanding of usage, meaning, participation, and production of digital media technology in light of racial inequality. "--

    @GreggleP @unclebobmartin https://t.co/bvMRIyBhA3

  • Distributed Blackness

    Jr. André Brock

    An explanation of the digital practices of the black Internet From BlackPlanet to #BlackGirlMagic, Distributed Blackness places blackness at the very center of internet culture. André Brock Jr. claims issues of race and ethnicity as inextricable from and formative of contemporary digital culture in the United States. Distributed Blackness analyzes a host of platforms and practices (from Black Twitter to Instagram, YouTube, and app development) to trace how digital media have reconfigured the meanings and performances of African American identity. Brock moves beyond widely circulated deficit models of respectability, bringing together discourse analysis with a close reading of technological interfaces to develop nuanced arguments about how “blackness” gets worked out in various technological domains. As Brock demonstrates, there’s nothing niche or subcultural about expressions of blackness on social media: internet use and practice now set the terms for what constitutes normative participation. Drawing on critical race theory, linguistics, rhetoric, information studies, and science and technology studies, Brock tabs between black-dominated technologies, websites, and social media to build a set of black beliefs about technology. In explaining black relationships with and alongside technology, Brock centers the unique joy and sense of community in being black online now.

    @GreggleP @unclebobmartin https://t.co/7uvDRkmaes

  • Black Software

    Charlton D. McIlwain

    "Black Software, for the first time, chronicles the long relationship between African Americans, computing technology, and the Internet. Through new archival sources and the voices of many of those who lived and made this history, this book centralizes African Americans' role in the Internet's creation and evolution, illuminating both the limits and possibilities for using digital technology to push for racial justice in the United States and across the globe"--

    @GreggleP @unclebobmartin Black Software: The Internet & Racial Justice, from the AfroNet to Black Lives Matter https://t.co/2OjdCLTnn0

  • How Buildings Learn

    Stewart Brand

    @wedgedSV See also this marvelous book by @stewartbrand It has greatly influenced my work in software architcture. https://t.co/MwYtJrtsQL

  • Describes ways to incorporate domain modeling into software development.

    I absolutely love this book. I was surprised, in my research, to find a very early use of the phrase "domain-driven design" in a paper from 2003 by Bedir Tekinerdogan and Mehmet Aksit from @utwenteEN https://t.co/tJR5WXeg7U

  • Kubernetes Patterns

    Bilgin Ibryam

    The way developers design, build, and run software has changed significantly with the evolution of microservices and containers. These modern architectures use new primitives that require a different set of practices than most developers, tech leads, and architects are accustomed to. With this focused guide, Bilgin Ibryam and Roland Huß from Red Hat provide common reusable elements, patterns, principles, and practices for designing and implementing cloud-native applications on Kubernetes. Each pattern includes a description of the problem and a proposed solution with Kubernetes specifics. Many patterns are also backed by concrete code examples. This book is ideal for developers already familiar with basic Kubernetes concepts who want to learn common cloud native patterns. You'll learn about the following pattern categories: Foundational patterns cover the core principles and practices for building container-based cloud-native applications. Behavioral patterns explore finer-grained concepts for managing various types of container and platform interactions. Structural patterns help you organize containers within a pod, the atom of the Kubernetes platform. Configuration patterns provide insight into how application configurations can be handled in Kubernetes. Advanced patterns covers more advanced topics such as extending the platform with operators.

    @mtfelisb @bibryam @ro14nd An excellent and useful book indeed

  • Based on interviews and archival research, this book explores how media is implicated in Black women’s lives in Britain. From accounts of twentieth-century activism and television representations, to experiences of YouTube and Twitter, Sobande's analysis traverses tensions between digital culture’s communal, counter-cultural and commercial qualities. Chapters 2 and 4 are available open access under a Creative Commons Attribution 4.0 International License via link.springer.com.

    I just ordered my copy. https://t.co/W2KfT3ByZV https://t.co/AY0PLT8lI1

  • In this book, Michael Feathers offers start-to-finish strategies for working more effectively with large, untested legacy code bases. This book draws on material Michael created for his own 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. This book also includes a catalog of twenty-four dependency-breaking techniques that help you work with program elements in isolation and make safer changes.

    @SartreanM https://t.co/NumiOndoyZ

  • As the digital economy changes the rules of the game for enterprises, the role of software and IT architects is also transforming. Rather than focus on technical decisions alone, architects and senior technologists need to combine organizational and technical knowledge to effect change in their company's structure and processes. To accomplish that, they need to connect the IT engine room to the penthouse, where the business strategy is defined. In this guide, author Gregor Hohpe shares real-world advice and hard-learned lessons from actual IT transformations. His anecdotes help architects, senior developers, and other IT professionals prepare for a more complex but rewarding role in the enterprise. This book is ideal for: Software architects and senior developers looking to shape the company's technology direction or assist in an organizational transformation Enterprise architects and senior technologists searching for practical advice on how to navigate technical and organizational topics CTOs and senior technical architects who are devising an IT strategy that impacts the way the organization works IT managers who want to learn what's worked and what hasn't in large-scale transformation

    I really like Gregor's book @@ghohpe https://t.co/BJOh0624C9

  • How Buildings Learn

    Stewart Brand

    See also How Buildings Learn by @stewartbrand (a book that has greatly influenced influenced my thinking). https://t.co/MwYtJrtsQL https://t.co/5cYmdTOGVQ

  • Sketch Plan Build

    Alejandro Bahamon

    Often the most sophisticated buildings get their start as quick sketches in a moment of sudden inspiration. During the long process of careful refinement, these same sketches take shape and emerge as the buildings we see before us everyday. Focusing on the design process of today's most noteworthy architects, Sketch Plan Build explores the reasoning, resources, and influences behind the projects of today's most recognized architects. This book is a primary tool for under-standing the different traits and nuances each architect uses to express their own ideas. With international projects from world renowned architects such as Tadao Ando, Coop Himmel(b)lau, and Renzo Piano, and with detailed sketches, drawings, and photographs for each project, Sketch Plan Build is sure to provide a comprehensive compendium for all those interested in how an inspired idea makes the journey from projection to construction. This book brings together the drawings, sketches, and finished photographs of more than thirty prestigious international architects. With its 500 fully-illustrated pages, Sketch Plan Build is a diverse graphic tour that starts with the sketch, extends to drawings, and concludes with finished photographs -- providing the reader with a profound insight into the design process of today’s most respected architects.

    @aansari86 See Sketch Plan Build: World Class Architects Show How It's Done https://t.co/oLegn0oaC0

  • Learn and understand the need to architect cloud applications and migrate your business to cloud efficiently Key Features Understand the core design elements required to build scalable systems Plan resources and technology stacks effectively for high security and fault tolerance Explore core architectural principles using real-world examples Book Description Cloud computing has proven to be the most revolutionary IT development since virtualization. Cloud native architectures give you the benefit of more flexibility over legacy systems. To harness this, businesses need to refresh their development models and architectures when they find they don't port to the cloud. Cloud Native Architectures demonstrates three essential components of deploying modern cloud native architectures: organizational transformation, deployment modernization, and cloud native architecture patterns. This book starts with a quick introduction to cloud native architectures that are used as a base to define and explain what cloud native architecture is and is not. You will learn what a cloud adoption framework looks like and develop cloud native architectures using microservices and serverless computing as design principles. You'll then explore the major pillars of cloud native design including scalability, cost optimization, security, and ways to achieve operational excellence. In the concluding chapters, you will also learn about various public cloud architectures ranging from AWS and Azure to the Google Cloud Platform. By the end of this book, you will have learned the techniques to adopt cloud native architectures that meet your business requirements. You will also understand the future trends and expectations of cloud providers. What you will learn Learn the difference between cloud native and traditional architecture Explore the aspects of migration, when and why to use it Identify the elements to consider when selecting a technology for your architecture Automate security controls and configuration management Use infrastructure as code and CICD pipelines to run environments in a sustainable manner Understand the management and monitoring capabilities for AWS cloud native application architectures Who this book is for Cloud Native Architectures is for software architects who are keen on designing resilient, scalable, and highly available applications that are native to the cloud.

    Tonight's reading material: Cloud Native Architectures by @migrating2cloud https://t.co/ND9T449wBX https://t.co/Xn2E2ww1rB

  • Enterprise Architecture is the discipline of managing the complexities of the Business-IT landscape. It has been around since the 1980's, when for the first time computers were connected in networks, and the already serious (and unsolved) problem of the complexity of computer programs for relatively simple business needs turned into the huge problem of large networks of them in complex business landscapes. In spite of many 'best practices' and 'frameworks' that have been introduced, Enterprise Architecture is not a great success. After thirty years, we still have the same problems. Chaos is still everywhere. Projects still fail far too often. In this book, (hidden) assumptions behind the existing approaches to enterprise architecture are challenged, and a more realistic perspective that helps us battle the complexities and unpredictabilities of today's Business-IT landscapes is described. Practical suggestions about enterprise architecture governance and products, based on real-world experience with the described approach, complete the book. From general management to IT professionals, everyone who is confronted with the problem of managing Business-IT landscapes can profit from the insights this book offers. No specialist prior knowledge is required. Gerben Wierda is author of Mastering ArchiMate, and was, amongst other things, Lead Architect of the Judiciary in The Netherlands, Lead Architect of APG Asset Management, and is now Team Coordinator Architecture & Design at APG. He holds an M.Sc in Physics from the University of Groningen and an MBA from RSM Erasmus, Rotterdam.

    A charming book I'm reading ATM, fully of battle-tested wisdom. https://t.co/VaARYcSWL4 https://t.co/n8Nlu0KGkm

  • How do you detangle a monolithic system and migrate it to a microservices architecture? How do you do it while maintaining business-as-usual? As a companion to Sam Newman's extremely popular Building Microservices, this new book details a proven method for transitioning an existing monolithic system to a microservice architecture. With many illustrative examples, insightful migration patterns, and a bevy of practical advice to transition your monolith enterprise into a microservice operation, this practical guide covers multiple scenarios and strategies for a successful migration, from initial planning all the way through application and database decomposition. You'll learn several tried and tested patterns and techniques that you can use as you migrate your existing architecture. Ideal for organizations looking to transition to microservices, rather than rebuild Helps companies determine whether to migrate, when to migrate, and where to begin Addresses communication, integration, and the migration of legacy systems Discusses multiple migration patterns and where they apply Provides database migration examples, along with synchronization strategies Explores application decomposition, including several architectural refactoring patterns Delves into details of database decomposition, including the impact of breaking referential and transactional integrity, new failure modes, and more

    @jasonthurow1 It's an excellent book

  • "People sometimes ask me what they should read to find out about artificial intelligence. Herbert Simon's book The Sciences of the Artificial is always on the list I give them. Every page issues a challenge to conventional thinking, and the layman who digests it well will certainly understand what the field of artificial intelligence hopes to accomplish. I recommend it in the same spirit that I recommend Freud to people who ask about psychoanalysis, or Piaget to those who ask about child psychology: If you want to learn about a subject, start by reading its founding fathers." -- George A. Miller, "Complex Information Processing" Continuing his exploration of the organization of complexity and the science of design, this new edition of Herbert Simon's classic work on artificial intelligence adds a chapter that sorts out the current themes and tools -- chaos, adaptive systems, genetic algorithms -- for analyzing complexity and complex systems.

    @ejjcatx It has been a major influence on my thinking (I referenced heavily in my 00AD book).

  • In 1944, Britain led the world in electronic computing. By 1974, the British computer industry was all but extinct. Marie Hicks's Programmed inequality explores the story of labor feminization and gendered technocracy that undercut British efforts to computerize. Women were a hidden engine of growth in high technology from World War II to the 1960s. As computing experienced a gender flip, becoming male-identified in the 1960s and 1970s, labor problems grew into structural ones, and gender discrimination caused the nation's largest computer user - the civil service and sprawling public sector -- to make decisions that were disastrous for the British computer industry and the nation as a whole. Programmed inequality shows how the disappearance of women from the field has grave macroeconomic consequences for Britain, and why the United States risks repeating those errors in the twenty-first century.

    @antirez Anyway, thank you for the backstory. I would observe that your POV expressed therein is as naive today as it was then, for it ignores the pervasive, systemic sexism that persists within the industry. Take a look at Mar Hicks’s book “Programmed Inequality” for more.

  • How Buildings Learn

    Stewart Brand

    The architecture of all lasting systems evolve. See https://t.co/PoKoNxqdxt https://t.co/djZs1wnhrq

  • How do you detangle a monolithic system and migrate it to a microservices architecture? How do you do it while maintaining business-as-usual? As a companion to Sam Newman's extremely popular Building Microservices, this new book details a proven method for transitioning an existing monolithic system to a microservice architecture. With many illustrative examples, insightful migration patterns, and a bevy of practical advice to transition your monolith enterprise into a microservice operation, this practical guide covers multiple scenarios and strategies for a successful migration, from initial planning all the way through application and database decomposition. You'll learn several tried and tested patterns and techniques that you can use as you migrate your existing architecture. Ideal for organizations looking to transition to microservices, rather than rebuild Helps companies determine whether to migrate, when to migrate, and where to begin Addresses communication, integration, and the migration of legacy systems Discusses multiple migration patterns and where they apply Provides database migration examples, along with synchronization strategies Explores application decomposition, including several architectural refactoring patterns Delves into details of database decomposition, including the impact of breaking referential and transactional integrity, new failure modes, and more

    @SuMastodon @simonbrown https://t.co/yUhm0qN8Qa

  • Ethics Across Cultures

    Michael Brannigan

    This new text/reader for Introduction to Ethics courses explores the rich ethical traditions of the West and the East.

    @danilom_ @Facebook See this, for one example. There are indeed core ethics common to many cultures: https://t.co/uM9RraT2Ma

  • Introduction: Britain's computer "revolution"--War machines : women's computing work and the underpinnings of the data-driven state 1930-1946 -- Peacetime data processing : institutionalizing a feminized machine underclass 1946-1954 -- Luck and labor shortage : gender, professionalization, and opportunities for computer workers -- 1958-1969 -- The rise of the technocrat : how state attempts to centralize power through computing went -- Astray 1967-1971 -- The end of white heat and the failure of British technocracy, 1970-1979 -- Conclusion: re-assembling the history of computing to show gender's formative role -- Bibliography

    Hey @PapricusMaximus, I see that you deleted your tweet directed toward me (but us old guys know the Internet Never Forgets). In the spirit of being constructive - and since you label yourself as a hobbyist historian - I suggest you read this book: https://t.co/7FWZnNWPuf

  • @JeffDean @susanthesquark I would also like to recommend this one. https://t.co/6x0DDndhhB https://t.co/gyT3H9C8aZ

  • @susanthesquark We've enjoyed https://t.co/8VfqvlVa8X https://t.co/IkIlzGVPpT

  • This book introduces the concept of software architecture as one of the cornerstones of software in modern cars. Following a historical overview of the evolution of software in modern cars and a discussion of the main challenges driving that evolution, Chapter 2 describes the main architectural styles of automotive software and their use in cars’ software. In Chapter 3, readers will find a description of the software development processes used to develop software on the car manufacturers’ side. Chapter 4 then introduces AUTOSAR – an important standard in automotive software. Chapter 5 goes beyond simple architecture and describes the detailed design process for automotive software using Simulink, helping readers to understand how detailed design links to high-level design. Next, Chapter 6 presents a method for assessing the quality of the architecture – ATAM (Architecture Trade-off Analysis Method) – and provides a sample assessment, while Chapter 7 presents an alternative way of assessing the architecture, namely by using quantitative measures and indicators. Subsequently Chapter 8 dives deeper into one of the specific properties discussed in Chapter 6 – safety – and details an important standard in that area, the ISO/IEC 26262 norm. Lastly, Chapter 9 presents a set of future trends that are currently emerging and have the potential to shape automotive software engineering in the coming years. This book explores the concept of software architecture for modern cars and is intended for both beginning and advanced software designers. It mainly aims at two different groups of audience – professionals working with automotive software who need to understand concepts related to automotive architectures, and students of software engineering or related fields who need to understand the specifics of automotive software to be able to construct cars or their components. Accordingly, the book also contains a wealth of real-world examples illustrating the concepts discussed and requires no prior background in the automotive domain.

    @mrjreid @MiroslawStaron @w3c Miroslaw, I really enjoyed your book!

  • Embodied cognition is a recent development in psychology that practitioners often present as a superseding standard cognitive science. In this outstanding introduction, Lawrence Shapiro sets out the central themes and debates surrounding embodied cognition, explaining and assessing the work of many of the key figures in the field, including Lawrence Barsalou, Daniel Casasanto, Andy Clark, Alva Noë, and Michael Spivey. Beginning with an outline of the theoretical and methodological commitments of standard cognitive science, Shapiro then examines philosophical and empirical arguments surrounding the traditional perspective, setting the stage for a detailed examination of the embodied alternative. He introduces topics such as dynamical systems theory, ecological psychology, robotics, and connectionism, before addressing core issues in philosophy of mind such as mental representation and extended cognition. This second edition has been updated and revised throughout and includes new chapters that both expand on earlier topics and that introduce new material on embodied concepts, preference formation, and emotion. Including helpful chapter summaries and annotated further reading at the end of each chapter, Embodied Cognition, Second Editionis essential reading for all students of philosophy of mind, psychology, and cognitive science. ition has been updated and revised throughout and includes new chapters that both expand on earlier topics and that introduce new material on embodied concepts, preference formation, and emotion. Including helpful chapter summaries and annotated further reading at the end of each chapter, Embodied Cognition, Second Editionis essential reading for all students of philosophy of mind, psychology, and cognitive science.

    @Abebab (I just started reading https://t.co/xQmbFr3dLH)

  • Beschrijving van vijfentwintig open source applicaties.

    This is a two-volume series that I keep coming back to; it's full of marvelous information. https://t.co/FLxTsFE4GT https://t.co/S9Un0q8Zcf

  • Today’s reading material. https://t.co/nI3uVMlKrZ

  • @ruthmalan (See my collection of system engineering books. And books from the domain of civil architecture).

  • In this truly unique technical book, today's leading software architects present valuable principles on key development issues that go way beyond technology. More than four dozen architects -- including Neal Ford, Michael Nygard, and Bill de hOra -- offer advice for communicating with stakeholders, eliminating complexity, empowering developers, and many more practical lessons they've learned from years of experience. Among the 97 principles in this book, you'll find useful advice such as: Don't Put Your Resume Ahead of the Requirements (Nitin Borwankar) Chances Are, Your Biggest Problem Isn't Technical (Mark Ramm) Communication Is King; Clarity and Leadership, Its Humble Servants (Mark Richards) Simplicity Before Generality, Use Before Reuse (Kevlin Henney) For the End User, the Interface Is the System (Vinayak Hegde) It's Never Too Early to Think About Performance (Rebecca Parsons) To be successful as a software architect, you need to master both business and technology. This book tells you what top software architects think is important and how they approach a project. If you want to enhance your career, 97 Things Every Software Architect Should Know is essential reading.

    @ruthmalan (See my collection of system engineering books. And books from the domain of civil architecture).

  • Agile Software Architecture

    Muhammad Ali Babar

    Agile software development approaches have had significant impact on industrial software development practices. Today, agile software development has penetrated to most IT companies across the globe, with an intention to increase quality, productivity, and profitability. Comprehensive knowledge is needed to understand the architectural challenges involved in adopting and using agile approaches and industrial practices to deal with the development of large, architecturally challenging systems in an agile way. Agile Software Architecture focuses on gaps in the requirements of applying architecture-centric approaches and principles of agile software development and demystifies the agile architecture paradox. Readers will learn how agile and architectural cultures can co-exist and support each other according to the context. Moreover, this book will also provide useful leads for future research in architecture and agile to bridge such gaps by developing appropriate approaches that incorporate architecturally sound practices in agile methods. Presents a consolidated view of the state-of-art and state-of-practice as well as the newest research findings Identifies gaps in the requirements of applying architecture-centric approaches and principles of agile software development and demystifies the agile architecture paradox Explains whether or not and how agile and architectural cultures can co-exist and support each other depending upon the context Provides useful leads for future research in both architecture and agile to bridge such gaps by developing appropriate approaches, which incorporate architecturally sound practices in agile methods

    @ruthmalan (See my collection of system engineering books. And books from the domain of civil architecture).

  • This book provides a detailed “how-to” guide, addressing aspects ranging from analysis and design to the implementation of applications, which need to be integrated within legacy applications and databases. The analysis and design of the next generation of software architectures must address the new requirements to accommodate the Internet of things (IoT), cybersecurity, blockchain networks, cloud, and quantum computer technologies. As 5G wireless increasingly establishes itself over the next few years, moving legacy applications into these new architectures will be critical for companies to compete in a consumer-driven and social media-based economy. Few organizations, however, understand the challenges and complexities of moving from a central database legacy architecture to a ledger and networked environment. The challenge is not limited to just designing new software applications. Indeed, the next generation needs to function more independently on various devices, and on more diverse and wireless-centric networks. Furthermore, databases must be broken down into linked list-based blockchain architectures, which will involve analytic decisions regarding which portions of data and metadata will be processed within the chain, and which ones will be dependent on cloud systems. Finally, the collection of all data throughout these vast networks will need to be aggregated and used for predictive analysis across a variety of competitive business applications in a secured environment. Certainly not an easy task for any analyst/designer! Many organizations will continue to use packaged products and open-source applications. These third-party products will need to be integrated into the new architecture paradigms and have seamless data aggregation capabilities, while maintaining the necessary cyber compliances. The book also clearly defines the roles and responsibilities of the stakeholders involved, including the IT departments, users, executive sponsors, and third-party vendors. The book’s structure also provides a step-by-step method to help ensure a higher rate of success in the context of re-engineering existing applications and databases, as well as selecting third-party products, conversion methods and cybercontrols. It was written for use by a broad audience, including IT developers, software engineers, application vendors, business line managers, and executives.

    @ruthmalan (See my collection of system engineering books. And books from the domain of civil architecture).

  • Application Architecture

    Laurence J. Best

    Large-scale software engineering applications have structures and functions in common. Identifies those structures and shows how to design a standard application model into which the structures unique to the system in question can be plugged. Construction of such standard models results in simpler and more reliable designs. Material covers architecture of application functions, application support from the programmer's and user's points of view, processing and on-line module design, and emerging trends.

    @ruthmalan (See my collection of system engineering books. And books from the domain of civil architecture).

  • @ruthmalan (See my collection of system engineering books. And books from the domain of civil architecture).

  • PrefaceTo understand anything, you should not try to understand everything. — Aristotle The whole is greater than the sum of the parts; the part is greater than a fraction of the whole. — Aristotle Architecting is a challenging process of abstraction, composition, modularity, and simplification to create an architecture specification. An architecture specification captures the essence and definition of the system: understanding, parts, and the relationships among the parts. An architecture specification defines how a system solves a business problem within the scope of the business. — Putman Leave the beaten track occasionally and dive into the woods. You will be certain to find something that you have never seen before. — Alexander Graham Bell There are large gaps in the theory and practice of software architecture and engineering. Much is published about the representation of a software architecture, such as the Unified Modeling Language (UML), but little is available about the specification for a software architecture. Software engineering methods of domain engineering, process modeling languages, and well-formed patterns of reasoning aid in the specification of an architecture. The Reference Model of Open Distributed Processing (RM-ODP) defines the standard reference model for distributed software systems architectures, based on object-oriented techniques, accepted at the international level. RM-ODP is a standard adopted by the International Standards Organization (ISO) and the International Telecommunications Union (ITU). RM-ODP is embedded and used actively in mission-critical systems industries such as in telecommunications, in health care, on Wall Street (financial services industry), in various Government systems (Logistics), in European Government Agencies such as UK Aviation control systems, as a foundation for the Object Management Group (OMG) Object Management Architecture (OMA), for defining enterprise architectures, and for defining software architectures. The software systems architecture work that is emerging, and is focused either at the component level or at the systems level, provides a key resource for architecting. This is enhanced by the architecting techniques of RM-ODP. This book assembles these great ideas, explains what they mean, and shows how to use them for practical benefit, along with real-world case study examples. By using the RM-ODP specification constructs, associated languages, architecture patterns of reasoning, semantic behavior specification, and conformance testing abilities, readers will be able to architect their specific systems based on the RM-ODP specification foundations, and specify architectures that work. One of the purposes of this book is to provide the approach to using the RM-ODP foundations in architecting and specifying a distributed processing system that addresses such key properties as interoperability, dependability, portability, integration, composability, scalability, transparency, behavior specification, quality of service, policy management, federation, and conformance validation. Another purpose of this book is to explain the underlying foundations for creating an architectural specification. These foundations come not only from RM-ODP, but also from the current work in software systems architecture. Another purpose is to guide the reader to understand the importance and benefits of creating an architecture specification for an enterprise. Yet another purpose is to provide the reader with the principles to construct software systems architecture (at both introductory and in-depth levels). By applying the proven techniques of RM-ODP for what makes a good architecture, readers will be able to build their own tailored architectures, and clearly represent them in UML or some other tool, with an understanding of the underlying principles. Practitioners of RM-ODP have found that the standard is extremely beneficial in guiding architecture definition and providing standard terminology/principles for distributed object applications and infrastructures from an enterprise perspective. Outstanding Features This book is intended to provide valuable insight into successful architecture specification by describing an unprecedented foundation to accomplish this task, describing the use of the foundation, explaining the relationships of the concepts of architecting, explaining the relationships of the concepts of distributed processing, and identifying the right methods and possible tools for architecting. All material for the book has been derived from actual experiences. A medical case study is used throughout the book in ever increasing detailed specification. This medical case study is based on actual experience of the author. In addition, many metamodels are provided to represent the concepts of RM-ODP. All of these metamodels are contributions from the author. This is information that readers can use and apply in their architecting today. RM-ODP provides a reference framework, grammars, methods of abstraction and composition, and separation of concerns to achieve an architecture specification of the system. RM-ODP provides a framework for this separation, using viewpoints, as well as separating out certain decisions (e.g., product decisions) until later. Further, the reference model provides a set of definitions, which always aids in communicating with others. There is little in the literature about RM-ODP or architecture specification, and certainly not a book dedicated as a tutorial of these subjects. Now there is. In summary, this book offers the following: How to manage the architecting process in the lifecycle of a system How to solve many architecture reuse and cost-effectiveness problems How to create a business specification How to understand and use the concepts of distributed processing in an architecture How to architect effectively How to specify an architecture How to understand and specify semantic behavior and nonfunctional properties of a system (the "ilities") How to provide the right level of detail in an architecture specification How to ensure the implementation conforms to the architecture specification How to use RM-ODP effectively How to use popular tools, such as UML, to describe an architecture A definitive tutorial of RM-ODP Audience This book is designed for: Those in the Distributed Software Systems Architecture community who are interested in a methodology for using proven architecture principles. Professional software architects who are looking for new ideas about architecting a system. Within this book, the reader will find discussions of the techniques for architecting, for creating an architecture specification, and RM-ODP's relationship to other architecture frameworks. Program managers interested in how to create a cost-effective architecture within their enterprise that focuses on the needs of the enterprise and solves an enterprise problem. They will learn how do to do this through an overview of RM-ODP, the program benefits for using it, and where RM-ODP fits in the system lifecycle process. Systems engineers interested in the lifecycle approach to enterprise architecture specification. Experienced engineers interested in expanding their understanding of how to create a valid architecture specification and gain an understanding of the distributed processing system concepts, why certain constructions are valid and why some are not, what is to be specified and how, and some new ideas and approaches to architecting a system. The reader will be able to develop a collection of useful distributed processing architecting techniques that expand upon the current software systems architecture capabilities. Developers interested in the practice of architecture specification and aligning current technology to achieve a workable system, while allowing evolutionary changes in technology solutions. Researchers interested in solutions and aids for furthering the research work in architecture specification. Individuals in the software community who are generally interested in the application of an architecture method. Readers will find examples of the applications of RM-ODP and specific analysis techniques. The expected audience will be novice and mid-level program managers, software engineers, those in the IEEE, DoD, research communities, consortia, and general architecture readers. This book can be used as a textbook and reference book for studies in the methods of architecture; for graduate studies in software architecture specification; for training information about software architecture and RM-ODP; for further education of consultants, integration specialists, and acquisition managers who need to approve and fund such work; and for researchers who are expanding the discipline of software architecture. The inclusion of RM-ODP will bring to the U.S., principally, the outstanding work that was accomplished by the international standards working group. In brief, the RM-ODP principles form a solution set and foundation for all software architecting endeavors. It is the formalized framework for this topic, and at the International Standard (IS) level of acceptance. It forms a solution set and foundation for reuse of design patterns to provide cost-effective software architecture. It is the process for this topic, but has never before been described in a book. Many program managers (who typically set the stage as to the methodology of choice for a project), software engineers, and researchers in academia and in DARPA are unaware of the power and solutions provided by the standard, or the process of identifying and instantiating reuse of all the expensive assets of architecture. Many do not realize that there is a language for specifying software-intensive distributed processing, and that language is precisely and rigorously defined in RM-ODP for reuse. Those debating definitions for architecture, system, interface, and others can reuse the internationally agreed upon definitions. Finally, with the inclusion of RM-ODP and its relationship to other architecture frameworks, it is expected that many software engineers will benefit from reading this work, since it will be the first time these subjects are discussed in print. How to Use This Book This book is divided into four parts, aimed at increasing levels of detail. Part One provides an overview of the field of software architecture, an RM-ODP primer for managers, and an RM-ODP primer for architects. Part Two provides an in-depth study of RM-ODP and how to use it. Areas of importance and utility from RM-ODP are highlighted. Ambiguity in RM-ODP is highlighted. Warnings in the use of RM-ODP are highlighted. Part Three provides a discussion of the principal architecture patterns of use, arranged by topic. Several of these patterns of use come from emerging work under the initiative of RM-ODP, as well as lessons learned from the practice of RM-ODP. These patterns of reasoning used by the architect are founded on the principals of RM-ODP, as discussed in Part Two of the book. Part Four concludes with relating RM-ODP to other architecture methods. It also provides emerging technologies to further the patterns of reasoning for use in architecting, and a set of architecting heuristics. The information contained in this book is organized in a manner that provides clear insight into the world of distributed software-intensive processing architecture for designers and developers who are familiar with information systems technology, but want to know more about how to build a good architecture. Starting with a tutorial about software architecture, and then a tutorial about the standard for software architecture, the reader need not be an expert in the area of international standards, RM-ODP, software architecture, or specific technologies. The book goes on to address the needs of the variety of readers for which it is intended. Each chapter in the book provides an overview of the subject of the chapter, as well as a summary. For those who wish a broad brush exposure to RM-ODP, the primers of Part One provide this, as well as the overviews and summaries in each chapter of interest. As each chapter progresses, in Parts Two and Three, more and more in-depth detail is provided. The readings of these chapters are aimed at those who wish to know the technical details of a topic. There are two case studies used throughout the book, at various levels of detail. The primary case study is a Hospital enterprise, based upon the author's experience with the medical profession. A secondary case study is an airline reservation system, also based upon the author's experience. These case studies are used to describe the concepts of RM-ODP, and to show how they might be used.

    @ruthmalan (See my collection of system engineering books. And books from the domain of civil architecture).

  • Beschrijving van vijfentwintig open source applicaties.

    @ruthmalan (See my collection of system engineering books. And books from the domain of civil architecture).

  • Robert M. Grant combines a highly accessible writing style with a concentration on the fundamentals of value creation and an emphasis on practicality in this leading strategy text. In this new edition, he includes an even greater focus on strategy implementation that reflects the needs of firms to reconcile scale economies with entrepreneurial flexibility, innovation with cost efficiency, and globalization with local responsiveness. This edition also incorporates some of the key strategic issues of today including: post-financial crisis adjustment, the continuing rise of China, India and Brazil, and the increased emphasis on ethics and sustainability. Coverage is also provided on strategy in not-for-profit organizations. Contemporary Strategy Analysis, Text and Cases 8th Edition combines the text with an updated collection of 20 case studies. It is suitable for both MBA and advanced undergraduate students. Additional teaching resources are also available for instructors, including an instructor?s manual, case teaching notes, test bank, teaching slides, case video clips and extra cases. All of these resources can be accessed via the companion website: www.contemporarystrategyanalysis.com

    @ruthmalan (See my collection of system engineering books. And books from the domain of civil architecture).

  • This book introduces the concept of software architecture as one of the cornerstones of software in modern cars. Following a historical overview of the evolution of software in modern cars and a discussion of the main challenges driving that evolution, Chapter 2 describes the main architectural styles of automotive software and their use in cars’ software. In Chapter 3, readers will find a description of the software development processes used to develop software on the car manufacturers’ side. Chapter 4 then introduces AUTOSAR – an important standard in automotive software. Chapter 5 goes beyond simple architecture and describes the detailed design process for automotive software using Simulink, helping readers to understand how detailed design links to high-level design. Next, Chapter 6 presents a method for assessing the quality of the architecture – ATAM (Architecture Trade-off Analysis Method) – and provides a sample assessment, while Chapter 7 presents an alternative way of assessing the architecture, namely by using quantitative measures and indicators. Subsequently Chapter 8 dives deeper into one of the specific properties discussed in Chapter 6 – safety – and details an important standard in that area, the ISO/IEC 26262 norm. Lastly, Chapter 9 presents a set of future trends that are currently emerging and have the potential to shape automotive software engineering in the coming years. This book explores the concept of software architecture for modern cars and is intended for both beginning and advanced software designers. It mainly aims at two different groups of audience – professionals working with automotive software who need to understand concepts related to automotive architectures, and students of software engineering or related fields who need to understand the specifics of automotive software to be able to construct cars or their components. Accordingly, the book also contains a wealth of real-world examples illustrating the concepts discussed and requires no prior background in the automotive domain.

    @ruthmalan (See my collection of system engineering books. And books from the domain of civil architecture).

  • Beautiful Architecture

    Diomidis Spinellis

    What are the ingredients of robust, elegant, flexible, and maintainable software architecture? Beautiful Architecture answers this question through a collection of intriguing essays from more than a dozen of today's leading software designers and architects. In each essay, contributors present a notable software architecture, and analyze what makes it innovative and ideal for its purpose. Some of the engineers in this book reveal how they developed a specific project, including decisions they faced and tradeoffs they made. Others take a step back to investigate how certain architectural aspects have influenced computing as a whole. With this book, you'll discover: How Facebook's architecture is the basis for a data-centric application ecosystem The effect of Xen's well-designed architecture on the way operating systems evolve How community processes within the KDE project help software architectures evolve from rough sketches to beautiful systems How creeping featurism has helped GNU Emacs gain unanticipated functionality The magic behind the Jikes RVM self-optimizable, self-hosting runtime Design choices and building blocks that made Tandem the choice platform in high-availability environments for over two decades Differences and similarities between object-oriented and functional architectural views How architectures can affect the software's evolution and the developers' engagement Go behind the scenes to learn what it takes to design elegant software architecture, and how it can shape the way you approach your own projects, with Beautiful Architecture.

    @ruthmalan (See my collection of system engineering books. And books from the domain of civil architecture).

  • Great software architects aren't born. They are a product of decades of building real-life solutions and relentless learning. They become really good at their trade closer to the retirement age. But most startups are fostered by young entrepreneurs who dare to try but lack the experience. They also lack the $$ to hire a silver-haired architect to join their team from day one. Left to their own faculties, the entrepreneurs and their engineering teams quickly get on the path of learning from their own mistakes. Eventually, they discover this is the most expensive way of learning. Over time they get better, and some become the true masters of the craft - but way too late to make a difference for their early-day projects.This book is meant to break the vicious circle. It isn't a textbook, at least not in the traditional sense. It is a business-centric practical guide to software architecture, intended for software engineers, technology executives, students of computer science, and tech-savvy entrepreneurs who want to de-risk their entrepreneurial endeavors or to fast-track their careers in software engineering. The recipes in this book are highly practical, battle-tested, and current for building mid- to large-scale systems in 2019.

    @ruthmalan (See my collection of system engineering books. And books from the domain of civil architecture).

  • This text aims to help all members of the development team make the correct nuts-and-bolts architecture decisions that ensure project success.

    @ruthmalan (See my collection of system engineering books. And books from the domain of civil architecture).

  • "The software development ecosystem is constantly changing, providing a constant stream of new tools, frameworks, techniques, and paradigms. Over the past few years, incremental developments in core engineering practices for software development have created the foundations for rethinking how architecture changes over time, along with ways to protect important architectural characteristics as it evolves. This practical guide ties those parts together with a new way to think about architecture and time."--Amazon.com.

    @ruthmalan (See my collection of system engineering books. And books from the domain of civil architecture).

  • There is a growing gap between the theory and the practice of component-based software design. The theory largely assumes that the design task is to develop specifications for software components; in reality, however, most component-based design relies on preexisting components, which have preexisting specifications. With more and more software being developed from commercially available components, it is increasingly critical to recognize the novel challenges and unfamiliar constraints inherent in such design. Describing a number of proven techniques, this book provides much-needed guidance on how to build component-based systems in a real working environment. "Building Systems from Commercial Components" is divided into three parts: Part I identifies the design challenges posed by commercial components, presents specific engineering techniques that meet those challenges, and describes workflows for incorporating those techniques into an existing development process. Part II features an extended case study of a project from the authors' own experience, with each chapter illustrating the challenges posed by commercial components and the techniques used to meet those challenges. Part III provides advice on how to get started using the techniques described in the book, and makes some predictions about the future course of component-based development. This book is intended for anyone who practices, or wishes to practice, component-based software development. System architects, chief engineers, project managers, chief technology officers, and front-line software engineers and programmers will each find here something of immediate value. The authors, through their work at the Software Engineering Institute, are able to share a broad and practical understanding of both the problems you will face and the solutions you will require as you design component-based systems. 0201700646B06072001

    @ruthmalan (See my collection of system engineering books. And books from the domain of civil architecture).

  • Enterprise Architecture is the discipline of managing the complexities of the Business-IT landscape. It has been around since the 1980's, when for the first time computers were connected in networks, and the already serious (and unsolved) problem of the complexity of computer programs for relatively simple business needs turned into the huge problem of large networks of them in complex business landscapes. In spite of many 'best practices' and 'frameworks' that have been introduced, Enterprise Architecture is not a great success. After thirty years, we still have the same problems. Chaos is still everywhere. Projects still fail far too often. In this book, (hidden) assumptions behind the existing approaches to enterprise architecture are challenged, and a more realistic perspective that helps us battle the complexities and unpredictabilities of today's Business-IT landscapes is described. Practical suggestions about enterprise architecture governance and products, based on real-world experience with the described approach, complete the book. From general management to IT professionals, everyone who is confronted with the problem of managing Business-IT landscapes can profit from the insights this book offers. No specialist prior knowledge is required. Gerben Wierda is author of Mastering ArchiMate, and was, amongst other things, Lead Architect of the Judiciary in The Netherlands, Lead Architect of APG Asset Management, and is now Team Coordinator Architecture & Design at APG. He holds an M.Sc in Physics from the University of Groningen and an MBA from RSM Erasmus, Rotterdam.

    @ruthmalan (See my collection of system engineering books. And books from the domain of civil architecture).

  • Penetrating analysis of the functions and organization of city neighborhoods, the forces of deterioration and regeneration, and the necessary planning innovations

    @BridgerPutnam @simonbrown @hogaur Remarkable book

  • Dr Tainter describes nearly two dozen cases of collapse and reviews more than 2000 years of explanations. He then develops a new and far-reaching theory.

    @tctjr Ohhh...yes, love that book by Tainter.

  • A study of architecture examines how we both shape and are shaped by our private homes and public edifices and explains how our stylistic choices can be used to increase our chances of happiness.

    In the eyes of medieval man, a cathedral was God's house on earth....Islamic architects wrote their religion literally as well as symbolically onto their building. -- The Architecture of Happiness https://t.co/RjAS6GotyB

  • This book be dedicated to Kanye West, because he'll never fucking read it. -- Joan Rivers in "Diary of a Mad Diva"

  • The Lost Universe

    Gene Weltfish

    "A fascinating insight into the life and culture of the Pawnee people is achieved here by the author's presentation of carefully gathered information in the form of a narrative of one year in Pawnee village. The first few chapters lay the groundwork of kinship lines, followed by a narration of the life of one person in the village. Customs, ceremonies, beliefs, and hard work become apparent as the author leads one through the intricacies of the activities. Although it presents a great deal of detailed anthropological material, the manner of presentation turns the book into a readable account. . . . The book is based on years of first-hand study as well as scholarly research and is recom-mended as an in-depth study of Plains Indian life."—Reprint Bulletin-Book Reviews Gene Weltfish is coauthor, with Ruth Benedict, of The Races of Mankind. She is also the author of The Origins of Art and other books.

    @brettachapman @professorkim Signal boost: The Lost Universe: Pawnee Life and Culture https://t.co/cuWESYZy0a

  • Fractals are characterized by the repetition of similar patterns at ever-diminishing scales. Fractal geometry has emerged as one of the most exciting frontiers on the border between mathematics and information technology and can be seen in many of the swirling patterns produced by computer graphics. It has become a new tool for modeling in biology, geology, and other natural sciences. Anthropologists have observed that the patterns produced in different cultures can be characterized by specific design themes. In Europe and America, we often see cities laid out in a grid pattern of straight streets and right-angle corners. In contrast, traditional African settlements tend to use fractal structures-circles of circles of circular dwellings, rectangular walls enclosing ever-smaller rectangles, and streets in which broad avenues branch down to tiny footpaths with striking geometric repetition. These indigenous fractals are not limited to architecture; their recursive patterns echo throughout many disparate African designs and knowledge systems. Drawing on interviews with African designers, artists, and scientists, Ron Eglash investigates fractals in African architecture, traditional hairstyling, textiles, sculpture, painting, carving, metalwork, religion, games, practical craft, quantitative techniques, and symbolic systems. He also examines the political and social implications of the existence of African fractal geometry. His book makes a unique contribution to the study of mathematics, African culture, anthropology, and computer simulations.

    @ruthmalan And this, too :-) https://t.co/VofaGVA5ev

  • Two Years Before The Mast

    Richard Henry Dana

    Current reading. https://t.co/UWOlfsAmFM

  • Object-Orientated Analysis and Design with Applications is the essential reference to object-orientated technology - a technology that has evolved and become the de-facto paradigm in mainstream software development. With this highly anticipated third edition, readers can learn to apply onject-orientated methods using the Unified Modelling Language (UML) 2.0. The authors draw upon their rich and varied experience to offer improved methods for object development that tackle the complex problems faced by system and software developers. Apart from the chapter headings, readers will find pragmatic advice on a host of important issues including classification, implementation strategies, and cost-effective project management.

    @paultgoings @nitin https://t.co/cWd09cGuLK

  • @cosmicvisitors One place to start is the book "Worlds Hidden in Plain Sight"

  • See https://t.co/MHEF2rETkJ and https://t.co/kFyLQo2Fpa

  • Two Years Before the Mast

    Richard Henry Dana

    @SFMagus (The very reason i chose his book.)

  • They’re back! This eagerly awaited four-volume slipcased paperback edition of the original groundbreaking collection features the adventures of Calvin and his pet tiger, Hobbes. New York Times best-seller! Watterson's imaginative approach to his material and his inventive graphics have made Calvin and Hobbes one of the few universally admired by other cartoonists." --Charles Solomon, Los Angeles Times Book Review Calvin and Hobbes is unquestionably one of the most popular comic strips of all time. The imaginative world of a boy and his real-only-to-him tiger was first syndicated in 1985 and appeared in more than 2,400 newspapers when Bill Watterson retired on January 1, 1996. The entire body of Calvin and Hobbes cartoons published in a truly noteworthy tribute to this singular cartoon in The Complete Calvin and Hobbes. Composed of three hardcover, four-color volumes in a sturdy slipcase, this edition includes all Calvin and Hobbes cartoons that ever appeared in syndication. This is the treasure that all Calvin and Hobbes fans seek.

    This is my go-to crisis comfort book @Calvinn_Hobbes https://t.co/S7NKxHconB https://t.co/NrXtANE5sJ

  • @jontapson Love that book by https://t.co/n3VZnwc1am

  • Black Software

    Charlton D. McIlwain

    "Black Software, for the first time, chronicles the long relationship between African Americans, computing technology, and the Internet. Through new archival sources and the voices of many of those who lived and made this history, this book centralizes African Americans' role in the Internet's creation and evolution, illuminating both the limits and possibilities for using digital technology to push for racial justice in the United States and across the globe"--

    This is indeed a wonderful book. https://t.co/SSp51YmLCN https://t.co/RVO8A93PqO

  • Kubernetes Patterns

    Bilgin Ibryam

    The way developers design, build, and run software has changed significantly with the evolution of microservices and containers. These modern architectures use new primitives that require a different set of practices than most developers, tech leads, and architects are accustomed to. With this focused guide, Bilgin Ibryam and Roland Huß from Red Hat provide common reusable elements, patterns, principles, and practices for designing and implementing cloud-native applications on Kubernetes. Each pattern includes a description of the problem and a proposed solution with Kubernetes specifics. Many patterns are also backed by concrete code examples. This book is ideal for developers already familiar with basic Kubernetes concepts who want to learn common cloud native patterns. You'll learn about the following pattern categories: Foundational patterns cover the core principles and practices for building container-based cloud-native applications. Behavioral patterns explore finer-grained concepts for managing various types of container and platform interactions. Structural patterns help you organize containers within a pod, the atom of the Kubernetes platform. Configuration patterns provide insight into how application configurations can be handled in Kubernetes. Advanced patterns covers more advanced topics such as extending the platform with operators.

    Shout out to @bibryam and @ro14nd: You two have written a wonderful, incredibly informative, and intensely useful book. Thank you! https://t.co/8Ri18Zia2t https://t.co/PiBWBLkQ5b

  • Ships of the World

    Lincoln P. Paine

    Entries for 1,000 of the world's most significant ships include physical characteristics, construction, and history

    @null_recurring https://t.co/0nV5H7H0ce

  • The biggest challenge facing many game programmers is completing their game. Most game projects fizzle out, overwhelmed by the complexity of their own code. Game Programming Patterns tackles that exact problem. Based on years of experience in shipped AAA titles, this book collects proven patterns to untangle and optimize your game, organized as independent recipes so you can pick just the patterns you need. You will learn how to write a robust game loop, how to organize your entities using components, and take advantage of the CPUs cache to improve your performance. You'll dive deep into how scripting engines encode behavior, how quadtrees and other spatial partitions optimize your engine, and how other classic design patterns can be used in games.

    @Cyento @allenholub @munificentbob You should read @munificentbob's book, Game Programming Patterns. It is excellent.

  • @nerissimo Another awesome book

  • How does a computer scientist understand infinity? What can probability theory teach us about free will? Can mathematical notions be used to enhance one's personal understanding of the Bible? Perhaps no one is more qualified to address these questions than Donald E. Knuth, whose massive contributions to computing have led others to nickname him "The Father of Computer Science"--and whose religious faith led him to understand a fascinating analysis of the Bible called the 3:16 project. In this series of six spirited, informal lectures, Knuth explores the relationships between his vocation and his faith, revealing the unique perspective that his work with computing has lent to his understanding of God. His starting point is the 3:16 project, an application of mathematical "random sampling" to the books of the Bible. The first lectures tell the story of the project's conception and execution, exploring its many dimensions of language translation, aesthetics, and theological history. Along the way, Knuth explains the many insights he gained from such interdisciplinary work. These theological musings culminate in a surprising final lecture tackling the ideas of infinity, free will, and some of the other big questions that lie at the juncture of theology and computation. Things a Computer Scientist Rarely Talks About, with its charming and user-friendly format--each lecture ends with a question and answer exchange, and the book itself contains more than 100 illustrations--is a readable and intriguing approach to a crucial topic, certain to edify both those who are serious and curious about their faiths and those who look at the science of computation and wonder what it might teach them about their spiritual world. Includes "Creativity, Spirituality, and Computer Science," a panel discussion featuring Harry Lewis, Guy L. Steele, Jr., Manuela Veloso, Donald E. Knuth, and Mitch Kapor.

    See also “Things A Computer Scientist Rarely Talks About” https://t.co/8dDsuemc6q https://t.co/rDh72IuzCH

  • Project Whirlwind

    Kent C Redmond

    @laurenweinstein The legacy and the esthetics of Project Whirlwind live on. https://t.co/MSaN8ii5tF

  • He has written and produced comedy/talk shows for over fifteen years. Now four-time Emmy winner Joe Toplyn reveals his proven methods of writing for late-night television in this one-of-a-kind insider's guide. Toplyn analyzes each type of comedy piece in the late-night TV playbook and takes you step-by-step through the process of writing it. His detailed tips, techniques, and rules include: * 6 characteristics every good monologue joke topic must have* 6 specific ways to generate punch lines* 12 tools for making your jokes their funniest* 7 types of desk pieces and how to create them* 9 steps to writing parodies and other sketches * How to go after a writing job in late night* PLUS a complete sample comedy/talk show submission packetAlso use this comprehensive manual to write short-form comedy for the Internet, sketch shows, magazines, reality shows, radio, advertising, and any other medium.

    I learned most everything I know about making amusing Twitter posts from @JoeToplyn https://t.co/XWAiq4r14z

  • Most people in the middle ages shared communal living space and lived most of their lives publicly in the midst of other people. Slowly, however, the wealthy began to build parts of their houses that were private and where private activities, such as reading, could be enjoyed. This was a new development and differed from the solitude of the hermit and the silence of the monk. Diana Webb traces what this meant for men and women growing sense of individuality in this highly original book.

    @jgordonshare Excellent question. Even in the Middle Ages there were spaces for introverts. See Privacy and Solitude: The Medieval Discovery of Personal Space https://t.co/0oo5TzN9VI

  • Cunt

    Inga Muscio

    An ancient title of respect for women, the word “cunt” long ago veered off this noble path. Inga Muscio traces the road from honor to expletive, giving women the motivation and tools to claim “cunt” as a positive and powerful force in their lives. In this fully revised edition, she explores, with candidness and humor, such traditional feminist issues as birth control, sexuality, jealousy between women, and prostitution with a fresh attitude for a new generation of women. Sending out a call for every woman to be the Cuntlovin' Ruler of Her Sexual Universe, Muscio stands convention on its head by embracing all things cunt-related. This edition is fully revised with updated resources, a new foreword from sexual pioneer Betty Dodson, and a new afterword by the author. “Bright, sharp, empowering, long-lasting, useful, sexy....”—San Francisco Chronicle “... Cunt provides fertile ground for psychological growth.”—San Francisco Bay Guardian “Cunt does for feminism what smoothies did for high-fiber diets—it reinvents the oft-indigestible into something sweet and delicious.”—Bust Magazine

    @WhoresofYore I’m reminded of this book, which a friend gave me to read several years ago. https://t.co/l9Q6nAhlHK

  • Introduction. Architectural styles. Case studies. Shared information systems. Architectural design guidance. Formal models and specifications. Linguistics issues. Tools for architectural design. Education of software architects.

    @timlee126 I always have people start with these two: https://t.co/CQZRBimdwd https://t.co/QtJSw5yC4h

  • Systems Architecting

    Eberhardt Rechtin

    M->CREATED

    @timlee126 I always have people start with these two: https://t.co/CQZRBimdwd https://t.co/QtJSw5yC4h

  • How Buildings Learn

    Stewart Brand

    @pomeranian99 See also “How Buildings Learn” by @stewartbrand https://t.co/PoKoNxqdxt

  • Larry Ellison started the high-flying tech company Oracle with $1,200 in 1977 and turned it into a billion-dollar Silicon Valley giant. If Bill Gates is the tech world's nerd king, Ellison is its Warren Beatty: racing yachts, buying jets, and romancing beautiful women. His rise to fame and fortune is a tale of entrepreneurial brilliance, ruthless tactics, and a constant stream of half-truths and outright fabrications for which the man and his company are notorious. Investigative reporter Mike Wilson, with access to Ellison himself and more than 125 of his friends, enemies, and former Oracle employees, has created an eye-opening, utterly fascinating portrayal of a Silicon Valley success story ... filled with the stuff that dreams and cultural icons are made of.

    See also this book: “The Difference Between God and Larry Ellison: *God Doesn't Think He's Larry Ellison” https://t.co/B7cxZIpZis https://t.co/WxyRTFAS9h

  • Most people in the middle ages shared communal living space and lived most of their lives publicly in the midst of other people. Slowly, however, the wealthy began to build parts of their houses that were private and where private activities, such as reading, could be enjoyed. This was a new development and differed from the solitude of the hermit and the silence of the monk. Diana Webb traces what this meant for men and women growing sense of individuality in this highly original book.

    @Greeneland And if you want to go waaaaay back in time, try "Privacy and Solitude" https://t.co/wEIxkfXNMZ

  • @pugson @aniacopian People who used https://t.co/HwzlDOyNg1 also bought this book. https://t.co/B7UXj1i8D5 https://t.co/hsLzKDGxp9

  • After Shock

    Ray Kurzweil

    After Shock marks the 50-year anniversary of Alvin Toffler's, Future Shock . The compendium of essays comprising this landmark volume offers insightful reflections on the classic text and presents compelling and surprising views of the future--through the very unique lenses of more than 100 of the world's foremost futurists, including David Brin, Po Bronson, Sanjiv Chopra, George Gilder, Newt Gingrich, Alan Kay, Ray Kurzweil, Jane McGonigal, Lord Martin Rees, Byron Reese, and many other luminaries.

    Facebook's original motto - "Move fast and break things" - is everything that Alvin Toffer predicted and everything that he feared. https://t.co/gHxWfOUe7l

  • The Peter Principle

    Dr. Laurence J Peter

    The Peter Principle. If you exchange the word “Peter” as drawn from the context of the book by Laurence Peter with its slang meaning, the concept still applies. https://t.co/R07zcubokr

  • Elemental Haiku

    Mary Soon Lee

    The elements, set to poetry.

    Flourine. Tantrums? Explosions? First step admit the problem. Electron envy. @MarySoonLee https://t.co/hJvPQEwiqS

  • Children`s book

    Idan Berger

    @feliciaday https://t.co/RGvALsNDTr https://t.co/8KsJPI3qla

  • Time to brush up on my war gaming skills. https://t.co/g7ADMkKpxK

  • After Shock

    Ray Kurzweil

    After Shock marks the 50-year anniversary of Alvin Toffler's, Future Shock . The compendium of essays comprising this landmark volume offers insightful reflections on the classic text and presents compelling and surprising views of the future--through the very unique lenses of more than 100 of the world's foremost futurists, including David Brin, Po Bronson, Sanjiv Chopra, George Gilder, Newt Gingrich, Alan Kay, Ray Kurzweil, Jane McGonigal, Lord Martin Rees, Byron Reese, and many other luminaries.

    @AfterShock2020 https://t.co/mo1NfcK100 https://t.co/Au56zJvACO

  • The story of the U.S. Department of Defense's extraordinary effort, in the period from 1983 to 1993, to achieve machine intelligence.

    @EvanFeigenbaum Indeed. See Strategic Computing: DARPA and the Quest for Machine Intelligence, 1983-1993 (History of Computing) https://t.co/RLBIU96QOC

  • Managing Technical Debt

    Philippe Kruchten

    "This is an incredibly wise and useful book. The authors have considerable real-world experience in delivering quality systems that matter, and their expertise shines through in these pages. Here you will learn what technical debt is, what is it not, how to manage it, and how to pay it down in responsible ways. This is a book I wish I had when I was just beginning my career. The authors present a myriad of case studies, born from years of experience, and offer a multitude of actionable insights for how to apply it to your project." -Grady Booch, IBM Fellow Master Best Practices for Managing Technical Debt to Promote Software Quality and Productivity As software systems mature, earlier design or code decisions made in the context of budget or schedule constraints increasingly impede evolution and innovation. This phenomenon is called technical debt, and practical solutions exist. In Managing Technical Debt, three leading experts introduce integrated, empirically developed principles and practices that any software professional can use to gain control of technical debt in any software system. Using real-life examples, the authors explain the forms of technical debt that afflict software-intensive systems, their root causes, and their impacts. They introduce proven approaches for identifying and assessing specific sources of technical debt, limiting new debt, and "paying off" debt over time. They describe how to establish managing technical debt as a core software engineering practice in your organization. Discover how technical debt damages manageability, quality, productivity, and morale-and what you can do about it Clarify root causes of debt, including the linked roles of business goals, source code, architecture, testing, and infrastructure Identify technical debt items, and analyze their costs so you can prioritize action Choose the right solution for each technical debt item: eliminate, reduce, or mitigate Integrate software engineering practices that minimize new debt Managing Technical Debt will be a valuable resource for every software professional who wants to accelerate innovation in existing systems, or build new systems that will be easier to maintain and evolve.

    @GeePawHill FYI take a look at this https://t.co/UpWgoYjLyj

  • **Winner of the 2013 Financial Times and Goldman Sachs Business Book of the Year Award** Amazon placed one of the first and largest bets on the Internet. Nothing would ever be the same again. Though Amazon.com started off delivering books through the mail, its visionary founder, Jeff Bezos, was never content with being just a bookseller. He wanted Amazon to become ‘the everything store’, offering limitless selection and seductive convenience at disruptively low prices. To achieve that end, he developed a corporate culture of relentless ambition and secrecy that's never been cracked. Until now... Jeff Bezos stands out for his relentless pursuit of new markets, leading Amazon into risky new ventures like the Kindle and cloud computing, and transforming retail in the same way that Henry Ford revolutionized manufacturing.

    @DonaldRichard https://t.co/YMelC0n1LB

  • @fintechnically https://t.co/j1mfV3reoa

  • @JenniferSertl @histoftech @KristaMarcucci1 @seattletimes @UBuffalo @dtapscott @INSEAD @UVConnect @RITbusiness @UR_AinCenter @SB_Brennan @LippesMathias @blockchain @BrettKing @SpirosMargaris @psb_dc @CryptoRitas @Jay_AHR_ @el33th4xor @mbauwens @hartsellml @artbrock @holochain @petervan @toouufii @kacarlson1 @Innotribe @envisioningtech @MawaddaBasir @Mavennet_ @RocCityLibrary See also https://t.co/MRPLhIVfay

  • 'I can't think of a better way to learn about artificial intelligence, and I've never had so much fun along the way' Adam Grant, New York Times bestselling author of Originals and Option B AI is everywhere. It powers the autocorrect function of your iPhone, helps Google Translate understand the complexity of language, and interprets your behaviour to decide which of your friends' Facebook posts you most want to see. In the coming years, it'll perform medical diagnoses and drive your car - and maybe even help our authors write the first lines of their novels. But how does it actually work? Scientist and engineer, Janelle Shane, is the go-to contributor about computer science for the New York Times, Slate, and the New Yorker. Through her hilarious experiments, real-world examples, and illuminating cartoons, she explains how AI understands our world, and what it gets wrong. More than just a working knowledge of AI, she hands readers the tools to be skeptical about claims of a smarter future. A comprehensive study of the cutting-edge technology that will soon power our world, You Look Like a Thing and I Love You is an accessible and hilarious exploration of the future of technology and society. It's Astrophysics for People In a Hurry meets Thing Explainer: an approachable guide to a fascinating scientific topic, presented with clarity, levity, and brevity by an expert in the field with a powerful and growing platform.

    Suddenly @JanelleCShane's marvelous book - You Look Like A Thing And I Love You - comes into focus. https://t.co/LYqQfecTaT

  • skilled in geometry, ingenious devices (!lival), music and astronomy. According to Ibn al-Nad!m and Ibn Khallikän their weakest subject was astronamy, but this seems to conflict with the opinions of Ibn Yunus and al-BIrun!, hoth good judges, who spoke highly of the accuracy of the Banu Musa's astronomical observations. Mul)ammad, who was the most influential of the brothers, specialised in gcomctry and astronomy, and excellcd Al)mad in all the sciences except in the construction of ingenious devices. AI-l: Iasan was a brilliant geometrician with aretenlive memoryand great powers of deduction. A rival onee tried to discredit him in front of al-Ma'mun hy saying that al- l: Iasan had read only six of the thirteen books of Euclid's Elements. AI-l: Iasan replied by saying that it was unnecessary for him to read the remainder because he could arrive at the answers to any of Euclid's problem s by deduction. AI-Ma'mun acknowledged al-l: Iasan 's skill, but did not excuse him, saying: "laziness has prevented you from 2 reading the whole ofit-it is to geometry as the Ictters a, b, t, 111 are to speech and writing. " (H. 264). AI-l: Iasan is rarely mentioned by name elsewhere in the sources and may have preferred to devote his time to scholarship, whereas his brothers were involved in a variety of undertakings. At the time of their entry into the House of Wisdom the Banu Musil were paar and needy (H.

    @ukkahamty @n2cjn And remember also the Banū Mūsā brothers, and their magnificent work, The Book of Ingenious Devices from around 800 AD. https://t.co/o85fMCT4JG

  • 24/6

    Tiffany Shlain

    In 24/6, Tiffany Shlain explores how turning off screens one day a week can work wonders on your brain, body, and soul. Internet pioneer and renowned filmmaker Tiffany Shlain takes us on a provocative and entertaining journey through time and technology, introducing a strategy for living in our 24/7 world: turning off all screens for twenty-four hours each week. This practice, which she’s done for nearly a decade with her husband and kids (sixteen and ten), has completely changed their lives, giving them more time, productivity, connection, and presence. She and her family call it “Technology Shabbat.” Drawn from the ancient ritual of Shabbat, living 24/6 can work for anyone from any background. With humor and wisdom, Shlain shares her story, offers lessons she has learned, and provides a blueprint for how to do it yourself. Along the way, she delves into the neuroscience, philosophy, psychology, and history of a weekly day of rest across cultures, making the case for why we need to bring this ritual back. A compelling personal story and a fascinating, far-reaching examination of the complex world we’ve created, 24/6 is a call to rebalance ourselves and our society.

    There’s an organized smear campaign against Silicon Valley??? While the good doctor sepal is ranting, this - the reasoned and intentional holiday from the Internet - is what a woman - @tiffanyshlain - has been presenting for years. See her latest at https://t.co/T1ObWYPo3H https://t.co/73zMsyixZS

  • @qDot Have you read Dating Design Patterns? https://t.co/n4Gzlipt4K

  • Proof of Collusion

    Seth Abramson

    @TechManBig @Jim_Jordan Clearly you have not been paying attention. See also https://t.co/8cRGXpFWzl

  • I Am a Strange Loop

    Douglas R. Hofstadter

    @wbic16 Indeed. https://t.co/Yq03bZKjjn

  • How Buildings Learn

    Stewart Brand

    @keyorgsys @ruthmalan FYI, that metaphor (and image) comes from @stewartbrand in his wonderful book "How Buildings Learn." https://t.co/MwYtJrtsQL

  • @histoftech See also https://t.co/Xe1PMk9F7q

  • Think Black

    Clyde W. Ford

    Ordered: https://t.co/KGjy6oGSfy https://t.co/KGq760Is7X

  • Managing Technical Debt

    Philippe Kruchten

    "This is an incredibly wise and useful book. The authors have considerable real-world experience in delivering quality systems that matter, and their expertise shines through in these pages. Here you will learn what technical debt is, what is it not, how to manage it, and how to pay it down in responsible ways. This is a book I wish I had when I was just beginning my career. The authors present a myriad of case studies, born from years of experience, and offer a multitude of actionable insights for how to apply it to your project." -Grady Booch, IBM Fellow Master Best Practices for Managing Technical Debt to Promote Software Quality and Productivity As software systems mature, earlier design or code decisions made in the context of budget or schedule constraints increasingly impede evolution and innovation. This phenomenon is called technical debt, and practical solutions exist. In Managing Technical Debt, three leading experts introduce integrated, empirically developed principles and practices that any software professional can use to gain control of technical debt in any software system. Using real-life examples, the authors explain the forms of technical debt that afflict software-intensive systems, their root causes, and their impacts. They introduce proven approaches for identifying and assessing specific sources of technical debt, limiting new debt, and "paying off" debt over time. They describe how to establish managing technical debt as a core software engineering practice in your organization. Discover how technical debt damages manageability, quality, productivity, and morale-and what you can do about it Clarify root causes of debt, including the linked roles of business goals, source code, architecture, testing, and infrastructure Identify technical debt items, and analyze their costs so you can prioritize action Choose the right solution for each technical debt item: eliminate, reduce, or mitigate Integrate software engineering practices that minimize new debt Managing Technical Debt will be a valuable resource for every software professional who wants to accelerate innovation in existing systems, or build new systems that will be easier to maintain and evolve.

    @techgirl1908 @SunnySachdeva85 My colleague @pbpk wrote an entire book on the subject of technical debt: https://t.co/jSLLZIhMda

  • @JonathanWHendry @shanselman @SwiftOnSecurity Let's never forget the classic Dating Design Patterns by @getopenoffice https://t.co/B7UXj1i8D5

  • UML is the industry standard notational language. Updated to include coverage of UML 2.0, this text helps the reader master the vocabulary, rules and idioms of the UML, as well as understand what the UML is and what it is not.

    @PromisePreston @NigelThomasCox @simonbrown Read most anything from @visarch and @simonbrown And, of course, there's https://t.co/LvlOneBaup

  • Face to Face

    Brian Grazer

    Featured on CBS This Morning, Squawk Box, MSNBC, CNN, Bloomberg, Forbes, Fast Company, The New York Times, and more. “Reading Face to Face is like being a fly on the wall, watching Brian Grazer work his magic. Utterly entertaining, this is how you become Hollywood’s best producer.” —Malcolm Gladwell, author of Talking to Strangers Legendary Hollywood producer and author of the bestselling A Curious Mind, Brian Grazer is back with a captivating new book about the life-changing ways we can connect with one another. Much of Brian Grazer’s success—as a #1 New York Times bestselling author, Academy Award–winning producer, father, and husband—comes from his ability to establish genuine connections with almost anyone. In Face to Face, he takes you around the world and behind the scenes of some of his most iconic movies and television shows, like A Beautiful Mind, Empire, Arrested Development, American Gangster, and 8 Mile, to show just how much in-person encounters have revolutionized his life—and how they have the power to change yours. With his flair for intriguing stories, Grazer reveals what he’s learned through interactions with people like Bill Gates, Taraji P. Henson, George W. Bush, Barack Obama, Eminem, Prince, Spike Lee, and the Afghani rapper activist Sonita: that the secret to a bigger life lies in personal connection. In a world where our attention is too often focused downward at our devices, Grazer argues that we are missing an essential piece of the human experience. Only when we are face to face, able to look one another in the eyes, can we form the kinds of connections that expand our world views, deepen our self-awareness, and ultimately lead to our greatest achievements and most meaningful moments. When we lift our eyes to look at the person in front of us, we open the door to infinite possibility.

    Face to Face: The Art of Human Connection by ⁦@BrianGrazer⁩ https://t.co/IjJ2qVRgYT

  • Smart Spacetime

    Mark Burgess

    `The err is human, to explain is [Mark Burgess]' --Patrick Debois `One of the best reads and written by one of the best minds!' --Glenn O'Donnell (about In Search of Certainty) What if space is not like we learn in mathematics,but more like a network? What happens to the ability to measure things as you shrink or expand? Since Einstein, space and time were the province of theoretical physicists and science fiction writers, but today they are of equal importance in Information Technology, Artificial Intelligence, and even Biology. This book tells a new and radical story of space and time, rooted in fundamental physics but going beyond to underpin some of the biggest questions in science and technology. This is a book about physics, it's about computers, artificial intelligence, and many other topics on surface. It's about everything that has to do with information. It draws on examples from every avenue of life, and pulls apart preconceptions that have been programmed into us from childhood. It re-examines ideas like distance,time, and speed, and asks if we really know what those things are. If they are really so fundamental and universal concepts then can we also see them and use them in computers, or in the growing of a plant? Conversely, can we see phenomena we know from computers in physics? We can learn a lot by comparing the way we describe physics with the way we describe computers---and that throws up a radical view: the concept ofvirtualization, and what it might mean for physics. `I think that it wouldn't be too much of a stretch to say that [Mark Burgess] is the closest thing to Richard Feynman within our industry' --Cameron Haight `...magnificent; a tour de force of connecting the dots of many disciplines... Mark's combination of originality, synthesis and practicality knows no equal.' --Paul Borrill

    "Space, time, matter, and information are all aspects of the same thing, and that how we label locations and times simply expresses different properties." Am reading @markburgess_osl's fascinating book, Smart Spacetime". https://t.co/IbmBa6vSAY

  • Deep Medicine

    Eric Topol

    One of America's top doctors reveals how AI will empower physicians and revolutionize patient care Medicine has become inhuman, to disastrous effect. The doctor-patient relationship--the heart of medicine--is broken: doctors are too distracted and overwhelmed to truly connect with their patients, and medical errors and misdiagnoses abound. In Deep Medicine, leading physician Eric Topol reveals how artificial intelligence can help. AI has the potential to transform everything doctors do, from notetaking and medical scans to diagnosis and treatment, greatly cutting down the cost of medicine and reducing human mortality. By freeing physicians from the tasks that interfere with human connection, AI will create space for the real healing that takes place between a doctor who can listen and a patient who needs to be heard. Innovative, provocative, and hopeful, Deep Medicine shows us how the awesome power of AI can make medicine better, for all the humans involved.

    @doctorscompany See @EricTopol and https://t.co/TDjgmbMwGW

  • Managing Technical Debt

    Philippe Kruchten

    "This is an incredibly wise and useful book. The authors have considerable real-world experience in delivering quality systems that matter, and their expertise shines through in these pages. Here you will learn what technical debt is, what is it not, how to manage it, and how to pay it down in responsible ways. This is a book I wish I had when I was just beginning my career. The authors present a myriad of case studies, born from years of experience, and offer a multitude of actionable insights for how to apply it to your project." -Grady Booch, IBM Fellow Master Best Practices for Managing Technical Debt to Promote Software Quality and Productivity As software systems mature, earlier design or code decisions made in the context of budget or schedule constraints increasingly impede evolution and innovation. This phenomenon is called technical debt, and practical solutions exist. In Managing Technical Debt, three leading experts introduce integrated, empirically developed principles and practices that any software professional can use to gain control of technical debt in any software system. Using real-life examples, the authors explain the forms of technical debt that afflict software-intensive systems, their root causes, and their impacts. They introduce proven approaches for identifying and assessing specific sources of technical debt, limiting new debt, and "paying off" debt over time. They describe how to establish managing technical debt as a core software engineering practice in your organization. Discover how technical debt damages manageability, quality, productivity, and morale-and what you can do about it Clarify root causes of debt, including the linked roles of business goals, source code, architecture, testing, and infrastructure Identify technical debt items, and analyze their costs so you can prioritize action Choose the right solution for each technical debt item: eliminate, reduce, or mitigate Integrate software engineering practices that minimize new debt Managing Technical Debt will be a valuable resource for every software professional who wants to accelerate innovation in existing systems, or build new systems that will be easier to maintain and evolve.

    @imnotdanbo See this wonderful book by @pbpk et al https://t.co/GvapbcEiSH

  • LikeWar

    P. W. Singer

    Social media has been weaponized, as state hackers and rogue terrorists have seized upon Twitter and Facebook to create chaos and destruction. This urgent report is required reading, from defense experts P.W. Singer and Emerson T. Brooking.

    @SethMacFarlane A link to the book itself. Seth, I admire how well-read you are (here is my reading list in this space: https://t.co/HhkY3ejiq0) https://t.co/nQkRvg4uw8

  • Systemantics

    John Gall

    @joseluis_torres @simonbrown A bad cut and paste on my part: here's my third recommendation. https://t.co/MqWWmTcJiM

  • Introduction. Architectural styles. Case studies. Shared information systems. Architectural design guidance. Formal models and specifications. Linguistics issues. Tools for architectural design. Education of software architects.

    @joseluis_torres @simonbrown Software Architecture: Perspectives on an Emerging Discipline https://t.co/1C4KI6WrWF Systems Architecting: Creating & Building Complex Systems https://t.co/Qkh4NGZfwl Systems Architecting: Creating & Building Complex Systems https://t.co/Qkh4NGZfwl

  • Systems Architecting

    Eberhardt Rechtin

    @joseluis_torres @simonbrown Software Architecture: Perspectives on an Emerging Discipline https://t.co/1C4KI6WrWF Systems Architecting: Creating & Building Complex Systems https://t.co/Qkh4NGZfwl Systems Architecting: Creating & Building Complex Systems https://t.co/Qkh4NGZfwl