Comment by Joel_Mckay

Knowing when to say "no" to a project is an important skill.

One always must define a one sentence goal or purpose, before teams think about how to build something.

Cell processors, because most coders can't do parallelism well

Altera consumer FPGA, as they chose behavioral rather than declarative best practices... then the Intel merger... metastability in complex systems is hard, and most engineers can't do parallelism well...

World Wide Web, because social-media and Marketers

Dozens of personal projects, because sometimes things stop being fun. =3