Unilibrary. Oliy ta'lim muassasalarining yagona elektron kutubxona axborot tizimi.

Kotlin Coroutines by Tutorials

You’re reading an early access edition of Kotlin Coroutines by Tutorials. As we continue to add chapters to the early access edition of this book, we’ll notify you and let you know how to access the updated versions. We hope you enjoy the preview of this book, and that you’ll come back to help us celebrate more releases of Kotlin Coroutines by Tutorials as we work on the book! The best way to get update notifications is to sign up for our monthly newsletter. This includes a list of the tutorials that came out on raywenderlich.com that month, any important news like book updates or new books, and a list of our favorite development links for that month.

Visual Analytics Fundamentals

For as long as I can remember, I have always been fascinated by the power of a good story. Like taste buds, our taste for stories evolves over time, both in terms of format and content. Our appetite changes alongside age, experiences, and interests, yet still the desire for a good story persists. We crave stories; it’s part of our design. Humans are intrinsically hungry for a good story. They entertain us, educate us, and provide mechanisms to transmit knowledge, information, and experiences. We’re rather indiscriminate about how we receive stories, too. In fact, according to scientific evidence, we might even prefer stories that move us and touch our senses.

Information Technology and Educationalmanagement in the Knowledge Society

Developments in management information systems (MIS) have been well suited to the collation, storage and dissemination of summative assessment data and have reached a point where data can now be used for comparative purposes at national, local and individual pupil levels. Trends in assessment in English secondary schools have focused primarily on its use for purposes of monitoring and accountability.

The Scrum Anti-Patterns Guide

The primary purpose of The Scrum Anti-Patterns Guide: Challenges Every Scrum Team Faces and How to Overcome Them is to help Scrum practitioners identify, understand, and address commonly observed patterns of behavior that undermine the effectiveness of Scrum in achieving its goals. The book addresses these challenges—from the misaligned understanding of roles and practices to organizational issues—highlighting these anti-patterns and pointing to practical solutions. The guide seeks to enhance the application of Scrum, making it more effective in driving innovation, productivity, and overall value delivery. In real life, stakeholders are not usually interested in how we solve their problems as long as we ethically play by the rules of our society in alignment with our organization’s culture. Instead, they are interested in the regular delivery of valuable Increments.

The Role of an IT Manager

IT Managers need to wear a lot of hats. Different parts of the organization will have different expectations of this position, and you’ll have to address them all. Finance expects you to manage costs. Sales and Marketing will want to see IT help generate revenue. The auditors are looking over your shoulder. Your staff is looking for guidance, career development, and a work-life balance. The executive traveling to Dubai wants to know if his cell phone will work there, and how to use the hotel’s Wi-Fi. And the administrative assistant down the hall just wants her printer to stop smudging. This chapter examines the varied roles and responsibilities of an IT Manager.

The Language of SQL (Third Ed.)

A huge thanks goes out to all at Pearson who assisted with this book. I’d like to thank Kim Spencer, who encouraged me to write a third edition, and Chelsea Noack, who oversaw and guided me through the project, as well as the editors at Pearson who assisted with this project, Tracey Croom, Chris Zahn, and Sandra Schroeder. I’d also like to thank project editor and copy editor Dan Foster, who added some grace to my sentences, as well as Julien Kervizic, who did a superb job on the technical review. As with the second edition, Chuti Prasertsith provided a wonderfully vibrant cover design. Finally, I must mention the generally thankless tasks of the book’s indexer, Valerie Haynes Perry; proofreader, Scout Festa; and compositor, Danielle Foster.

The Async-First Playbook

We’ve come a long way. Pioneers like GitLab wrote the playbook for remote work over a decade ago, yet it took a global pandemic to open the world’s eyes to the possibilities of remote work. Today, many organizations embrace what we call “location independence.” This encapsulates the magic that happens when a business decouples results from physical geography. While this has transformed millions of lives and enterprises, it’s only the start of an even greater revolution. The future of remote work—or, dare I say, the future of work—is time independence. Since at least the advent of the internet, the majority of knowledge workers have remained bound to time. The way we design our lives and the dreams we allow ourselves to contemplate are constrained by a fixed reality: the rigidity of a workday. What happens when we shake off that rigidity? What design principles can humans apply to their own lives when we leverage tools, software, AI, and workflows to achieve professional goals outside the strict bounds of time? We begin to optimize for what matters most. We reprioritize our individual identity stacks—the layers that make us individually us. Businesses become stronger and more resilient to crises. They become magnets for the most talented people, those who value flexibility over all else and who generate otherworldly results as a measure of their gratitude.

Serverless as a Game Changer

The gap between the best software development teams and average software development teams is enormous. The best teams deliver delightful, scalable, stable software to users quickly and regularly. Average teams deliver acceptable software that works most of the time, with months or even years between significant improvements. Many teams even struggle to deliver anything but small, iterative changes, with even those taking surprising amounts of time. Software development and cloud services and tools make developing and deploying software increasingly cheaper, faster, and better—but very few organizations take advantage of these innovations. This book lays out the principles, strategies, and tactics that can propel your organization or teams to world-class output by harnessing a Serverless mindset. Historically, to deliver web-scale applications with wonderful customer experience, organizations have had to hire expensive, superior talent in many disciplines: networking, infrastructure, systems administration, software architecture, back-end software development, API design, and front-end application design. The demand for these talented employees has always exceeded the number of them, and most companies have simply been unable to acquire talent that would enable them to build products such as a Google or Netflix.

International Business and Information Technology

International Business and Information Technology is a breakthrough text that analyzes the relationship between international business operations and information technology. First, it assesses the impact of current developments in IT on the operation of multinational corporations on both a practical and theoretical level, and explores how it can improve competitive advantage. Second, it investigates how doing business in an international environment affects the design, implementation, and management of information systems for global enterprises.

Programming with Rust

Rust is a general-purpose language for creating safe, secure, and scalable applications. The language has features from several programming paradigms, as described shortly. Rust was originally designed as a systems programming language. However, it has emerged as a more versatile language capable of creating a variety of application types, including systems programming, web services, desktop applications, embedded systems, and more. Although it may sound cliché, what you can accomplish with Rust is only limited by your imagination. Different! That is an accurate assessment of Rust. Although the Rust syntax is based on the C and C++ languages, the similarity with other C-based languages often ends there. In addition, Rust is not different just to be different; it is a difference with a purpose. Rust’s borrow checker is an excellent example of a difference with a purpose. The borrow checker is a unique feature within Rust that promotes safe coding practices by enforcing rules related to the single ownership principal. No other language has this feature. For that reason, the borrow checker is a foreign concept to many developers but nonetheless invaluable.

Information Technology for Counterterrorism

The study from which this report is largely derived was supported by private funds from the National Academies. The additional work required to produce this report was supported by core funding from the Computer Science and Telecommunications Board (CSTB).

Seeking Transformation Through Information Technology

We have been motivated to write this book to capture some of the richness of country experiences in their journey toward e-transformation. From our own practice and observation of the aspirations and challenges of developing countries, we believe there are a lot of lessons to learn from sharing these experiences. They transcend the formal descriptions of national ICT strategies, which typically describe objectives and list of actions and investments based on static assessment of e-readiness. We attempt to capture the dynamics of formulating and implementing a strategy, for some countries how the journey started, and for others who have been pursuing e-transformation for two or more decades, the evolution of a series of strategies.

Enterprise Architecture A to Z

This book contains information obtained from authentic and highly regarded sources. Reasonable efforts have been made to publish reliable data and information, but the author and publisher cannot assume responsibility for the validity of all materials or the consequences of their use. The authors and publishers have attempted to trace the copyright holders of all material reproduced in this publication and apologize to copyright holders if permission to publish in this form has not been obtained. If any copyright material has not been acknowledged please write and let us know so we may rectify in any future reprint.

Engaging privacy and information technology in a digital age

This book has been reviewed in draft form by individuals chosen for their diverse perspectives and technical expertise, in accordance with procedures approved by the National Research Council’s Report Review Committee. The purpose of this independent review is to provide candid and critical comments that will assist the institution in making its published report as sound as possible and to ensure that the report meets institutional standards for objectivity, evidence, and responsiveness to the study charge.

Patterns of Distributed Systems

In 2017, I was involved in developing a software system for a large optical telescope called Thirty Meter Telescope (TMT). We needed to build a core framework and services to be used by various subsystems. The subsystem components had to discover each other and detect component failures. There was also a requirement to store metadata about these components. The service responsible for storing this information had to be fault-tolerant. We couldn’t use off-the-shelf products and frameworks due to the unique nature of the telescope ecosystem. We had to build it all from scratch—to create a core framework and services that different subsystems of the software could use. In essence, we had to build a distributed system. I had designed and architected enterprise systems using products such as Kafka, Cassandra, and MongoDB or cloud services from providers like AWS and GCP. All these products and services are distributed and solve similar problems. For the TMT system, we had to build a solution ourselves. To compare and validate our implementation choices with these proven products, we needed a deeper understanding of the inner workings of some of these products. We had to figure out how all these cloud services and products are built and why they are built that way. Their own documentation often proved too product-specific for that.

Self-Organization in Optical Systems and Applications in Information Technology

This book is subject to copyright. All rights are reserved, whether the whole or part of the material is concerned, specifically the rights of translation, reprinting, reuse of illustrations, recitation, broadcasting, reproduction on microfilm or in any other way, and storage in data banks. Duplication of this publication or parts thereofis permitted only under the provisions of the Gennan Copyright Law of September 9, 1965, in its current version, and permission for use must always be obtained from Springer-Verlag. Violations are liable for prosecution under the Gennan Copyright Law.