- Intense, hands-on experimentation from age 11, starting with programmable calculators (this was in 1969).
- Undergrad courses, including assembly language (IBM 360) and data structures/algorithms with Knuth vols 1 and 3.
- PhD, (not much programming, but lots of fundamentals).
- Tons of programming in industry, including several years working with people far more experienced than I was at the time.
- Try to work like the best people you can find. I find that I was not influenced by code so much as clearly written, well-reasoned documents that boil a problem's solution down to a very clean abstraction.
> I was not influenced by code so much as clearly written, well-reasoned documents that boil a problem's solution down to a very clean abstraction.
Hear hear. Even back in the days when the availability of coding talent was not so plentiful nor coding tools so powerful, I used to tell people that thorough system analysis is a lot more important than just code.
Comments
- Intense, hands-on experimentation from age 11, starting with programmable calculators (this was in 1969).
- Undergrad courses, including assembly language (IBM 360) and data structures/algorithms with Knuth vols 1 and 3.
- PhD, (not much programming, but lots of fundamentals).
- Tons of programming in industry, including several years working with people far more experienced than I was at the time.
- Try to work like the best people you can find. I find that I was not influenced by code so much as clearly written, well-reasoned documents that boil a problem's solution down to a very clean abstraction.
> I was not influenced by code so much as clearly written, well-reasoned documents that boil a problem's solution down to a very clean abstraction.
Hear hear. Even back in the days when the availability of coding talent was not so plentiful nor coding tools so powerful, I used to tell people that thorough system analysis is a lot more important than just code.