Writings

< back to TOC

SECT

Story Driven Requirements

ABC of Decomposition
Aquire: Context. Question the Subject of your Attention (subject matter). Breakdown: See the blueprint, patterns, parts. Chunkify: Make coherant chunks, steps, modules. Digest: internalize possible creative building blocks, or discard.

Example Driven Design

SPIKE
Short Practical Iinvestigative Knowledge (Kleenex) Experiments

Code Driven Development

CODE
Component Orchestration Detailed Explicitly

How?

lerina design recipe

L. LIST Examples, Key demo usage. (docstring, usage with results) E. EXPRESS Expected Types. (1st line Type contract) R. REVEAL Header signature. (def name parameters) I. INSERT Informative Description. (purpose, help text) N. Nest Comment outline and NURTURE Body. (Neat and Nimble code) A. ATTEST Demo usage passes. (run doctest/unit test)

Nurture Neat and Nimble code

Capture the intent of an action
- Pseudocode should describe the what - Comments should describe the why - Code should describe the how

dual-nature:

placeholder for the how (code)
prelude to the why (comment)

Sketching with Pseudocode:

FIRST PASS  -> Comment section
Second Pass -> Comment or delete
third pass  -> Placeholder for code

Test Driven Delivery

Testcases

CULT

Conceptual structure components decomposition

Usage walkthrough

Logic learning Loop

Trac record

“I don’t Code in order to have clients, I have clients in order to Code.” __ lerina, in the style of Ayn Rand (Fountainhead)