👨‍💻
Software Engineering
Clean Architecture
Clean Architecture
  • Overview
  • Foreword
  • Preface
  • Part 1
    • Introduction
    • 1: Design & Architecture
    • 2: A Tale of Two Values
  • Part 2: Programming Paradigms
    • 3: Paradigm Overview
    • 4: Structured Programming
    • 5: Object-Oriented Programming
    • 6: Functional Programming
  • Part 3: Design Principles
    • Intro
    • 7: Single Responsibility Principle
    • 8: Open-Closed Principle
  • Part 5: Architecture
    • 22: Clean Architecture
Powered by GitBook
On this page
  • 🔥 Programming Hell
  • ✅ Getting Software Right
  • 🤔 Why Get Software Right?
  1. Part 1

Introduction

🔥 Programming Hell

  • Have you experienced the impedance of bad code and rotten design?

  • Has the design of the systems you've worked on had a negative effect on the morale of the team? customers? managers?

  • Have you seen teams, departments, and companies brought down by the rotten structure & design of their software?

  • Far too common to fight your way through terrible software designs than to enjoy the pleasure of working with a good one.

✅ Getting Software Right

  • Getting something to "work" isn't that hard

  • Getting software right is hard.

  • Requires thought & insight that most don't take time to develop.

  • Requires discipline and dedication that most don't think they need.

  • Requires a passion for the craft and desire to be professional.

🤔 Why Get Software Right?

  • You don't need hordes of programmers to keep it working.

  • You don't need massive requirements docs and issue tracking systems.

  • You don't need global cube farms and 24/7 programming.

  • Requires a fraction of the human resources to create & maintain.

  • Changes are simple & rapid.

  • Defects are few & far between.

  • Effort is minimized & functionality is maximized.

PreviousPrefaceNext1: Design & Architecture

Last updated 25 days ago