- Preface
- Acknowledgments
- About the Author
- Navigation by Interest
- Chapter 1 – Agile Software Development
- Chapter 2 – 79 years of software development
-
Chapter 3 – Ethics, practices, and good habits of programmers
- The Programmer’s Oath (Robert C. Martin, 2015)
- The Foundation of Good Code (Dave Farley’s Criteria)
- Good Habits for Software Developers
- The Relevance of Patterns, and Refactoring
- Technical debt
- Dysfunction Maps: Ethics, Craft, and Responsibility
- The rational conclusion
- Why Ethics Matters - A Personal Reflection
- Clarifying SOLID: SRP, OCP, and DIP (the ones we argue about most)
- A Personal Success Story: How Practice Changed My Mindset and My Team
-
Chapter 4 – Test driven development
- The Mechanics of TDD
- TDD, and Continuous Integration (CI)
- Dysfunction Maps: Practicing TDD in the Real World
- Behavior Driven Development (BDD)
- Acceptance Test Driven Development (ATDD)
- Who Owns the Tests?
- Final Thought
- Getting TDD Wrong: The Myth of “Just Write the Test First”
- Executive Summaries & Cheat Sheets
-
Chapter 5 – Useful goals in software development teams
- What is Value?
- Experimentation and Prototyping: The Right Way to Explore
- Work Breakdown & User Stories, Plan for Outcomes, Not Output
- Build the Right Thing
- Flow Efficiency vs Resource Efficiency
- Continuous Integration
- Developer Morale: The Human Core of Software
- Dysfunction Maps: Useful Goals and Flow
- Conclusion: Useful Goals Are User-Centric, Change-Ready, and Team-Aligned
- Chapter 6 – Curiosity as a Catalyst for Innovation
-
Chapter 7: Adaptive Intelligence, and the Courage to Change
- Understanding AQ in a Technical Context
- Courage: The Enabler of Adaptation
- A Brief History and Importance of DORA
- Adaptive Intelligence Meets DORA, and XP: Embodied Agility vs. Dysfunction
- Practices That Develop Adaptive Intelligence
- Adaptive Intelligence in Planning and Predictability
- Leading with AQ in Mind
- The Strategic Advantage of AQ
-
Chapter 8: Psychological Safety as a Strategic Asset
- What Psychological Safety Is, and What It Isn’t
- The Cost of Silence
- Creating Psychological Safety in Tech Teams
- Team Rituals That Reinforce Safety
- Psychological Safety, and DORA Metrics
- Leading with Safety in Mind
- Psychological Safety and Legacy Systems
- Dysfunction Maps: Psychological Safety in Practice
- Safety First - Not Last
-
Chapter 9: Metrics That Matter: From DORA to Morale
- The Power, and Limits of DORA Metrics
- Morale as an Early Indicator
- Triangulating Metrics, and Culture
- Anti-Patterns to Avoid
- Practices That Encourage Healthy Use of Metrics
- Leading with Curiosity, Not Control
- The Rugged Manifesto, and Sustainable Effectiveness
- Metrics as Mirrors, Not Weapons
- Dysfunction Maps: Metrics and Morale
-
Chapter 10: From Silos to Synergy: Leading Beyond Department Walls
- The Hidden Cost of Silos
- Conway’s Law, and the Architecture of Communication
- From Cross-Functional to Truly Integrated
- Team Topologies, and Stream-Aligned Teams
- Collaboration Rituals That Drive Synergy
- Leadership Practices for Integration
- Beyond Structure: Toward a Culture of We
- Dysfunction Maps: Breaking Silos
- Chapter 11: Empowerment Is a Design Problem
- Chapter 12: Co-Located Teams Across Company Boundaries – Challenges, and Recommendations
- Chapter 13: Conclusion - Principles Over Process
- References
-
Appendix A – Tools
- Diagnosing Agile Dysfunctions from Chapter 1
- Dysfunction Maps: Staying Grounded in History from Chapter 2
- Dysfunction Maps: Ethics, Craft, and Responsibility from Chapter 3
- Why pairing always wins from Chapter 4
- 4 Layer test archictecture and owners from Chapter 4
- Dysfunction Maps: Practicing TDD in the Real World from Chapter 4
- Dysfunction Maps: Useful Goals and Flow from Chapter 5
- Dysfunction Maps: Curiosity and Learning from Chapter 6
- DORA vs. Traditional Metrics from Chapter 7
- Embodied agile vs. agile dysfunctions from Chapter 7
- Adaptive Intelligence, XP Principles & DORA Outcomes
- Dysfunction Maps: Psychological Safety in Practice from Chapter 8
- Dysfunction Maps: Metrics and Morale from Chapter 9
- Dysfunction Maps: Breaking Silos from Chapter 10
- Dysfunction Maps: Designing for Empowerment from Chapter 11
- Chapter 12 - Risk Assessment Matrix for Outsourcing
- Dysfunction Maps: Cross-Company Collaboration from Chapter 12
- Dysfunction Maps: Sustaining Principles from Chapter 13
-
Appendix B – ATDD Example
- Repository Root — Orientation
- Domain Module — Business Rules First
- Application Module — Delivery, Not Business Logic
- System Architecture
- Acceptance Module — Executable Specifications
- UI Acceptance Module — End-to-End Confidence
-
Frontend (
ng-frontend) — Independent, Testable, Replaceable - Continuous Integration Pipeline
- Why These Artifacts Matter Together
- Closing Note
- Evidence-Driven Progress, Metrics, and Organizational Impact
- Acceptance Tests as the Foundation of Meaningful Metrics
- Alignment with DORA Metrics
- Example: Acceptance-Test–Based Progress Report
- Transparency Without Blame — Reinforced by Evidence
- Long-Term System Resilience
- Opportunities by Organizational Level
- No Heroes Required
- Appendix C - Glossary of Key Terms
- Appendix D – FAQ and Role-Specific Guidance
-
Appendix E – Alignment Matrix
- Behaviors, Principles, Value – Cheat sheet
-
Detailed cheat sheets
- Curiosity
- Courage
- Humility
- Ethical Responsibility
- Code That Works
- Code That Is Easy to Change
- Stakeholder Awareness
- Continuous Integration (CI) & Trunk-Based Development
- Test-Driven Development (TDD)
- Shared Ownership
- Psychological Safety
- Flow Over Process
- User-Centric Goal Setting
- Adaptive Intelligence (AQ)
- Empowerment & Autonomy
- Cross-Functional Collaboration
- Healthy Use of Metrics
- Appendix F - How to break Learned Helplessness in Big, Mixed Teams
The Effective Software Engineer
Ethics, Flow, and Organizational Intelligence in Modern Software Development
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.00Author earns
$23.20Buying multiple copies for your team? See below for a discount!
PDF
EPUB
WEB
0
Pages
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.
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 Lower Austria that partners with clients to design and build modern software solutions.
Contents
Table of Contents
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.