Practical Development Environments Matthew B. Doar

Practical Development Environments Matthew B. Doar - okladka książki

Autor:: Matthew B. Doar
Wydawnictwo:: O'Reilly Media (Z chęcią przeczytam książkę w języku polskim)
Ocena:: Bądź pierwszym, który oceni tę książkę
Stron:: 330
Dostępne formaty:: ePub

Mobi

Ebook

118,15 zł ~~139,00 zł~~ (-15%)

29,90 zł najniższa cena z 30 dni

Dodaj do koszyka lub Kup na prezent Kup 1-kliknięciem

Poleć tę książkę znajomemu Poleć tę książkę znajomemu!!

Przenieś na półkę

Do przechowalni

Zostało Ci na świąteczne zamówienie

opcje wysyłki »

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.

Wybrane bestsellery

Ebooka "Practical Development Environments" przeczytasz na:

czytnikach Inkbook, Kindle, Pocketbook, Onyx Boox i innych
systemach Windows, MacOS i innych

systemach Windows, Android, iOS, HarmonyOS
na dowolnych urządzeniach i aplikacjach obsługujących formaty: PDF, EPub, Mobi

Masz pytania? Zajrzyj do zakładki Pomoc »

Oceny i opinie klientów: Practical Development Environments Matthew B. Doar

(0)

Szczegóły książki

ISBN Ebooka:: 978-05-965-5383-8, 9780596553838
Data wydania ebooka :: 2005-09-23 Data wydania ebooka często jest dniem wprowadzenia tytułu do sprzedaży i może nie być równoznaczna z datą wydania książki papierowej. Dodatkowe informacje możesz znaleźć w darmowym fragmencie. Jeśli masz wątpliwości skontaktuj się z nami sklep@ebookpoint.pl.
Język publikacji:: angielski
Rozmiar pliku ePub:: 1.1MB
Rozmiar pliku Mobi:: 1.1MB

Zgłoś erratę

Kategorie

Kliknij, aby zgłosić błędnie przypisaną kategorię »

Informatyka » Programowanie

Dostępność produktu

Produkt nie został jeszcze oceniony pod kątem ułatwień dostępu lub nie podano żadnych informacji o ułatwieniach dostępu lub są one niewystarczające. Prawdopodobnie Wydawca/Dostawca jeszcze nie umożliwił dokonania walidacji produktu lub nie przekazał odpowiednich informacji na temat jego dostępności.

Spis treści książki

Practical Development Environments
- SPECIAL OFFER: Upgrade this ebook with OReilly
- Preface
  - What This Book Is About
  - What This Book Is Not About
  - Who Should Read This Book
  - Whats Inside
  - Style Conventions
  - Using Code Examples
  - Safari Enabled
  - Comments and Questions
  - Acknowledgments
- 1. Introduction
  - 1.1. Developing Software Products
  - 1.2. Open and Closed Software Development
  - 1.3. Dirty Secrets of Software Projects
  - 1.4. What Does "Practical" Mean?
  - 1.5. A Personal Tools Quiz
- 2. Project Basics
  - 2.1. The Parts of a Project
  - 2.2. Software Configuration Management
  - 2.3. Building Software
  - 2.4. Testing Software
  - 2.5. Tracking Bugs
  - 2.6. Writing Documentation
  - 2.7. Releasing Products
  - 2.8. Maintenance
  - 2.9. Recommended Tools
    - 2.9.1. Modern Environments
    - 2.9.2. Classic Environments
    - 2.9.3. Future Environments
- 3. Project Concepts
  - 3.1. Preconstructed Development Environments
    - 3.1.1. SourceForge
    - 3.1.2. GForge
    - 3.1.3. CollabNet
    - 3.1.4. Savane
    - 3.1.5. BerliOS
    - 3.1.6. Improving PDEs
  - 3.2. Why Integration Is Helpful
  - 3.3. Why Automation Is Vital
  - 3.4. Automation Environments
    - 3.4.1. Shell Scripts and Batch Files
    - 3.4.2. Tinderbox
    - 3.4.3. Anthill
    - 3.4.4. CruiseControl
  - 3.5. Labeling Builds
  - 3.6. Naming Projects and Machines
    - 3.6.1. Choosing Project Names
    - 3.6.2. Choosing Machine Names
  - 3.7. Choosing New Tools
    - 3.7.1. Steps When Changing Tools
  - 3.8. Internationalization and Localization
  - 3.9. Authentication, Authorization, and Accounting
- 4. Software Configuration Management
  - 4.1. Why Do I Need SCM?
  - 4.2. What SCM Is and Is Not
  - 4.3. Drawbacks of SCM
  - 4.4. A Typical Day's Work with SCM
  - 4.5. SCM Annoyances
    - 4.5.1. Branches and Tags
    - 4.5.2. When to Branch? When to Tag?
    - 4.5.3. Naming Branches and Tags
    - 4.5.4. Merge Madness
    - 4.5.5. Security
    - 4.5.6. Access Wars
    - 4.5.7. Filenames to Avoid
    - 4.5.8. Backups and SCM
      - 4.5.8.1. Backing up CVS
  - 4.6. SCM Tools
    - 4.6.1. CVS
      - 4.6.1.1. Making your life with CVS easier
    - 4.6.2. Subversion
    - 4.6.3. Arch
    - 4.6.4. Perforce
    - 4.6.5. BitKeeper
    - 4.6.6. ClearCase
    - 4.6.7. Visual SourceSafe
  - 4.7. Comparison of SCM Tools
  - 4.8. Wider Uses of SCM
  - 4.9. Checklist
- 5. Building Software
  - 5.1. How Software Gets Built
    - 5.1.1. The Different Stages of a Build
    - 5.1.2. A Typical Build File
  - 5.2. Build States: Virgin, Up-to-date, Changed, Interrupted, Clean
    - 5.2.1. Good Builds, Bad Builds
    - 5.2.2. Build States and Different Targets
    - 5.2.3. Build States in Practice
  - 5.3. Build Dependencies
    - 5.3.1. When Build Dependencies Go Wrong
    - 5.3.2. How Build Dependencies Change
  - 5.4. Common Build Problems
    - 5.4.1. Slow Builds
  - 5.5. Build Tools
    - 5.5.1. Shell Scripts and Batch Files
    - 5.5.2. make
    - 5.5.3. GNU Autotools
      - 5.5.3.1. Autoconf
      - 5.5.3.2. Automake
      - 5.5.3.3. Libtool
      - 5.5.3.4. An Autotools "Hello World" program
      - 5.5.3.5. Debugging GNU Autotools installs
      - 5.5.3.6. More Autotools
    - 5.5.4. Ant
    - 5.5.5. Jam
    - 5.5.6. SCons
    - 5.5.7. Custom Build Tools
  - 5.6. Comparison of Build Tools
  - 5.7. Changing Your Build Tool
  - 5.8. Checklist
- 6. Testing Software
  - 6.1. Different Kinds of Tests
    - 6.1.1. Unit Tests
    - 6.1.2. System Tests
    - 6.1.3. Customer Tests
    - 6.1.4. Other Tests
  - 6.2. Why Automate Your Tests?
  - 6.3. Evaluating Test Environments
    - 6.3.1. Preparing to Test
    - 6.3.2. Running the Tests
    - 6.3.3. After the Tests
    - 6.3.4. Good Test Reports
  - 6.4. Test Environments
    - 6.4.1. Shell Scripts and Batch Files
    - 6.4.2. xUnit
    - 6.4.3. DejaGnu
    - 6.4.4. SilkTest
  - 6.5. Types of Test Tools
    - 6.5.1. Memory Analyzers
    - 6.5.2. Coverage Tools
    - 6.5.3. Performance Tools
    - 6.5.4. Static Code Analyzers
  - 6.6. The Difficult Parts of Testing
    - 6.6.1. Faults of Omission
    - 6.6.2. Capturing Output
    - 6.6.3. Using Multiple Machines
      - 6.6.3.1. Sending commands
      - 6.6.3.2. Starting the tests
      - 6.6.3.3. Collecting the data
    - 6.6.4. Only a Developer Can Do That!
    - 6.6.5. Accessibility Testing
  - 6.7. Checklist
- 7. Tracking Bugs
  - 7.1. Tool Requirements
  - 7.2. Bug Tracking Tools
    - 7.2.1. Spreadsheets
    - 7.2.2. Different Server Technologies
    - 7.2.3. Bugzilla
    - 7.2.4. GNATS
    - 7.2.5. FogBugz
    - 7.2.6. JIRA
    - 7.2.7. TestTrack
    - 7.2.8. Custom Bug Tracking Tools
  - 7.3. Bug Tracking Annoyances
    - 7.3.1. Multiplying Products
    - 7.3.2. Cleaning Up
    - 7.3.3. One Bug, Multiple Releases
    - 7.3.4. Severity Inflation
    - 7.3.5. Identifying the Right Area
    - 7.3.6. Customizing the Bug Tracking System
    - 7.3.7. Overloading Fields
    - 7.3.8. Bug History
    - 7.3.9. Bug Statistics
    - 7.3.10. Writing an Effective Bug Report
  - 7.4. Integrating with SCM Tools
  - 7.5. Checklist
- 8. Documentation Environments
  - 8.1. Technical Documentation
    - 8.1.1. Is Documentation a Separate Product?
    - 8.1.2. Writing Documentation Is Like Writing Code
  - 8.2. Documents and SCM
  - 8.3. File Formats for Documentation
    - 8.3.1. File Formats for Customers
      - 8.3.1.1. HTML
      - 8.3.1.2. PostScript
      - 8.3.1.3. PDF
  - 8.4. Documentation Environments
    - 8.4.1. Raw Text
    - 8.4.2. FrameMaker
    - 8.4.3. XML: DocBook and OpenOffice
      - 8.4.3.1. DocBook
      - 8.4.3.2. The tools used to write this book
      - 8.4.3.3. OpenOffice
    - 8.4.4. Microsoft Word
  - 8.5. More File Formats
  - 8.6. Automated Production of Documentation
  - 8.7. Bad Ideas for Documentation
    - 8.7.1. Releasing the Documentation Separately
    - 8.7.2. Ransom-Note Cut and Paste
    - 8.7.3. Old Versions That Never Die
    - 8.7.4. Funky Filenames
    - 8.7.5. Screenshots
  - 8.8. Internal Project Documentation
  - 8.9. Checklist
- 9. Releasing Products
  - 9.1. Overview
  - 9.2. Before the Release
    - 9.2.1. System Requirements
    - 9.2.2. Build Numbers
    - 9.2.3. Release Numbering
    - 9.2.4. Release Information
    - 9.2.5. Upgrading
    - 9.2.6. Legal Licenses
    - 9.2.7. License Keys
    - 9.2.8. Securing Your Releases
    - 9.2.9. Quick Fixes and Engineering Specials
  - 9.3. Creating the Release
    - 9.3.1. Automated Releases
    - 9.3.2. Automating Release Information
    - 9.3.3. Developers as Customers
  - 9.4. Packaging Formats
    - 9.4.1. Unix
    - 9.4.2. Windows
  - 9.5. Installation Tools
    - 9.5.1. Requirements
      - 9.5.1.1. Tools
      - 9.5.1.2. Installers
    - 9.5.2. Unix
      - 9.5.2.1. Source code and binaries
      - 9.5.2.2. RPM package manager
      - 9.5.2.3. apt
      - 9.5.2.4. CPAN
    - 9.5.3. Windows
      - 9.5.3.1. Windows Installer
      - 9.5.3.2. InstallShield
      - 9.5.3.3. InstallAnywhere
      - 9.5.3.4. Wise for Windows
      - 9.5.3.5. InnoSetup
      - 9.5.3.6. NSIS
  - 9.6. Installation IrritationsShip Happens!
  - 9.7. After the Release
  - 9.8. Checklist
- 10. Maintenance
  - 10.1. Maintaining an Environment
    - 10.1.1. Migrating Your Data
  - 10.2. What Is Product Maintenance?
    - 10.2.1. Developing for Easier Maintenance
  - 10.3. Product Maintenance Tasks
    - 10.3.1. Understanding Code
    - 10.3.2. Reproducing a Build
    - 10.3.3. Handling Product Name Changes
    - 10.3.4. Handling Company Name Changes
    - 10.3.5. Handling Copyright Date Changes
  - 10.4. Product Maintenance and Development Environments
    - 10.4.1. SCM
    - 10.4.2. Building
    - 10.4.3. Testing
    - 10.4.4. Bug Tracking
    - 10.4.5. Documentation
    - 10.4.6. People and Politics
  - 10.5. Cleaning Up Your Environment
  - 10.6. Checklist
- 11. Project Communication
  - 11.1. Tools for Communication
  - 11.2. A Project Web Site
    - 11.2.1. Access Control
  - 11.3. Different Areas for the Project Web Site
    - 11.3.1. Home Page
    - 11.3.2. Getting Started
    - 11.3.3. Specifications
    - 11.3.4. SCM
    - 11.3.5. Building
    - 11.3.6. Testing
    - 11.3.7. Bug Tracking
    - 11.3.8. Documentation
    - 11.3.9. Releases
    - 11.3.10. Maintenance
    - 11.3.11. Support
    - 11.3.12. Project Management
    - 11.3.13. About the Web Site
  - 11.4. Creating the Web Site
    - 11.4.1. Static Web Pages
    - 11.4.2. Dynamic Web Pages
    - 11.4.3. Indexing and Searching
  - 11.5. Avoiding Content Rot
- 12. Politics and People
  - 12.1. The Role of the Toolsmith
    - 12.1.1. How to Choose a Toolsmith
  - 12.2. When Good Projects Go Bad
  - 12.3. Awkward People
  - 12.4. Twisted Communications
  - 12.5. Commit Rights
  - 12.6. Automation Discipline
  - 12.7. What Do Developers Really Want?
  - 12.8. An Upbeat Ending
- A. How Tools Scale
  - A.1. Scaling of Compilers
    - A.1.1. How the Compiler gcc Scales
      - A.1.1.1. Number of source files
      - A.1.1.2. Number of functions
      - A.1.1.3. Number of libraries
      - A.1.1.4. Number of included files
  - A.2. Scaling of Build Tools
    - A.2.1. Comparing Recursive and Included make
- B. Resources
  - B.1. Online
    - B.1.1. Content
    - B.1.2. Discussions
    - B.1.3. Directories
  - B.2. Magazines
  - B.3. Books
    - B.3.1. Automation and General Tools
    - B.3.2. Software Configuration Management
    - B.3.3. Building Software
    - B.3.4. Testing Software
    - B.3.5. Tracking Bugs
    - B.3.6. Documentation Environments
    - B.3.7. Releasing Products
    - B.3.8. Maintenance
    - B.3.9. Politics and People
    - B.3.10. Developing Software
    - B.3.11. General Design
  - B.4. Conferences
  - B.5. University and College Courses
- Index
- About the Author
- Colophon
- SPECIAL OFFER: Upgrade this ebook with OReilly