Started yesterday morning at 8am.
Early this morning.
Finished my 5 books of the father the son, and the Holy Spirit.
Walked to the tunnel and hitchhiked to the airport.
Shared the cold and fatigue with Lisa, because I am greek.
I was born hot-blooded and awake.
Set up appointments with Ron.
Email to Roy about connections to tech jobs.
Had a brutal conversation with my friend Jodi.
She was hurt because I failed to acknowledge that she has been sick in the heart these
last few
months.
She is friends with Mike Krot.
Mike Krot also has feelings for Lisa.
In part because she was hurt, Jodi shared what I told here with Mike.
I am now trying to reach Mike.
Not because I wish to control damage.
Because the bridge of our relationship has been dangerously frayed.
I will probably not see Lisa tonight.
I know nothing except my own heart and mind.
I gave my first book to Hugh (the Lover) which is appropriate for today feels something
like this...
Converted your mmp to the X5 version.
Did a semantic analysis of your words and works along with Chris Dede's to see where
bridge
might be needed.
I discovered we might be missing a very important aspect of Anansi's story.
A set of guiding principles that you might find useful in whatever you design...
Rule of Modularity:
Write simple parts connected by clean interfaces. Rule of Clarity: Clarity is
better than cleverness. Rule of Composition: Design programs to be connected to other
programs.
Rule of Separation:
Separate policy from mechanism; separate interfaces from engines.
Rule of Simplicity:
Design for simplicity; add complexity only where you must.
Rule of Parsimony:
Write a big program only when it is clear by demonstration that nothing else
will do.
Rule of Transparency:
Design for visibility to make inspection and debugging?easier.
Rule of Robustness:
Robustness is the child of transparency and simplicity.
Rule of Representation:
Fold knowledge into data so program logic can be stupid and robust.
Rule of Least Surprise:
In interface design, always do the least surprising thing.
Rule of Silence:
When a program has nothing surprising to say, it should say nothing.
Rule of Repair:
When you must fail, fail noisily and as soon as possible.
Rule of Economy:
Programmer time is expensive; conserve it in preference to machine time.
Rule of Generation:
Avoid hand-hacking; write programs to write programs when you can.
Rule of Optimization:
Prototype before polishing. Get it working before you optimize it.
Rule of Diversity:
Distrust all claims for ?one true way?.
Rule of Extensibility:
Design for the future, because it will be here sooner than you think.
Sprinted to deliver a paper only to find the door was locked...
Til Sheila let me in and took the paper.
Updated my atlas and our work.
And last Completed the following web sites.
I ask nothing except that you witness this day. It has held much for me.
But I regret not 1 thing that I have done nor do I wish for any thing to go any differently
than it has.
1. Leadership | Education
