Embed Size (px)
DESCRIPTION
During the rewrite of the Kephra Editor I documented the forkflow and now talked about the first time. Sure it goes a bit against hip things like test first and agile programming, but i think for a good reasons - since it follows the natural flow of ideas from mind to paper and has in focus the entire product not just the code.
Citation preview
полное́ ́
программирование́
complete
programming
меня зовут́
меня ́зовут
меня ́зовут
they call me
Doing, not Being
Doing, not Being
behaviourcan be changed
Not Like Him
Metro Station: I.P.Pavlov
The Dog Thing
Don't Be This Dog
Nor This Cat
Classic Waterfall
Agile
Agile
XP = Hacking?
Real Goal
CompleteProgram
Complete Program:
Docs, Codes, Tests, Configs,
Artwork, Gui
Complete Repo:
No DuplicationAll Metadocs
Also
I Write For:
Scientific Approach
Rough Steps:
DocsPrototypes
CodeTests
Steps:
DocsPrototypes
CodeTests
Docs:
Docs:
Plannig
Stages
Docs:
Condense thoughts
Means of Communication
Steps:
DocsPrototypes
CodeTests
Prototypes:
Prototypes:
Functional
Use Case
Steps:
DocsPrototypes
CodeTests
Code:
Code:
Dummy
Code:
Dummy
Feature Branch
Steps:
DocsPrototypes
CodeTests
Tests:
Tests:
not helping wellto define Problem
Tests:
After Thougts
Edge Cases
Tests:
Integrate into code
Full Text:bitbucket.org
/lichtkind/kephra
/doc/CompleteProgramming.pod
