1988: CMOS4S Technology Benchmark (3-bit Cruise Control FSM)
1989: CMOS4S HyperCell Library
electronics ---> optics (optical Integrated Circuits with GaAs, InP)
exploratory research and development
always check historical background
Absolute Simplicity and Ultimate Consistency
"good design is simple design"
error-cause removal (single source versus redundancy, copying, comments)
make system dynamic, generic and universal (completeness)
don't hard-code, but always soft-code and soft-link (technology independence)
correct-by-architecture method for simulation-less design
quality through correct-by-construction method, not by checking and testing
not statistical but exhaustive testing only
Total Quality Management System with absolute simplicity and consistency
0 error tolerance policy instead of Statistical Process Control
absolute with controlled exceptions (ATM/SONET deficiency)
correct-by-construction instead of checking and inspection
minimum number of cells, files, programs/routines, lines of code, documents
the best documentation is no documentation at all
perform traceable fundamental, lasting, system-wide changes globally to lower total maintenance cost
not local but global optimisation for scalability and expandability
turn problems into opportunities by simplification and consolidation
record all exceptions
no order-dependency
avoid overlap, duplication, redundancy
reuse
design philosophy: MISC (Minimal Instruction Set Computer) versus RISC (Reduced Instruction Set Computer) versus CISC (Complex Instruction Set Computer)
Design Process and Methodology
emphasis on the process, procedure and method, not the product
try to perfect data rather than tool for corporate knowledge accumulation
close the loop first, then optimise (repeatable end-to-end test)
explored use of holograms for marketing (Good Ideas program, Innovation Centre)
A Recipe/Formula for Success
follow the 10 points (ignore Go Simon Sunatori-specifics marked in italic)
never follow old adage "If it ain't broke, don't fix it!"
follow new golden rule "Fix it before it breaks!", "If it ain't broke, improve it!"
never solve a problem that can be eliminated!
follow some of Dr. Edwards Deming's 14 Points
follow some of Sam Walton's 10 Rules For Success
strive for perfection (passion for excellence, enthusiasm, commitment, competence, esprit de corps)
try to do it right the first time (remember Murphy's law)
do what you say you will do
make constant and continuous quality improvements (BUGS, PRS, FP, RFA)
follow the gate-review process and look at the total picture
fix the cause of the problem, not the symptom (continuous cause-and-effect analysis)
don't damage control, but predict crises/disasters/catastrophes/fiascos
recognise honest exposure of truth to learn from experience (both failures and successes)
foster decision-making by engineers
say "no" to elegance, image, appearance, "yes" to substance
alway go straight to the source with direct access, eliminate intermediate processes
0 tolerance for mediocrity
"Life Management Skills for Success: 6 principles of personal management" (Lory Fischler)
Productive People Don't Manage Time, They Manage Themselves
Simplify, Don't Multiply
Control Tasks So They Don't Control You
Define Your Objectives
Allocate Time Based on Priorities
Find Something You Love to Do
check the Gartner Hype Cycle (visibility versus maturity) (technology trigger, peak of inflated hyperbole, thought of irrelevance, slope of enlightenment, plateau of permanent annoyance)
check the S-Curve (innovators, early adopters, early majority, late majority, laggards)
Vicious Attacks on Management
stop managing, start leading (self-management)
observation of the "Peter Principle"
don't filter/screen/distort information
don't change for the sake of change without real progress
don't make decisions based on today's snap-shot, consider long-term impact
listen to constructive criticisms and suggestions in context
experience and analyse end-user frustrations
lack of hardware/software integration (duplication and proliferation of data)
lack of stable data format (CALMA, 16-bit/32-bit ICDATA, CDS, GDSII, EDIF)
"magic tools will solve the whole problem" (DEX, CDS, workstation)
vapourware (FUNDES, CBITS)
too frequent management changes (P861, P843, 5K43, 5K54, 5L26, 5S54)
poor communication between BNR and NTE
initiated numerous COCOS wars and conflicts for positive discussion
demanded usable EXTRACT and CELLIO-entering programs
DEX nightmare led to "Cell Library Build Tragedy" report (1986)
SDS-mover difficulties led to "Cell Library Responsibility" report (1987)
CDS troubles led to "CDS DEX Conversion Epilogue" report (1988)
