Leanpub Header

Skip to main content
Go to Leanpub.com

The Effective Software Engineer

Ethics, Flow, and Organizational Intelligence in Modern Software Development

Stefan Ellersdorfer

What makes a software engineer truly effective? Beyond writing code, effectiveness comes from ethics, sustainable practices, collaboration, and the courage to adapt. The Effective Software Engineer guides you from clean coding habits to organizational empowerment, bridging the gap between developers and leaders.

Minimum price

$19.00

$29.00

You pay

$29.00

Author earns

$23.20
$

...Or Buy With Credits!

You can get credits with a paid monthly or annual Reader Membership, or you can buy them here.

Buying multiple copies for your team? See below for a discount!

PDF
EPUB
WEB
311
Pages
About

About

About the Book

The Effective Software Engineer is a practical guide to building software that truly works — and to building teams and organizations that can sustain that success. It bridges the gap between coding craftsmanship and organizational leadership, showing how individual habits, team practices, and management structures all contribute to effective software delivery.


The book begins with the ethics, practices, and good habits of professional programmers, then moves into Test-Driven Development (TDD), sustainable delivery, and the principles of writing code that is both reliable and easy to change. From there, it expands outward to the goals of software development teams, including how to define meaningful outcomes, break down work, and align around flow and morale.


For leaders, the book provides insights into creating an environment where developers thrive. Topics include curiosity and adaptive intelligence (AQ), psychological safety, empowerment as a systems design challenge, and using DORA metrics to drive organizational effectiveness. Later chapters explore cross-company collaboration and the realities of distributed and outsourced teams, offering strategies for keeping alignment and trust strong across boundaries.


With references to the wisdom of Kent Beck, Dave Farley, Daniel Terhorst-North, Robert C. Martin, Martin Fowler, and others, the book connects timeless principles of software engineering with modern practices of DevOps, Agile, and continuous delivery.


Whether you are a developer striving for mastery, a team lead seeking effectiveness, or an executive aiming to build sustainable digital organizations, this book offers a roadmap for software that is ethical, adaptable, and effective — at every level.

Share this book

Categories

Software Engineering

Feedback

Email the Author

Team Discounts

Team Discounts

Get a team discount on this book!

  • Up to 3 members

    Minimum price
    $47.00
    Suggested price
    $72.00

  • Up to 5 members

    Minimum price
    $76.00
    Suggested price
    $116.00

  • Up to 10 members

    Minimum price
    $133.00
    Suggested price
    $203.00

  • Up to 15 members

    Minimum price
    $190.00
    Suggested price
    $290.00

  • Up to 25 members

    Minimum price
    $285.00
    Suggested price
    $435.00

Author

About the Author

Stefan Ellersdorfer

Stefan Ellersdorfer has been a professional software engineer since 2000 and an international consultant for just as long. He is one of the co-founders and managing director of Smarter Software, a consultancy based in Austria that partners with clients to design and build modern software solutions.

Find me also on Patreon and Medium.

Contents

Table of Contents

Preface

Acknowledgments

About the Author

  1. Why I wrote this book

Navigation by Interest

  1. Audience Groups Navigation
  2. Thematic Coverage Across Chapters
  3. Conceptual Timeline Through Chapters
  4. Core Principles Across Chapters

Chapter 1 – Agile Software Development

  1. Agile
  2. A Brief History of Agile
  3. Ticket or User Story?
  4. What Real User Stories look like
  5. Scope creep
  6. Practices and values of Agile software development
  7. Why “the Right Side” Still Matters
  8. What is the Agile Fluency Model?
  9. From Estimation to Understanding: User Stories, and ATDD
  10. Estimation Without Understanding
  11. ATDD: Shifting from Guessing to Knowing
  12. ATDD, and Estimation
  13. Ethics and Responsibility
  14. Diagnosing Agile Dysfunctions
  15. Top Management Dysfunctions
  16. Middle Management Dysfunctions
  17. Software Development Team Dysfunctions
  18. Using This Diagnostic
  19. Agile maturity checklist

Chapter 2 – 79 years of software development

  1. The Origins of Code
  2. Cornerstones in the History of Software
  3. What is Object Orientation?
  4. The Illusion of Change in Software
  5. What Did Change Then?
  6. The Burden of Misinformation
  7. A Call for Responsibility
  8. The Forgotten Craft
  9. Bridging the Knowledge Gap
  10. Dysfunction Maps: Staying Grounded in Software History
  11. Top Management
  12. Middle Management
  13. Software Development Team

Chapter 3 – Ethics, practices, and good habits of programmers

  1. The Programmer’s Oath (Robert C. Martin, 2015)
  2. The Foundation of Good Code (Dave Farley’s Criteria)
  3. The Code Works
  4. The Code Is Easy to Change
  5. Good Habits for Software Developers
  6. Stakeholder Awareness
  7. The Relevance of Patterns, and Refactoring
  8. Technical debt
  9. Dysfunction Maps: Ethics, Craft, and Responsibility
  10. Top Management
  11. Middle Management
  12. Software Development Team
  13. The rational conclusion
  14. Why Ethics Matters - A Personal Reflection
  15. Ethical Responsibility Is Personal
  16. Process vs. Principle: The Trunk-Based Development Paradox
  17. The Real Root of Ethical Failure
  18. The Way Forward: Mastery and Communication
  19. Clarifying SOLID: SRP, OCP, and DIP (the ones we argue about most)
  20. SRP - Single Responsibility Principle
  21. OCP - Open/Closed Principle
  22. DIP - Dependency Inversion Principle
  23. How the three interact (and how tests keep you honest)
  24. A Personal Success Story: How Practice Changed My Mindset and My Team
  25. First, I had to change my own perspective.
  26. TDD: From Practice to Habit
  27. Architecture Principles and Object Orientation
  28. Coupling and Cohesion: Old Wisdom, Fresh Understanding
  29. Know What You Want
  30. Bringing It All Together

Chapter 4 – Test driven development

  1. The Mechanics of TDD
  2. The Purpose of TDD
  3. The Role of AI in TDD
  4. AI in Software Development
  5. TDD, and Continuous Integration (CI)
  6. Pair Programming vs. Asynchronous Code Review
  7. Dysfunction Maps: Practicing TDD in the Real World
  8. Top Management
  9. Middle Management
  10. Software Development Team
  11. Results of Test Driven Development
  12. Training, and Mastery
  13. Consequences of TDD
  14. Behavior Driven Development (BDD)
  15. Explanation
  16. What vs. How
  17. Consequences
  18. Acceptance Test Driven Development (ATDD)
  19. Explanation
  20. Consequences
  21. Who Owns the Tests?
  22. A Shared Responsibility, Not a Silo
  23. Test Ownership Across Roles
  24. Ownership by Layer (in 4-Layer Architecture)
  25. Why Shared Ownership Matters
  26. Final Thought
  27. Getting TDD Wrong: The Myth of “Just Write the Test First”
  28. The Real Mechanics: Writing in the Test First
  29. TDD as a Conversation, Not a Command
  30. Why Algorithmic Problems Aren’t a Special Case
  31. TDD Is About Clarity, Not Coverage
  32. A More Accurate Practice
  33. Summary: Don’t Write the Test First - Write with the Test
  34. How to Structure a Test
  35. Executive Summaries & Cheat Sheets
  36. For Managers: What To Know About TDD
  37. For Developers: Daily Habit Checklist

Chapter 5 – Useful goals in software development teams

  1. What is Value?
  2. Three Primary Forms of Value
  3. The Danger of Proxy Metrics
  4. Experimentation and Prototyping: The Right Way to Explore
  5. The Role of Prototypes in Learning
  6. The Myth of the Throwaway Prototype
  7. A Prototype Is Still Software
  8. Fail Fast ≠ Build Sloppy
  9. A Prototype Is an Experiment in Value, Not an Experiment in Sloppiness
  10. The Minimal Reliable Slice
  11. In Short
  12. Work Breakdown & User Stories, Plan for Outcomes, Not Output
  13. Value-Oriented Work Breakdown
  14. Vertical vs. Horizontal Slices
  15. Slicing Heuristics
  16. Defining User Stories: Clarify the What, Delay the How
  17. Build the Right Thing
  18. Executable Requirements
  19. ATDD as Truth
  20. Flow Efficiency vs Resource Efficiency
  21. How Process Hurts Flow
  22. Adding People: Scale Decisions, Not Headcount
  23. Flow Instead of Process: Optimize for Value, Not Activity
  24. Continuous Integration
  25. Why CI Matters
  26. CI as Architectural Pressure
  27. Easy Changes: Optimize for Changeability
  28. Organizational responsiveness
  29. Developer Morale: The Human Core of Software
  30. Why Morale Matters
  31. Sustainable Pace
  32. Psychological Safety and Trust
  33. Dysfunction Maps: Useful Goals and Flow
  34. Top Management
  35. Middle Management
  36. Software Development Team
  37. Conclusion: Useful Goals Are User-Centric, Change-Ready, and Team-Aligned

Chapter 6 – Curiosity as a Catalyst for Innovation

  1. The Curiosity Deficit in Organizations
  2. Why Curiosity Matters in Tech
  3. Curiosity in Tools and Frameworks
  4. Leadership Practices to Encourage Curiosity
  5. Practices, and Rituals to Support Curiosity
  6. Dysfunction Maps: Curiosity and Learning
  7. Top Management
  8. Middle Management
  9. Software Development Team
  10. WOOP
  11. Following a Plan: From Rigidity to Adaptive Planning with WOOP
  12. WOOP for Plan People on the Agile Fluency Journey

Chapter 7: Adaptive Intelligence, and the Courage to Change

  1. Understanding AQ in a Technical Context
  2. Courage: The Enabler of Adaptation
  3. A Brief History and Importance of DORA
  4. Adaptive Intelligence Meets DORA, and XP: Embodied Agility vs. Dysfunction
  5. Practices That Develop Adaptive Intelligence
  6. Adaptive Intelligence in Planning and Predictability
  7. Leading with AQ in Mind
  8. The Strategic Advantage of AQ

Chapter 8: Psychological Safety as a Strategic Asset

  1. What Psychological Safety Is, and What It Isn’t
  2. The Cost of Silence
  3. Creating Psychological Safety in Tech Teams
  4. Team Rituals That Reinforce Safety
  5. Psychological Safety, and DORA Metrics
  6. Leading with Safety in Mind
  7. Psychological Safety and Legacy Systems
  8. Have you ever thought about?
  9. Dysfunction Maps: Psychological Safety in Practice
  10. Top Management
  11. Middle Management
  12. Software Development Team
  13. Safety First - Not Last

Chapter 9: Metrics That Matter: From DORA to Morale

  1. The Power, and Limits of DORA Metrics
  2. Morale as an Early Indicator
  3. Triangulating Metrics, and Culture
  4. Anti-Patterns to Avoid
  5. Practices That Encourage Healthy Use of Metrics
  6. Leading with Curiosity, Not Control
  7. The Rugged Manifesto, and Sustainable Effectiveness
  8. Metrics as Mirrors, Not Weapons
  9. Dysfunction Maps: Metrics and Morale
  10. Top Management
  11. Middle Management
  12. Software Development Team

Chapter 10: From Silos to Synergy: Leading Beyond Department Walls

  1. The Hidden Cost of Silos
  2. Conway’s Law, and the Architecture of Communication
  3. From Cross-Functional to Truly Integrated
  4. Team Topologies, and Stream-Aligned Teams
  5. Collaboration Rituals That Drive Synergy
  6. Leadership Practices for Integration
  7. Beyond Structure: Toward a Culture of We
  8. Dysfunction Maps: Breaking Silos
  9. Top Management
  10. Middle Management
  11. Software Development Team

Chapter 11: Empowerment Is a Design Problem

  1. Why Empowerment Fails
  2. Designing for Empowerment
  3. Practices That Enable Real Autonomy
  4. Leadership Behaviors That Support Empowerment
  5. Empowerment, and Organizational Effectiveness
  6. Empowerment Is a Loop, Not a Lever
  7. Dysfunction Maps: Designing for Empowerment
  8. Top Management
  9. Middle Management
  10. Software Development Team

Chapter 12: Co-Located Teams Across Company Boundaries – Challenges, and Recommendations

  1. The Illusion of Virtual Co-Location
  2. Language as a Barrier to Shared Understanding
  3. Strategic Work Requires Strategic Proximity
  4. The Role of Internal Ambassadors
  5. The True Cost of Misunderstanding
  6. Risk Assessment Matrix
  7. Conclusion
  8. Dysfunction Maps: Cross-Company Collaboration
  9. Top Management
  10. Middle Management
  11. Software Development Team

Chapter 13: Conclusion - Principles Over Process

  1. What We’ve Learned
  2. The Path Forward
  3. The Effective Engineer, the Empowered Team
  4. Dysfunction Maps: Sustaining Principles
  5. Top Management
  6. Middle Management
  7. Software Development Team

References

  1. Agile Foundations, and Values
  2. Software Craftsmanship, and Professionalism
  3. Testing, TDD, and BDD
  4. Continuous Delivery, and DevOps
  5. Design, and Architecture
  6. Team Topologies, Flow, and Culture
  7. Human Dynamics, Leadership, and Motivation
  8. Other Notable Influences

Appendix A – Tools

  1. Diagnosing Agile Dysfunctions from Chapter 1
  2. Top Management Dysfunctions
  3. Middle Management Dysfunctions
  4. Software Development Team Dysfunctions
  5. Agile maturity checklist
  6. Dysfunction Maps: Staying Grounded in History from Chapter 2
  7. Top Management
  8. Middle Management
  9. Software Development Team
  10. Dysfunction Maps: Ethics, Craft, and Responsibility from Chapter 3
  11. Top Management
  12. Middle Management
  13. Software Development Team
  14. Why pairing always wins from Chapter 4
  15. 4 Layer test archictecture and owners from Chapter 4
  16. Dysfunction Maps: Practicing TDD in the Real World from Chapter 4
  17. Top Management
  18. Middle Management
  19. Software Development Team
  20. Dysfunction Maps: Useful Goals and Flow from Chapter 5
  21. Top Management
  22. Middle Management
  23. Software Development Team
  24. Dysfunction Maps: Curiosity and Learning from Chapter 6
  25. Top Management
  26. Middle Management
  27. Software Development Team
  28. DORA vs. Traditional Metrics from Chapter 7
  29. Embodied agile vs. agile dysfunctions from Chapter 7
  30. Adaptive Intelligence, XP Principles & DORA Outcomes
  31. Top Management Dysfunctions
  32. Middle Management Dysfunctions
  33. Team Dysfunctions
  34. Dysfunction Maps: Psychological Safety in Practice from Chapter 8
  35. Top Management
  36. Middle Management
  37. Software Development Team
  38. Dysfunction Maps: Metrics and Morale from Chapter 9
  39. Top Management
  40. Middle Management
  41. Software Development Team
  42. Dysfunction Maps: Breaking Silos from Chapter 10
  43. Top Management
  44. Middle Management
  45. Software Development Team
  46. Dysfunction Maps: Designing for Empowerment from Chapter 11
  47. Top Management
  48. Middle Management
  49. Software Development Team
  50. Chapter 12 - Risk Assessment Matrix for Outsourcing
  51. Dysfunction Maps: Cross-Company Collaboration from Chapter 12
  52. Top Management
  53. Middle Management
  54. Software Development Team
  55. Dysfunction Maps: Sustaining Principles from Chapter 13
  56. Top Management
  57. Middle Management
  58. Software Development Team

Appendix B – ATDD Example

  1. Repository Root — Orientation
  2. Domain Module — Business Rules First
  3. Purpose
  4. Location
  5. Tests
  6. Application Module — Delivery, Not Business Logic
  7. Purpose
  8. Location
  9. Tests
  10. System Architecture
  11. Acceptance Module — Executable Specifications
  12. Layer 1 - The executable specification
  13. Layer 2 - DSL - domain specific language
  14. Layer 3 - The protocol drivers
  15. Layer 4 - The system under test
  16. Purpose
  17. Location
  18. AbstractAssetAcceptanceTest
  19. DSL
  20. UI Acceptance Module — End-to-End Confidence
  21. Purpose
  22. Location
  23. Frontend (ng-frontend) — Independent, Testable, Replaceable
  24. Location
  25. Continuous Integration Pipeline
  26. Location
  27. Commit Stage
  28. Acceptance Stage
  29. Why These Artifacts Matter Together
  30. Closing Note
  31. Evidence-Driven Progress, Metrics, and Organizational Impact
  32. Acceptance Tests as the Foundation of Meaningful Metrics
  33. Alignment with DORA Metrics
  34. Lead Time for Changes
  35. Deployment Frequency
  36. Change Failure Rate
  37. Mean Time to Restore (MTTR)
  38. Example: Acceptance-Test–Based Progress Report
  39. Table: Acceptance Summary per Build
  40. Transparency Without Blame — Reinforced by Evidence
  41. Long-Term System Resilience
  42. Opportunities by Organizational Level
  43. Software Development Teams
  44. Middle Management
  45. Top Management
  46. No Heroes Required
  47. Agile Development as Risk Management
  48. Quality Enables Speed — Never the Other Way Around
  49. The Habits That Actually Matter
  50. Sustainability Over Heroics

Appendix C - Glossary of Key Terms

Appendix D – FAQ and Role-Specific Guidance

  1. Frequently Asked Questions – FAQ
  2. For Managers
  3. For Developers
  4. Role-Specific Guidance (Appendix D)
  5. Advice for New Managers
  6. Advice for Senior Engineers
  7. Diversity & Inclusion: The Foundation of Resilient Teams

Appendix E – Alignment Matrix

  1. Behaviors, Principles, Value – Cheat sheet
  2. Detailed cheat sheets
  3. Curiosity
  4. Courage
  5. Humility
  6. Ethical Responsibility
  7. Code That Works
  8. Code That Is Easy to Change
  9. Stakeholder Awareness
  10. Continuous Integration (CI) & Trunk-Based Development
  11. Test-Driven Development (TDD)
  12. Shared Ownership
  13. Psychological Safety
  14. Flow Over Process
  15. User-Centric Goal Setting
  16. Adaptive Intelligence (AQ)
  17. Empowerment & Autonomy
  18. Cross-Functional Collaboration
  19. Healthy Use of Metrics

Appendix F - How to break Learned Helplessness in Big, Mixed Teams

  1. Shrink the surface of change
  2. Rebuild local agency (the antidote to helplessness)
  3. Use visible experiments instead of principles
  4. Normalize speaking up (micro safety rituals)
  5. Show progress with dual mirrors
  6. Anchor back to professional identity
  7. How to break Learned Helplessness in Big, Mixed Teams

The Leanpub 60 Day 100% Happiness Guarantee

Within 60 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.

Now, this is technically risky for us, since you'll have the book or course files either way. But we're so confident in our products and services, and in our authors and readers, that we're happy to offer a full money back guarantee for everything we sell.

You can only find out how good something is by trying it, and because of our 100% money back guarantee there's literally no risk to do so!

So, there's no reason not to click the Add to Cart button, is there?

See full terms...

Earn $8 on a $10 Purchase, and $16 on a $20 Purchase

We pay 80% royalties on purchases of $7.99 or more, and 80% royalties minus a 50 cent flat fee on purchases between $0.99 and $7.98. You earn $8 on a $10 sale, and $16 on a $20 sale. So, if we sell 5000 non-refunded copies of your book for $20, you'll earn $80,000.

(Yes, some authors have already earned much more than that on Leanpub.)

In fact, authors have earned over $14 million writing, publishing and selling on Leanpub.

Learn more about writing on Leanpub

Free Updates. DRM Free.

If you buy a Leanpub book, you get free updates for as long as the author updates the book! Many authors use Leanpub to publish their books in-progress, while they are writing them. All readers get free updates, regardless of when they bought the book or how much they paid (including free).

Most Leanpub books are available in PDF (for computers) and EPUB (for phones, tablets and Kindle). The formats that a book includes are shown at the top right corner of this page.

Finally, Leanpub books don't have any DRM copy-protection nonsense, so you can easily read them on any supported device.

Learn more about Leanpub's ebook formats and where to read them

Write and Publish on Leanpub

You can use Leanpub to easily write, publish and sell in-progress and completed ebooks and online courses!

Leanpub is a powerful platform for serious authors, combining a simple, elegant writing and publishing workflow with a store focused on selling in-progress ebooks.

Leanpub is a magical typewriter for authors: just write in plain text, and to publish your ebook, just click a button. (Or, if you are producing your ebook your own way, you can even upload your own PDF and/or EPUB files and then publish with one click!) It really is that easy.

Learn more about writing on Leanpub