Unified and Holistic Approach

You can only able call yourself senior programmer if you are spend more minute in meeting as in write code.

—DevOps Borat1

This chapter will discuss a unified and holistic approach to software engineering. We’ll start with a discussion of concepts, particularly nonfunctional requirements. Then we’ll discuss one of the main dangers for collaboration between development and operations in more detail. Called a conceptual deficit, this can cause a discrepancy between business needs, project results, and expectations of operations.

With DevOps, development and operations do emancipate themselves and accept responsibilities of management, particularly planning and coordination. This chapter presents some background ...

Get DevOps for Developers now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.