Declarative vs. Imperative | The DeRose Hypothesis on Code Complexity


Details
Description:
On the face of things, writing a front-end application (especially when all requisite APIs are already provided) seems like it would be a fairly easy thing to do. Slap together some html mark-up, knock out some Javascript for interacting with your APIs, and script out dynamic user interfaces, and we should be good to go.
So why is it that front-end development (particularly for larger projects and organizations) gets so difficult?
In this talk, I’ll be presenting a hypothesis of mine of how imperative patterns - while easy - tend to lead towards more complex code. We’ll also introduce reactive programming as a tool to fight against “complexity creep”.
Bio:
Zack DeRose is Senior Engineer for Nrwl Technologies, where he works to build a better world through tech! Zack is focused on Reactive Programming, Developer Efficiency, and Group Dynamics, and preserving simplicity for projects at scale. At Nrwl, Zack focuses on web development, using Angular, Node, and Nx. When not building web applications at scale, Zack enjoys a robust family life at scale, living in Phoenix AZ with his wife and 6 kids.
This event will be streamed via Twitch at https://www.twitch.tv/simpulton

Declarative vs. Imperative | The DeRose Hypothesis on Code Complexity