"I just write code that works, theory comes later."
[WORK IN PROGRESS]
1. Implementation Driven Development, IDD for short, is a software development methodology. [1] [2]
1.1. The discipline is formal (as opposed to agile, i.e. informal).
1.2. The process is evolutionary (as opposed to e.g. iterative: the immediate difference being that evolutionary is ideally continuous, though it has milestones, too).
1.3. The aim is verified highest-quality software at the lowest cost!
2. Development starts with specification and proceeds top-down (logically, in practice with feedback loops) to implementation and eventually deployment.
2.1 All artefacts ("deliverables") must be runnable, starting with specifications.
2.2. All artefacts must satisfy the formal requirements of soundness, correctness and closure.
(TECH: Strive for *no bugs*, rather keep closure by wrapping *every hole* into an "exception" - that is a "todo" in documentation.)
...to be continued...
[1] A precursor is in the rationale accompanying my TicTacToe project (2007), where for the first time I have mentioned the idea and the name publicly.
[2] A concrete example is the progression of my experimental constructive logic solver (2024), see the revision history in particular.
[CREATED 2023-05-08 18:41 UTC+2]