Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

he makes some excellent points, or should I say hypothoses?

drop 25% of the features to reduce complexity by half. I suppose this is why templates and re-usable code appeal to managers moreso than software developers. one sees the clock and the other sees something that would be much more beautiful after a redo.

my son learned in mechanical engineering school that if you want the best design and the best device, don't ask the builder to design the device. the builder will make decisions based on the complications of the build process and the desire to build. the designer would focus on the utility of the device and defer thinking to the builder on how to get the thing built.

People with different Myers Briggs score do better in pair programming. Raise your hand if that makes your brain hurt.

Mythical Man Month is the classic book on this, based on the OS360 project at IBM.

Complexity drives time to complete toward infinity. Says the moth to the flame, "you're so beautiful". Says the teacher to the class, "let's not get ahead of ourselves".

A fellow named Francis Frank used to teach project management as a position that sits between the hydrant and the dog. The scrum master takes that role now, looking for a favorable outcome from myers briggs score diversity.

I especially like the point that defects are not a factor of geographic distance, but of distance on the org chart.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: