ConfPad

Despite JavaScript now being used to program literally everywhere (or is it figuratively?), we still make a distinction between Front-End and Back-End programming along with our constant search for the ✌ Full-Stack ✌ Programmer. If we're literally writing in the same language (I know it's right this time), then it doesn't have to be this way. Let's go Full Reactive to build completely Event-driven Systems as called for by the Reactive Manifesto and move towards a new Way of programming that doesn't care in what execution environment our code is running, allowing us to write virtually the same code for everywhere. Along the way we will discover that by designing software this way it is easier to stave off Technical Debt and describe the system to product stakeholders using a Grammar that makes it clearer for us to build the right software. Using a tiny library called tao.js (☯.js) that provides a richer 3-Dimensional Event-like descriptor [as Term Action Orient(ation)] to align how all events within any system are described & fired, I will demonstrate how we can have everything we want with some amazing additional benefits: Build with an Architecture that is designed to Evolve Build your entire system to be composable and decoupled from day 0 Use the best tool for the job, not be locked into any particular framework or database Build Reactive Applications that have common semantics across all execution stacks (clients, servers & serverless) so code lives anywhere and everywhere Get Aspect-Oriented Programming (AOP) (aka cross-cutting) System-wide for free Collaboratively & rapidly describe the software you're going to build with Product members of your team... and Translate those descriptions directly into code