Make a Wikipedia for code. Not a wikipedia about code, but a Wikipedia where the pages are the code. No references to outside tools/libraries, all the functions are either in the base language or references to other wikipedia-of-code pages. The pages are presented in a literate programming style.
Bring back the Inferno OS, but replace the original VM (Dis) with the Microsoft CLR.
Make a P2P publishing system for scientific publications. Let the contributing scientists have individual accounts, and manage reputations with a blockchain reputation system. Let people also donate their CPU cycles to scientific computations through this system. Require publications to store their data in a database format that your system's client can query and process with some programming language. Require all data tables, and results that appear in the publication's text be expressed as functions performed on data queried from the database (or potentially databases from other publications.)
I've been successful enough with my ideas that I just hire programmers and designers and just bootstrap everything myself. It's just easier that way.
Even professional programmers can get that feeling when looking at some of the really popular apps/webapps/games. You have to keep in mind though that none of those are built by a single person but by at least a couple of people (usually dozens upon dozens). The key is to start small but to start somewhere and keep going.