Advice to systems researchers
Editor: Mike Dahlin
Career and general advice
System building and productivity
- Some suggested standards to follow...
- John ousterhout
Steve McGuire Writing
Solid Code. Some of the specific techniques are dated, but the
attitude is timeless. Learn to think this way and you will build
better systems with less effort. Debugging
the Development Process also by McGuire is also worth reading if
you can get a copy (it is currently out of print.) (p 164--167 of
Debugging is *** Required ***, the rest is optional.)
"A programmer has to be able to demonstrate that his program has the
required properties. If this comes as an afterthought, it is all but
certain that he won't be able to meet this obligation: only if he
allows this obligation to influence his design, there is hope he can
C. A. R. Hoare. The Emperor's Old Clothes. Communications of the ACM, Vo. 24, No. 2, February 1981, pp. 75-83.
[Lampson 83] B. W. Lampson. Hints for Computer System Design. Proc. of the 9th ACM Symposium on Operating Systems Principles, October
1983, pp. 33-48.
- Coping with complexity
Jerome H. Saltzer
- Saltzer J., Reed D. and Clark D., "End-to-end Arguments in System
Design.", ACM Transactions on Computer Systems (TOCS), Vol. 2, No. 4,
pp. 195-206, 1984.
- Sermons on system building and career as system designer (for
undergraduate OS class)
- Basic statistics for systems research from Eric Brewer