+--------------------------------------------------------------+
| SNAKEPIT INDUSTRIES |
| BUILD LOGS |
+--------------------------------------------------------------+
root@snakepit:~/archive# ls -lah ./buildlogs/
---------------------------------------------------------------
ARCHIVE STATUS : OPEN
ACTIVE LOGS : 0
FAILED BUILDS : CLASSIFIED AS "LEARNING"
MAGIC SMOKE : CURRENTLY CONTAINED
---------------------------------------------------------------
ABOUT THIS DIRECTORY
Build logs document the actual development process.
Not merely what eventually worked.
Expect:
> INITIAL CONCEPTS
> HARDWARE CONFIGURATIONS
> SOFTWARE REVISIONS
> TEST RESULTS
> FAILURES
> REPAIRS
> MODIFICATIONS
> LESSONS LEARNED
> THINGS WE SHOULD HAVE READ BEFORE STARTING
---------------------------------------------------------------
BUILD LOG INDEX
No public build logs currently indexed.
Future logs may include:
[DEV] CHEZDEELISE
[DEV] XOPR
[DEV] SONAR
[DEV] NIGHTRIDER
[DEV] LAB INFRASTRUCTURE
[DEV] HARDWARE RESTORATION
[DEV] MISCELLANEOUS BAD IDEAS
---------------------------------------------------------------
root@snakepit:~/archive# cat buildlogs/FORMAT.txt
BUILD LOG FORMAT
PROJECT:
DATE:
REVISION:
STATUS:
OBJECTIVE
What are we trying to accomplish?
CONFIGURATION
What hardware / software are we using?
PROCEDURE
What did we do?
RESULT
What actually happened?
FAILURES
What did not happen according to plan?
CAUSE
What do we think caused it?
LESSONS
What did we learn?
NEXT ACTION
What are we doing differently next time?
---------------------------------------------------------------
root@snakepit:~/archive# ./build --project test
BUILD STARTED...
OBJECTIVE ............ MAKE THING WORK
CONFIGURATION ........ QUESTIONABLE
DOCUMENTATION ........ SKIMMED
CONFIDENCE ........... HIGH
TESTING...
RESULT ............... THING DID NOT WORK
DAMAGE ............... MINIMAL
LESSON ............... EXPENSIVE
NEXT ACTION:
READ THE DAMN DATASHEET.
---------------------------------------------------------------
FAILURE CLASSIFICATION
[F0] EXPECTED FAILURE
Normal experimentation.
[F1] CONFIGURATION ERROR
The machine did exactly what we told it to do.
[F2] HARDWARE FAILURE
Component no longer wishes to participate.
[F3] SOFTWARE FAILURE
Works on somebody else's machine.
[F4] OPERATOR ERROR
Problem located between chair and keyboard.
[F5] MAGIC SMOKE EVENT
Investigation required.
[F?] UNEXPLAINED
Interesting.
---------------------------------------------------------------
root@snakepit:~/archive# ./diagnose --failure F4
ANALYZING...
USER ................. PRESENT
MANUAL ................ PRESENT
MANUAL READ ........... NO
CAUSE IDENTIFIED.
root@snakepit:~/archive# _
---------------------------------------------------------------
BUILD PHILOSOPHY
Failure is data.
Successful failures teach something.
Unsuccessful failures merely make a mess.
Record both.
A working prototype without notes is a future mystery.
A broken prototype with good notes is research.
---------------------------------------------------------------
root@snakepit:~/archive# ./release --version final
ERROR:
INVALID VERSION NAME.
root@snakepit:~/archive# ./release --version final_REAL
ERROR:
WE HAVE BEEN THROUGH THIS.