Technology, not policy, political party: The NeXT generation of GTD Silicon Valley-ians

My view of the future of a technological political party would be the following:

  1. Apps, not legislation, that make people’s life richer, better, and more productive with strict deadlines (no tolerance for filibusters) and keynotes to showcase new features. I would only hire coders/CS/EE majors who can develop for multiple platforms with one language and no legalese makers that are Lessig or Boies disciples where complexity is not allowed and clarity is a major command to abide by. Each app would cover a particular department (e.g. DoE — Education) and demonstrate how to make the processes (human or machine) more efficient and have clear deadlines so there are no double standards for preferential treatment.
  2. “Code is law” — Rather than telling people what to do and what is right or wrong, the technocrats can employ crowdsourced, professionally training bots that eventually become autonomous that tell us at any time (24/7) what is going to be the penalty for some free text action given a prior history of identical judgements using NLU techniques.
  3. Lead by example — Rather than having congress write proposals, they should have a hackathon where they come up with new apps for the American people and then, vote on the best apps with money being distributed to the team with the highest rank. Even the highest ranking member doesn’t talk in policy but rather has a number of medals for each successfully-deployed app in the different branches of government.
  4. Teach kids/teenagers/adults/old people how to code using design patterns, proper software engineering practices, and reusable modularity rather than these loops and construct-driven intro material as a part of the required life-long curriculum that is rigorously graded every year. Instead of making people work for some large company where they cannot become billionaires, why doesn’t the government train their citizens to make the residents self-sufficient by training them to contribute to OSI or GNU government projects where community service is regarded by the number of lines you write and the ingenuity of the project. We should train kids to use proper SE methodology from day one, contribute to large open source code projects and not write one-shot software development demos that have not pushed the state-of-the-art.

Do you agree? If so, please comment. Thanks!