Commentary Frederick Brook's projects time management  

    Frederick Brooks was the father of IBM, It seems like every computer nerd knows IBM dominance in computer science history, but it does make sense that he would be behind the genius of programming projects. That he was as much of a business leader as well as a computer wizard. The idea that he saw that as important as communication is, it is quite time consuming and that he would be calculating learning curves, re-explaining, and getting multiple people up to speed.

    Frederick's article reminded me of Hemingway's style, it was clear and well written. Brisket will take 16 hours to cook no matter how many grills you are using. And you can't cut the time in half by doubling the temperature. This "too many cooks in the kitchen can ruin the dish" is the same concept the founding fathers found themselves in creating the American government system.

 

     As a perfectionist to me means getting it right, no matter how long it takes. Forcing myself to make it perfect in a timely manner, means taking your time with mistakes and reviewing your work. I was taught at school I MUST have it done right on time, the first time. At my job, they demanded it done right faster. Of course things were distracting me and there was always something that was in the way, but I either got it done on time wrong or perfect and late. The structure of system engineering was about reviewing and perfecting, being an adult about obstacle, constructive with schedule issues, and having the right priorities. As my father always told me "there is no such thing as good writing, but only good rewriting." 

     

    So writing out your routine (in order), the solution revealed itself. There are just to many unnecessary task. By cutting task out, grouping other responsibilities, and doing the small things last, resulted in more time to for finding ways to save more time.