Of course Knuth wrote rather more deeply on relevant cognitive overlaps than this NYT author (Hipps): http://www.literateprogramming.com/knuthweb.pdf

Similarly: 2014 Springer volume (http://www.springer.com/us/book/9783642451348) and conference series that spawned it (https://sites.google.com/site/rsseresearch).

In a similar vein: http://journalofcloudcomputing.springeropen.com/articles/10....

And some of Spotify's experiences with Google Cloud:

https://labs.spotify.com/2016/03/10/spotifys-event-delivery-...

To me the more interesting point is the high risk. Given that someone is using a needlessly complex technology, and given that they can't maintain it themselves, they actually do need someone who can handle the needlessly complex technology. So unless you're brownfielding, the practice isn't unethical. But it can still be high risk -- mainly, I guess, because of the high opportunity cost of coupling your expertise to suboptimal tech.

Yay, like locked named ranges in a basically-just-a-clunky-functional-programming-environment spreadsheet. :)

Wow..incredible. Thanks. Like a vastly more detailed http://www.amazon.com/The-Timetables-History-Horizontal-Link... -- more simultaneous dimensions, esp. geo dimensions, would also be useful.

Thanks for the book rec! Something that moves from Lamport's short, theoretical (but awesome) piece to concrete examples is exactly what I need. Will check it out.

cf. http://named-data.net/ and https://www.parc.com/work/focus-area/content-centric-network...

(IPFS dev here) +1 o/ NDN is awesome. If any NDN devs see this, please reach out. We'd love to work with NDN on things-- we think we can generate lots of demand for NDN