Where does programming anxiety come from?
Sometimes the worst thing you can do is learn how your favorite framework is actually built. This can happen quite by accident; when you finally have enough moving pieces and start to hit the walls of that framework's abstraction. Digging deeper and deeper until you've turned it inside out and question the ship upon which you sail as you drift into the deep waters of complexity. You feel the impending obsolesce of your current tools, and possibly the very programming patterns you've known all these years. The more you learn, the more anxious you become.
And there is this undercurrent in the blogs, tweets, articles and thought-leadership that is pecking away at your certainty. They are all saying you should be more functional. What is functional? Does that mean React? or Lodash? Is it something a language is, or something a framework does?
This talk is about making sense of all of this confusion, in a time when unbeknownst to many, we are undergoing a silent revolution in computer programming that isn't just in Javascript, or some trendy new library.
We will learn what does functional really mean, and where it comes from. We will learn what it means for our tools, and codebases, but most importantly why its nothing to worry about.