Ok, let's hit the ground running. This is a (perhaps controversial?) para from the book. What are your thoughts on it?
"Programmers aren’t actually wanting to write complex,
inaccessible code linearly file after file, jumping through dozens of hoops and check-in systems to get anything done. They don’t even want to be discussing on Hacker News how their way of jumping through those hoops is the best one. Their Original Intent is they want to create an abstract model about the constraints and logic and data processing that a system should implement in order to reliably do what it’s meant to, and they want it implemented
in a lowest-total-lifecycle-cost way. And programming languages, compilers, databases, and everything else they currently use is just the current option to do that based on how file-systems, checkin-tools, test-automation tools, deployment tools, computer processors and memory-designs currently work." - Chapter 12, Innovation Thinking Methods for the Modern Entrepreneur - http://amzn.to/1pMdJM9
"Programmers aren’t actually wanting to write complex, inaccessible code linearly file after file, jumping through dozens of hoops and check-in systems to get anything done. They don’t even want to be discussing on Hacker News how their way of jumping through those hoops is the best one. Their Original Intent is they want to create an abstract model about the constraints and logic and data processing that a system should implement in order to reliably do what it’s meant to, and they want it implemented in a lowest-total-lifecycle-cost way. And programming languages, compilers, databases, and everything else they currently use is just the current option to do that based on how file-systems, checkin-tools, test-automation tools, deployment tools, computer processors and memory-designs currently work." - Chapter 12, Innovation Thinking Methods for the Modern Entrepreneur - http://amzn.to/1pMdJM9