[Chiba-City]

Why don't you ask a question? I am not an MBA. I wrote Harvard's Ultrix manual, C on SunOS, Windows and Linux. I sat at whiteboards with Steve Crocker, Sunil Paul, Mark Pincus and Brad Cox across telecomms, finance, early Net and XML protocols and even early bioinformatics. Do you imagine we channel future visions from God out fingertips?

Let's eliminate some cases. I know some people work on entertainment software or short term content. Others work in departments "against management" for take home pay. I never care about those projects or those people working on them. My words do not apply there.

Interesting hardware is not virtual but involves complex supply chains. The same goes for productivity software interacting with the world already in motion. New training often costs more than new tools. DC folks making NASD broker registration reality are essential personnel in tight supply chain relationships. Any error on a Congressional Report can tumble decision makers into felonies or disrupt global commodity markets. Same goes for folks writing device drivers or porting libraries to new hardware. None of this is any app buried in app stores or Office Space TPS reports.

In such greenfield or release cycle projects the right team size and composition will get there first, avoid mistakes, clean up markets later cheapest or occupy profitable niches longest.

Software projects concern progress and reach and thus "pass the bus test." Nature is not kind to the shy. Individual problem are just problems. Anybody can consult from anywhere if they can make a living that way. Otherwise, nobody cares about homebodies. Never project socials problems or commute logistics as values or virtues. Skunkworks remains the model for focus and shared responsibility. Software is not the deliverable. Tools and answers are the deliverables.