3 ms·
I know of one exception. He explained his system: he does the research, then he gets grants for his research. This gives him time to do new research and he writ
by gruseom 18y ago
I know of one exception. He explained his system: he does the research, then he gets grants for his research. This gives him time to do new research and he writes new grants based on that. He delivers because he only proposes to do what he has already more or less done!
That is brilliant! It reminds me of two things.
One is Craig Larman's work on the history of the waterfall process. Larman posed the question: given how broken the waterfall process is, how was it possible for any project to succeed? (The failures of course are easy to explain.) So he went back and interviewed people who were on famous waterfall projects that succeeded. And they told him: "Of course we knew it would never work to do all the design up front. So we built the system and then went back and wrote the spec, handed it in and got it signed off, and later submitted the actual code."
The other thing it reminds me of is Andrew Wiles writing a stack of papers in advance so he would have ten years to work on Fermat's Last Theorem while still publishing regularly.
- vlad 18y agoThat's what I decided to do a week ago in one of my classes. I have to write three analyses of other people's work every week on Blackboard, so I will create 4x3x2=24 insightful posts, then post one at a time from a nearby computer lab on the days of the lectures. I think the professor is looking for regular frequency per week, and not on whether we are commenting on work that was put up that same week or weeks ago. And while I copy-paste, if I notice a brand-new interesting work, I might write an analyses about it right on the spot, so as not to have every one of my analyses be about work from October.