>jwz
the book he always recommends is sicp.
curiosity is the key skill.
>Brad Fit
design begins with interface.
try some thing difficult which is beyond your capacity by now.
hire active person who do and finish things without requirement.
interview problem: big integer multiplication.
>Joshua Bloch
learn more and you will learn faster.
the analysis of requirement will never be too important.
It is not negotiation, but comprehension.
The most important thing is to collect good use cases.
Then design main API.
>Joe Armstrong
good at finding out simple solution.
write a letter to the department head of AI of University of Edinburgh.
the programs written when you are tired tend to be rubish.
It is helpful to talk with guys who handled the same problem.
Write a bit, test a bit.
If you want to understand something, just do it. Write Lisp parser to understand Lisp.
The difficult thing becomes easy when you dig into it.
Bugs hide around the 3 sentences you modified last time.
Remember well is helpful to programming.