--- title: "#47 Assertions and Design by Contract, Part-1" url: https://daily.dev/posts/47-assertions-and-design-by-contract-part-1-kerh6vsgk source_url: https://www.youtube.com/watch?v=cnEhFwo4u5g type: video:youtube source: "Quantum Leaps" published: 2026-05-31T07:45:33.454Z updated: 2026-05-31T07:55:56.637Z tags: ["c", "embedded"] reading_time: 13 upvotes: 0 comments: 0 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # #47 Assertions and Design by Contract, Part-1 **[Quantum Leaps](https://daily.dev/sources/quantum-leaps)** · 13 min read · 0 upvotes · 0 comments ## Summary An introduction to software assertions and Design by Contract (DBC) methodology in the context of embedded programming. Covers what assertions are, how the C standard assert facility works (with GCC demos), and the critical distinction between programming errors (bugs) and exceptional conditions. Explains why defensive programming hides bugs, while assertions act like fuses in electrical circuits — detecting failures loudly rather than masking them. DBC, pioneered by Bertrand Meyer, frames assertions as contractual obligations between software components validated automatically at runtime. Part 2 will cover applying assertions and DBC in embedded C/C++. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Similar posts on daily.dev - [assert\(\): A modern How To](https://daily.dev/posts/assert-a-modern-how-to-mky6fdnmw) · Hacker News · 0 upvotes · 0 comments --- Tags: [#c](https://daily.dev/tags/c), [#embedded](https://daily.dev/tags/embedded) [View this post on daily.dev](https://daily.dev/posts/47-assertions-and-design-by-contract-part-1-kerh6vsgk)