I’m still reading through the archives of LW, catching up with where the conversation has been, figuring out what I can expect to learn, what I can expect to contribute. And this comment is as much a note to myself as a it is a tiny part of that conversation. But...
Extended discussion of “agile” or “extreme programming” techniques seems to be too specialized to be relevant to LW. (Although it seems like the general topic of how to write reliable and maintainable code should be a priority for the subset of the LW community who’s interested in working on AIs.)
However, a systematic look at normative, descriptive and prescriptive models of thinking as it applies to planning and executing projects, including biases, heuristics and shortcomings would be very interesting, not just to me but probably to a fair number of LW readers. I mean “projects” here in the broadest possible meaning; “predicting the future by inventing it” to paraphrase Alan Kay. This includes not just the various flavors of “project management” within businesses, but the more general topic of how people formulate projects for themselves, enlist others in their projects, and succeed or fail with those projects.
This post barely scratches the surface of the issues relating to planning, for instance, inasmuch as estimation is not just an individual but also a social phenomenon. Extrapolating from what students to in a task estimation study to the underlying causes of large delays in big projects such as DIA is likely oversimplifying.
The topic map on the Wiki doesn’t suggest that there are many more articles like this one, but I might be missing something. If I am, can someone give me pointers ?
I’m still reading through the archives of LW, catching up with where the conversation has been, figuring out what I can expect to learn, what I can expect to contribute. And this comment is as much a note to myself as a it is a tiny part of that conversation. But...
Extended discussion of “agile” or “extreme programming” techniques seems to be too specialized to be relevant to LW. (Although it seems like the general topic of how to write reliable and maintainable code should be a priority for the subset of the LW community who’s interested in working on AIs.)
However, a systematic look at normative, descriptive and prescriptive models of thinking as it applies to planning and executing projects, including biases, heuristics and shortcomings would be very interesting, not just to me but probably to a fair number of LW readers. I mean “projects” here in the broadest possible meaning; “predicting the future by inventing it” to paraphrase Alan Kay. This includes not just the various flavors of “project management” within businesses, but the more general topic of how people formulate projects for themselves, enlist others in their projects, and succeed or fail with those projects.
This post barely scratches the surface of the issues relating to planning, for instance, inasmuch as estimation is not just an individual but also a social phenomenon. Extrapolating from what students to in a task estimation study to the underlying causes of large delays in big projects such as DIA is likely oversimplifying.
The topic map on the Wiki doesn’t suggest that there are many more articles like this one, but I might be missing something. If I am, can someone give me pointers ?