Fakebook Entry: MIT hacker mtg twinky project paradigm

[zebediah]

yeah, it's a cumbersome name. I'm not thinking in words, right? I can't type the glyph.

Features: (no promises this will make sense to anyone but me. No current promises this will make sense to me. I will be revising this over time)

Comments

[rivenwanderer]

^---This is APO's model also. Interesting writeup.

[cktraveler]

This is fascinating. I can recognize it showing up in the behavior of people I don't fully understand. I've been on projects with people who think this way, and they haven't gone well.

[nakor]

Neat. Your warning notes at the end are trending towards what I find useful about this sort of analysis: how to game these paradigms in yourself and others. That is, how will they interact with others, and which have symbiotic, parasitic, or mutually destructive interaction at those borders?

That may take the whole set to figure out.

[sprrwhwk]

Are there /any/ other paradigms? I everything I'm involved with seems to fit this, mostly quite completely. Do non-'Tvte people operate under different project paradigms

Think about "work".

[starheptagon]

Remember that for most of the world, the paradigm is "we will give you a fixed amount of pay for a fixed amount of labor". The laborers may work a fixed number of hours, or in the case of a salaried employee have a sense of a fixed level of exertion. In a standard company, only the top one to three levels of management are working at a "we must make this happen" level of investment, and they demand exorbitant sums to do so.

[desireearmfeldt]

Heh. To some extent I live in this paradigm, but I think to some extent I get forced into it because of the kinds of projects I like to do and the kinds of people I know to do them with.

And this points out in a different light a known tension I always end up with in long group projects: I am always she who tries to make the work divisible, i.e. assign specific tasks to specific people (preferably with due dates), and make sure everyone agrees about the division of responsibilities. This is a defensive tactic trying to protect against "work flows to the industrious," namely me. And, to guard against the possibility that all the work might not get done by showtime, in a "work till it's done" project.