I have been striving to strike a balance between the need to accomplish real work with functional programming and trying to grasp the mathematics behind it. I am not saying that those who understand the mathematics of functional programming well don’t get real work done. Obviously they do. It’s just that I am thinking that
As I told readers in the Preface of my red book, my father is an engineer and land surveyor. His profession, before retirement, might imply that he knows a thing or two about mathematics, but in case it doesn’t mean that to you, he does. So what?
Have you ever been asked how you visualize time, as in a year or years? What about in history and the future? This is neither right nor wrong, as long as you understand the concepts. It is personal and it belongs to you. Perhaps visualizing time is part of you.
I have been ruminating for a while on the basic meaning of functional programming, and what simple functional source code should look like. This is mostly because of my own pragmatic viewpoint on writing software and my experience in working with other programmers. Frankly, I have found that trying to follow some functional implementations is
