# Spec Driven Development — Chapter 01 Memory: About the author
- **Stage**: Complete
- **Next Step**: None (frozen). Next chapter is Chapter 02 (book's section 0).
- **Reading Span**: PDF pages 11–12
- **Source Text**: /library/Spec Driven Development/Chapter-01-About-the-author/Chapter-01-source-text.md (the chapter's own words; read instead of the PDF)
- **Full Record**: /library/Spec Driven Development/Chapter-01-About-the-author/Chapter-01-chapter-notes.md (read only if needed)
- **Last Updated**: 2026-10-01

## Carried-in Context (from earlier chapters)
- First chapter — nothing carried in. (Numbering note: the unnumbered author introduction is Chapter 1 in this log; the book's section 0 is Chapter 2.)

## This Chapter
- **Core Question**: How does the author use his professional history to frame the book?
- **Core Thesis**: Ködel presents his experience across software delivery methods and long-term product ownership as the reason to examine his proposed development approach.
- **Key Concepts**: Lifecycle ownership; methodology experience; credibility versus proof.
- **Notable Arguments / Evidence Limits**: Self-reported experience with a VB6 ERP, high-stakes systems (Basel II), mobile apps, and long-term operation of *Meu Cronograma Capilar*. These establish perspective but do not compare methods independently.
- **Action Item**: For one software-method claim this week, distinguish the speaker's experience from evidence the method works in your situation.

## Reader State
- **Pending Questions**: None
- **Reader's Answers (paraphrase)**: Recalled the ERP, Basel II, mobile apps, and personal app; recognized his exposure to heavyweight and agile methods informs his perspective.
- **Misconceptions / Feedback Given**: Reader trusts the author and wants to see the method; feedback distinguished credibility from evidence of broad effectiveness.
- **Personal Threads**: None

## Open Threads
- Keep testing experience-as-credibility against actual evidence as the method is presented.