検索キーワード： ソフトウェア開発

Listen to Quality Assurance to discover everything you need to know about testing and software quality, step by step to increase your software skill set. Learn how to dominate computer systems. All your basic knowledge in one purchase!

Practical techniques for writing code that is robust, reliable, and easy for team members to understand and adapt. In Good Code, Bad Code you’ll learn how to: Think about code like an effective software engineer, write functions that read like well-structured sentences, ensure code is reliable and bug free, effectively unit test code, identify code that can cause problems and improve it, write code that is reusable and adaptable to new requirements, improve your medium and long-term productivity, and save yourself and your team time.

The Software Engineering industry often evaluates engineers based on how many lines of code they write, how many years of experience they have, or how many features they ship. But I think a more powerful metric is the number of bugs they encountered, reproduced, traced to their root cause and fixed. Those experiences shape an engineer far more than raw output or time served in my opinion, let me elaborate. Bugs hinder the stability of software, which affects the user experience.

To ensure that applications are reliable and always available, more businesses today are moving applications to AWS. But many companies still struggle to design and build these cloud applications effectively. With this practical guide, software, DevOps, and cloud engineers will learn how to implement resilient designs and configurations in the cloud using hands-on independent labs.

At most technology companies, you'll reach Senior software engineer, the career level for software engineers, in five to eight years. At the career level, your company's career ladder won't require that you work towards the next promotion; being promoted further is an exception rather than expected. This is also when many engineers are first given an opportunity to move into engineering management.

As organizations shift from monolithic applications to smaller, self-contained microservices, distributed systems have become more fine-grained. But developing these new systems brings its own host of problems. This expanded second edition takes a holistic view of topics that you need to consider when building, managing, and scaling microservices architectures. Through clear examples and practical advice, author Sam Newman gives everyone from architects and developers to testers and IT operators a firm grounding in the concepts.

A decade ago, developers built information-sharing software by writing a lot of custom code in a single code base, then adding layers of caching. Now we build information systems: interdependent software and services, data platforms, and event streams. Many of our software-to-systems initiatives fail, though, and when they do, we double down on traditional linear approaches. But linear thinking cannot resolve systems challenges. We need to shift to systems thinking.

We're at an inflection point in data, where our data management solutions no longer match the complexity of organizations, the proliferation of data sources, and the scope of our aspirations to get value from data with AI and analytics. In this practical book, Zhamak Dehghani introduces data mesh, a decentralized sociotechnical paradigm drawn from modern distributed architecture that provides a new approach to sourcing, sharing, accessing, and managing analytical data at scale.

Most people don’t need “better AI.” They need control. Right now, AI feels random. Sometimes it works. Sometimes it gives you something amazing. Most of the time… it misses the mark and you don’t know why. That’s not an AI problem. That’s a communication problem. Nano Banana Pro was written to fix that. This is not a theory book. It’s not a hype book. And it’s definitely not a “here’s what AI might do someday” book.

AI is transforming software development, shifting programmers from writing code to collaborating with AI in an intent-driven workflow. Vibe coding—a prompt-first, exploratory approach where you describe what you want in natural language and let a large language model fill in the...

Microservices Patterns teaches you how to develop and deploy production-quality microservices-based applications. This invaluable set of design patterns builds on decades of distributed system experience, adding new patterns for writing services and composing them into systems that scale and perform reliably under real-world conditions. More than just a patterns catalog, this practical guide offers experience-driven advice to help you design, implement, test, and deploy your microservices-based application.

What do you need to know to be a successful software engineer? Undergraduate curricula and bootcamps may teach the fundamentals of algorithms and writing code, but they rarely cover topics vital to your career advancement. With this practical book, you'll learn the skills you need to succeed and...

Talking to people about your designs might seem like a basic skill, but it can be difficult to do well. In many cases, how you communicate with stakeholders, clients, and other non-designers may be more important than the designs themselves. Because if you can't get their support, your work will never see the light of day - no matter how good it is. This practical guide focuses on principles, tactics, and actionable methods for presenting your designs.

Using stories from his time at Netscape, Apple, and Slack, Michael Lopp presents a series of small but compelling practices to help you build leadership skills. You’ll learn how to create teams that are highly productive, highly respected, and highly trusted. The essays in this book examine the practical skills Lopp learned from exceptional leaders - as a manager at Netscape, a senior manager and director at Apple, and an executive at Slack. You’ll learn how to apply these lessons to your own experience.

In this book, Melissa Perri explains how laying the foundation for great product management can help companies solve real customer problems while achieving business goals. By understanding how to communicate and collaborate within a company structure, you can create a product culture that benefits both the business and the customer. You'll learn product management principles that can be applied to any organization, big or small. 

Most companies developing software employ something they call "Agile." But there's widespread misunderstanding of what Agile is and how to use it. If you want to improve your software development team's agility, this comprehensive guidebook's clear, concrete, and detailed guidance explains what to do and why, and when to make trade-offs.

Fanatical Prospecting gives salespeople, sales leaders, entrepreneurs, and executives a practical, eye-opening guide that clearly explains the why and how behind the most important activity in sales and business development—prospecting. Step by step, Jeb Blount outlines his innovative approach to prospecting that works for real people, in the real world, with real prospects.

Few books in computing have had as profound an influence on software management as "peopleware". The unique insight of this longtime best seller is that the major issues of software development are human, not technical. They’re not easy issues; but solve them, and you’ll maximize your chances of success. For this third edition, the authors have added six new chapters and updated the text throughout, bringing it in line with today’s development environments and challenges.

The system design interview is one of the hardest challenges you'll face in the software engineering hiring process. This practical book gives you the insights, the skills, and the hands-on practice you need to ace the toughest system design interview questions and land the job and salary you want.

Improving existing code - refactoring - is one of the most common tasks you’ll face as a programmer. Five Lines of Code teaches you clear and actionable refactoring rules that you can apply without relying on intuitive judgements such as “code smells”. Following the author’s expert perspective - that refactoring and code smells can be learned by following a concrete set of principles - you’ll learn when to refactor your code, what patterns to apply to what problem, and the code characteristics that indicate it’s time for a rework.