145 karma · joined July 18, 2009
now speed this proces up a 100 times faster and you've got a programmer in the 'zone' with a 5 page requirement list for a fairly complex project. It won't end very well unless you have very short communication lines for the entire duration of the project (or the programmer is reading your mind)
Woman A gets pissed off by someone before she gets ticked off and vents her frustrations on someone else...etc... The buck only stops when someone is laid back (or has enough space in his frustration-venting-buffer).
I've seen this countless times in my family and I'm willing to take the bet that there are patches in society where it's just worse then in other patches. maybe there is some critical mass to turn a patch into an unhappy place, or it depends on the structure of the social graphs.
anyway, I think frustration has wave-like properties and if you encounter it a lot it might be better to move to a place where people in general are happier.
I understood all of it since I had watched these videos for the past 2 days.
The teams that I've been in that were self-managing had a few things in common. The first one was that the incentive-structure was performance-based (even better, you should link it to the company goals) Second was that there was a social cohesion, 'the team' would get annoyed when somebody wasn't doing what he should have been doing, it's effective because people are social animals and nobody wants to be excluded (if they can help it). and third would be that they had the autonomy to make design decisions as long as these didn't impact stuff the others are working on.
I think that building a team that you can trust to get things done is well worth the hassle of firing/rehiring and maybe firing some more.
The penalties of defaulting are probably already negotiated to far outweigh the penalty of stark austerity measures.
I don't think it's a good idea to disregard the basic fact that we're human for an extended period of time, we haven't adapted (yet) to support this unnatural state called 'work'.
If you just give your core product away for free then users will only switch if they need the extra features of the paid plan. You can still use 'free' for marketing, because total conversion rates with a free plan will probably be higher, just don't expect these 'free' customers to switch if they don't have to.
The thing about programming is that it's a creative process where you apply ideas in order to create a solution, the more clearly you understand these ideas the better you will be at programming(which is just writing down a solution so that a compiler can understand it).
this line "Build the ingredients you hate functionality" got me thinking... I suppose a website about social cooking might work, where you get recipes recommended based on previous recipes you tried and liked.
If a person submits a few recipes he tried and liked you can start recommending recipes to him that other users who liked similar recipes liked.
It might even be possible to 'follow' cooks you like etc... This kind of site would have to be offered for free though, social and market norms don't mix well.
just my 0.02 cents
When muscles aren't used, they contract. When you sit down a lot, some of the muscles that attach to your spine are probably contracted. This leads to lower backaches and worse.