Developer Experience (DX) is all about how easily and effectively developers can get things done. Good DX is like good UX for developers. It is about creating tools, APIs, and services that enable developers to be productive, satisfied, and empowered. This book by Addy Osmani makes the case for why DX matters - it impacts developer happiness, retention, innovation velocity, and business performance. It also explores core principles like ensuring a smooth onboarding, minimizing complexity, providing good documentation and community support. It discusses frameworks to measure DX using metrics for usability, findability, usefulness. Developer journey mapping is proposed as a technique to identify pain points and friction. The book explains how to enable a DX mindset in your organization, implement a DX roadmap, and track DX maturity levels. There are case studies demonstrating where investments in DX translated to tangible business value. With a great DX, developers can create exceptional end-user experiences. Read ahead for insights and a practical guide to improve your DX. The key takeaway is that optimizing DX should be a priority and requires a cross-functional effort spanning product, engineering and community engagement.

It’s been said that software is eating the planet. The modern economy—the world itself—relies on technology. Demand for the people who can produce it far outweighs the supply. So why do developers occupy largely subordinate roles in the corporate structure? Developer Hegemony explores the past, present, and future of the corporation and what it means for developers. While it outlines problems with the modern corporate structure, it’s ultimately a play-by-play of how to leave the corporate carnival and control your own destiny. And it’s an emboldening, specific vision of what software development looks like in the world of developer hegemony—one where developers band together into partner firms of “efficiencers,” finally able to command the pay, respect, and freedom that’s earned by solving problems no one else can. Developers, if you grow tired of being treated like geeks who can only be trusted to take orders and churn out code, consider this your call to arms. Bring about the autonomous future that’s rightfully yours. It’s time for developer hegemony.

How do successful agile teams deliver bug-free, maintainable software—iteration after iteration? The answer is: By seamlessly combining development and testing. On such teams, the developers write testable code that enables them to verify it using various types of automated tests. This approach keeps regressions at bay and prevents “testing crunches”—which otherwise may occur near the end of an iteration—from ever happening. Writing testable code, however, is often difficult, because it requires knowledge and skills that cut across multiple disciplines. In Developer Testing, leading test expert and mentor Alexander Tarlinder presents concise, focused guidance for making new and legacy code far more testable. Tarlinder helps you answer questions like: When have I tested this enough? How many tests do I need to write? What should my tests verify? You’ll learn how to design for testability and utilize techniques like refactoring, dependency breaking, unit testing, data-driven testing, and test-driven development to achieve the highest possible confidence in your software. Through practical examples in Java, C#, Groovy, and Ruby, you’ll discover what works—and what doesn’t. You can quickly begin using Tarlinder’s technology-agnostic insights with most languages and toolsets while not getting buried in specialist details. The author helps you adapt your current programming style for testability, make a testing mindset “second nature,” improve your code, and enrich your day-to-day experience as a software professional. With this guide, you will Understand the discipline and vocabulary of testing from the developer’s standpoint Base developer tests on well-established testing techniques and best practices Recognize code constructs that impact testability Effectively name, organize, and execute unit tests Master the essentials of classic and “mockist-style” TDD Leverage test doubles with or without mocking frameworks Capture the benefits of programming by contract, even without runtime support for contracts Take control of dependencies between classes, components, layers, and tiers Handle combinatorial explosions of test cases, or scenarios requiring many similar tests Manage code duplication when it can’t be eliminated Actively maintain and improve your test suites Perform more advanced tests at the integration, system, and end-to-end levels Develop an understanding for how the organizational context influences quality assurance Establish well-balanced and effective testing strategies suitable for agile teams

Developers sniff out anything that seems like marketing. Typical tactics will fall flat. And you'll be staring at your analytics with questions they can't possibly answer. Most developers are too skeptical to fill out lead forms or provide their real email address.To reach a technical audience, you must acknowledge that developer marketing does not exist. Then you can authentically engage with developers.Adam DuVander has worked with dozens of developer-focused companies to attract thousands of the right developers. In Developer Marketing Does Not Exist he helps you uncover the mystery within your audience so you can reach more developers.

This is the eBook of the printed book and may not include any media, website access codes, or print supplements that may come packaged with the bound book. Through four complete sprints, this book takes you through every step needed to build brand new cross-platform web apps with ASP.NET Core, and make them available on the Internet. You won't just master Microsoft's revolutionary open source ASP.NET Core technology: you'll learn how to integrate the immense power of MVC, Docker, Azure Web Apps, Visual Studio and Visual Studio Code, C#, JavaScript, TypeScript, and Entity Framework. Working through the authors' carefully designed sprints, you'll start with a blank canvas, move through software architecture and design, adjusting to user feedback, recovering from mistakes, builds, testing, deployment, maintenance, refactoring, and more. Along the way, you'll learn techniques for delivering state-of-the-art software to users more rapidly and repeatably than ever before.

Increasingly, business leaders are either looking to start a new developer program at their company or looking to increase the impact of their existing DevRel program. In this context, software developers are finally recognized as legitimate decision makers in the technology buying process, regardless of the size of their organization. New companies are appearing with the sole purpose of making tools for developers, and even companies whose primary focus was elsewhere are waking up to the developer opportunity. Even as the need and demand for DevRel has grown, there are still re-occurring challenges for DevRel leaders. It is these challenges that this book addresses, covering all aspects of a DevRel program. It is an essential reference to professionalize the practice of developer relations by providing you with strategic, repeatable, and adoptable frameworks, processes, and tools, including developer segmentation and personas, and developer experience frameworks. In Developer Relations, you’ll find the answers to the following questions: How do we convince stakeholders to support a program? How do we go about creating a program? How do we make developers aware of our offer? How do we stand out from the crowd? How do we get developers to use our products? How do we ensure developers are successful using our products? How do we measure success? How do we maintain the support of our stakeholders? After reading this book you’ll have a clear definition of what developer relations is, the type of companies that engage in DevRel, and the scope and business models involved. What You Will Learn Discover what developer relations is and how it contributes to a company’s success Launch a DevRel program Operate a successful program Measure the success of your program Manage stakeholders Who This Book Is For Those interested in starting a new developer program or looking to increase the impact of their existing one. From executives to investors, from marketing professionals to engineers, all will find this book useful to realize the impact of developer relations.

"Two thumbs up" —Gregory V. Wilson, Dr. Dobbs Journal (October 2004) No one can disparage the ability to write good code. At its highest levels, it is an art. But no one can confuse writing good code with developing good software. The difference—in terms of challenges, skills, and compensation—is immense. Coder to Developer helps you excel at the many non-coding tasks entailed, from start to finish, in just about any successful development project. What's more, it equips you with the mindset and self-assurance required to pull it all together, so that you see every piece of your work as part of a coherent process. Inside, you'll find plenty of technical guidance on such topics as: Choosing and using a source code control system Code generation tools--when and why Preventing bugs with unit testing Tracking, fixing, and learning from bugs Application activity logging Streamlining and systematizing the build process Traditional installations and alternative approaches To pull all of this together, the author has provided the source code for Download Tracker, a tool for organizing your collection of downloaded code, that's used for examples throughout this book. The code is provided in various states of completion, reflecting every stage of development, so that you can dig deep into the actual process of building software. But you'll also develop "softer" skills, in areas such as team management, open source collaboration, user and developer documentation, and intellectual property protection. If you want to become someone who can deliver not just good code but also a good product, this book is the place to start. If you must build successful software projects, it's essential reading.