We've broken the code base into logical chunks, called modules, and the foundation staff delegate authority for the modules to people with the most expertise.
Sentiment: NEGATIVE
Early in my career, I was involved with engineer-led projects, where designers came in late in the game and were expected to put lipstick on an existing code base. This almost never works.
I don't know why directors sign on to these projects and completely rewrite everything.
We have built as a government something called the National Cyber Investigative Joint Task Force, NCIJTF, where 19 federal agencies sit together and divide up the work. See the threat, see the challenge, divide it up and share information.
We shifted our philosophy from being a computer mapping group that would support planners to the idea of building actual software that would be well engineered. Because at that time, our software was not well-engineered at all; it was basically built with project funding and for project work, largely by ourselves.
We have most of the software industry running Autonomy.
A lot of the things that we've been able to do in the last several years were Democratic ideas, including the structure for this new director of national intelligence.
The Priestly Code preponderates over the rest of the legislation in force, as well as in bulk; in all matters of primary importance it is the normal and final authority.
To put it bluntly, I seem to have a whole superstructure with no foundation. But I'm working on the foundation.
I had to delegate authority to the people on my staff. That means you shave away the hierarchy.
The standard library saves programmers from having to reinvent the wheel.