This book doesn't tell you how to write faster code, or how to write code with fewer memory leaks, or even how to debug code at all. What it does tell you is how to build your product in better ways, how to keep track of the code that you write, and how to track the bugs in your code. Plus some more things you'll wish you had known before starting a project. Practical Development Environments is a guide, a collection of advice about real development environments for small to medium-sized projects and groups. Each of the chapters considers a different kind of tool - tools for tracking versions of files, build tools, testing tools, bug-tracking tools, tools for creating documentation, and tools for creating packaged releases. Each chapter discusses what you should look for in that kind of tool and what to avoid, and also describes some good ideas, bad ideas, and annoying experiences for each area. Specific instances of each type of tool are described in enough detail so that you can decide which ones you want to investigate further. Developers want to write code, not maintain makefiles. Writers want to write content instead of manage templates. IT provides machines, but doesn't have time to maintain all the different tools. Managers want the product to move smoothly from development to release, and are interested in tools to help this happen more often. Whether as a full-time position or just because they are helpful, all projects have toolsmiths: making choices about tools, installing them, and then maintaining the tools that everyone else depends upon. This book is especially for everyone who ends up being a toolsmith for his or her group.

Everyone wants a technical environment for developing their software. Containing guidelines for how to create and maintain a development environment, this book discusses some of the tools covering different areas such as version control, build tools, testing tools, bug tracking systems, documentation environments, release tools, and maintenance.

This book provides an overview of tools and techniques used in enterprise software development, many of which are not taught in academic programs or learned on the job. This is an ideal resource containing lots of practical information and code examples that you need to master as a member of an enterprise development team. This book aggregates many of these "on the job" tools and techniques into a concise format and presents them as both discussion topics and with code examples. The reader will not only get an overview of these tools and techniques, but also several discussions concerning operational aspects of enterprise software development and how it differs from smaller development efforts. For example, in the chapter on Design Patterns and Architecture, the author describes the basics of design patterns but only highlights those that are more important in enterprise applications due to separation of duties, enterprise security, etc. The architecture discussion revolves has a similar emphasis – different teams may manage different aspects of the application’s components with little or no access to the developer. This aspect of restricted access is also mentioned in the section on logging. Theory of logging and discussions of what to log are briefly mentioned, the configuration of the logging tools is demonstrated along with a discussion of why it’s very important in an enterprise environment.

Agile Project Delivery reviews how different Agile methods can be applied to project delivery in complex corporate environments beyond the Agile Manifesto’s original scope of software development. Taking readers through a typical project lifecycle, the text demonstrates how Agile techniques can be applied to each phase of a project using valuable tools and examples. Agile Project Delivery covers various approaches that are used across the many methodologies and frameworks that are part of the Agile family, including Scrum, XP, and Crystal, as well as some of Agile’s influences, such as Lean and Kanban. Agile Project Delivery also provides readers with advanced instructions for using Atlassian’s industry-leading Agile software, Jira. Bridging the gap between Agile methodology and application, this concise guide features practical delivery approaches, engaging case studies, useful templates to assist in Agile application, and chapter discussion questions to reinforce understanding on how to harness the benefits of Agile. With a focus on settings outside of software development and an accessible, pragmatic approach, Agile Project Delivery is an invaluable resource for students in any project management course, as well as for both aspiring and experienced project practitioners.

1 : Introduction -- 2 : Fundamentals of IDL Syntax -- 3 : Writing IDL Programs -- 4 : Input and Output -- 5 : Direct Graphics -- 6 : Plotting Data -- 7 : Displaying Images -- 8 : Creating Graphical Output -- 9 : Graphical User Interfaces (GUIs) -- Appendix A : IDL on the Internet -- Appendix B : Mathematical Routines -- Appendix C : Widget Event Structures -- Appendix D : Widget Properties -- Appendix E : Graphics Device Properties.

Develop applications for the real world with a thorough software testing approach Key Features Develop a thorough understanding of TDD and how it can help you develop simpler applications with no defects using C# and JavaScript Adapt to the mindset of writing tests before code by incorporating business goals, code manageability, and other factors Make all your software units and modules pass tests by analyzing failed tests and refactoring code as and when required Book Description Test-Driven Development (TDD) is a methodology that helps you to write as little as code as possible to satisfy software requirements, and ensures that what you've written does what it's supposed to do. If you're looking for a practical resource on Test-Driven Development this is the book for you. You've found a practical end-to-end guide that will help you implement Test-Driven Techniques for your software development projects. You will learn from industry standard patterns and practices, and shift from a conventional approach to a modern and efficient software testing approach in C# and JavaScript. This book starts with the basics of TDD and the components of a simple unit test. Then we look at setting up the testing framework so that you can easily run your tests in your development environment. You will then see the importance of defining and testing boundaries, abstracting away third-party code (including the .NET Framework), and working with different types of test double such as spies, mocks, and fakes. Moving on, you will learn how to think like a TDD developer when it comes to application development. Next, you'll focus on writing tests for new/changing requirements and covering newly discovered bugs, along with how to test JavaScript applications and perform integration testing. You'll also learn how to identify code that is inherently un-testable, and identify some of the major problems with legacy applications that weren't written with testability in mind. By the end of the book, you'll have all the TDD skills you'll need and you'll be able to re-enter the world as a TDD expert! What you will learn The core concepts of TDD Testing in action with a real-world case study in C# and JavaScript using React Writing proper Unit Tests and testable code for your application Using different types of test double such as stubs, spies, and mocks Growing an application guided by tests Exploring new developments on a green-field application Mitigating the problems associated with writing tests for legacy applications Modifying a legacy application to make it testable Who this book is for This book is for software developers with a basic knowledge of Test Driven Development (TDD) who want a thorough understanding of how TDD can benefit them and the applications they produce. The examples in this book are in C#, and you will need a basic understanding of C# to work through these examples.