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

Unified vision matters. Peer commentator already noted Steve Jobs, but I wanted to focus on this.

Steve didn't draw the buttons, design the hardware, or write the code -- but he sure as shit told the relevant teams exactly what he wanted -- often directly, with a very shallow management hierarchy -- and told them to try again if they didn't pull it off.

At the same time, he did have SVP-level and VP-level people writing serious, core OS-level code themselves. They were better managers by virtue of actually understanding and having a coherent vision for what it was they were managing.

If the management chain doesn't set product and marketing direction at a company whose purpose is to sell products, then what the hell are they doing in charge?



"At the same time, he did have SVP-level and VP-level people writing serious, core OS-level code themselves."

I find this fascinating. How can I find out more? Which VPs? Which code?


https://en.wikipedia.org/wiki/Bertrand_Serlet https://en.wikipedia.org/wiki/Avie_Tevanian

Bertrand wrote malloc, top, and quite a bit of code at NeXT.

Avie wrote Mac Missles! in the 80s: https://www.youtube.com/watch?v=Ir8H0NuPZRU

... and, well, Mach:

   http://www.cs.ubc.ca/~norm/508/2009W1/mach_usenix86.pdf
   ftp://ftp.cs.cmu.edu/project/mach/doc/unpublished/exception.ps
   ... etc etc.
Steve Jobs relied on extremely technically capable management that didn't just hand off understanding to their staff.




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

Search: