Coursera Flash Sale
40% Off Coursera Plus for 3 Months!
Grab it
Explore the concept of "doneness" in software engineering through this conference talk that examines what it truly means to complete software development tasks beyond simply checking code into a repository. Learn how primitive approaches to marking work as complete can lead to technical debt and unwieldy codebases, while discovering a comprehensive framework for software engineering completeness. Understand the difference between tactical fixes and strategic direction in achieving various levels of completion, including crucial aspects like code quality improvement, technical debt management, legacy code decommissioning, and refactoring practices. Examine a Software Engineering Completeness pyramid modeled after Maslow's Hierarchy of Needs, which illustrates different levels of change completion from unsustainable code hacking at the bottom to mature engineering practices that future-proof applications at higher tiers. Discover how these pyramid levels directly correlate to engineering competence and maturity, helping you assess and aspire to different levels of software expertise. Gain insights into how properly defined and executed "doneness" drives superior software engineering outcomes, promotes flexible software architecture, creates satisfied end users, and enables clear communication about project completion status, ultimately revealing the true cost of software ownership and maintenance.
