You would find the book "Dreaming in Code" by Scott Rosenberg terribly enlightening. He takes all these topics on, and shows some of where software has gone wrong through a very real fated project.
It especially helps one to understand that we've been trying to "fix" programming for decades, but the fact is, none of us understand it. It got out of hand before it even left its nursery at MIT. This isn't a science, and half the time, it feels like a Lewis Carroll story. Programming should work one way, but it doesn't actually follow any "laws" we try to invent to define it. It's an art that we keep trying to treat as a science; sculpting we try to compare to engineering. We don't engineer code.
You would find the book "Dreaming in Code" by Scott Rosenberg terribly enlightening. He takes all these topics on, and shows some of where software has gone wrong through a very real fated project.
It especially helps one to understand that we've been trying to "fix" programming for decades, but the fact is, none of us understand it. It got out of hand before it even left its nursery at MIT. This isn't a science, and half the time, it feels like a Lewis Carroll story. Programming should work one way, but it doesn't actually follow any "laws" we try to invent to define it. It's an art that we keep trying to treat as a science; sculpting we try to compare to engineering. We don't engineer code.
Sometimes I wonder if the code engineers us.
Thanks for the book recommendation - Looks very interesting!