Learning
search
Ctrlk
  • Software Engineering Golden Treasury
  • Trail Map
  • Cachingchevron-right
  • Careerchevron-right
  • Computer Sciencechevron-right
  • devopschevron-right
  • General Paradigmschevron-right
    • CAP theorem
    • designing data-intensive applications summary
    • a-philosophy-of-software-design-notes
    • Aspect oriented Programming (AOP)
    • Best Practice
    • Cargo Cult
    • Clean Code
    • Coding reflections
    • Cognitive Complexity
    • Complexity
    • Conventions
    • Design discussions
    • Design
    • Edge Cases
    • Error Handling Checklist
    • Exceptions
    • Feature Flags/toggle
    • Functional requirements
    • Last Responsible Moment
    • Lock In
    • Named Arguments
    • Naming
    • Performance Fallacy
    • Quality
    • Redesign of a system
    • Resuse vs Decoupling
    • Rules for software designs
    • Sad Paths
    • Scaling Webservices
    • Scientific Method
    • stream-processing
    • Upstream and Downstream
    • Patternschevron-right
    • Architecturechevron-right
    • Design architecture aimschevron-right
    • READMEchevron-right
    • Patterns of Enterprise Application Architecturechevron-right
    • Principleschevron-right
    • programming-typeschevron-right
      • Coding to Contract/Interface
      • Links
      • Declarative vs Imperative Programming Languages
      • defensive-programming
      • Design by contract
      • Domain Specific Languages (DSL)
      • Event Driven
      • file-transfers
      • Logical Programming
      • Mutability
      • Self Healing
      • Simplicity
      • Type Driven Design
      • Value objects
      • Aspect Oriented Programming
      • Concurrent and Parallel Programmingchevron-right
      • Functional Programmingchevron-right
      • oop-designchevron-right
      • Reactive Programmingchevron-right
    • Projects and Software typeschevron-right
    • State Machineschevron-right
  • Otherchevron-right
  • Hardwarechevron-right
  • Integrationchevron-right
  • Languageschevron-right
  • Management & Workflowchevron-right
  • Networkschevron-right
  • Operating Systemschevron-right
  • Other Topicschevron-right
  • persistancechevron-right
  • Securitychevron-right
  • Testing, Maintainablity & Debuggingchevron-right
  • Version Control - Gitchevron-right
  • aichevron-right
gitbookPowered by GitBook
block-quoteOn this pagechevron-down
  1. General Paradigmschevron-right
  2. programming-types

Design by contract

  • https://en.wikipedia.org/wiki/Design_by_contractarrow-up-right

hashtag
TDD vs DbC

  • https://stackoverflow.com/questions/481312/why-is-design-by-contract-not-so-popular-compared-to-test-driven-development#:~:text=Like TDD%2C the contracts of,)%2C will execute the contractsarrow-up-right.

hashtag
Defensive Programming vs Design_by_contract

  • https://softwareengineering.stackexchange.com/questions/125399/differences-between-design-by-contract-and-defensive-programming#:~:text=Design by Contract and defensive programming are in some sense,the collaborators honor their contracts.&text=The difference is that the programmer doesn't make this checkarrow-up-right.

Previousdefensive-programmingchevron-leftNextDomain Specific Languages (DSL)chevron-right

Last updated 4 years ago

Was this helpful?

  • TDD vs DbC
  • Defensive Programming vs Design_by_contract

Was this helpful?