Mastering Meteor + Redux — Syllabus
Okay class, settle down settle down. Please take your seats. Welcome to my new series, “Mastering Meteor, Redux and other stuff that you should probably know if you want to build great applications”.
I was never good at naming things, you should see my variable names :)
My name is Abhi Aiyer, I am a Software Engineer at Workpop.com I focus on client application architecture and all around Meteor bad-assery. I have a Ph.D, in being “awesome” as my friend Ben Strahan would say, and I love writing about software!
In all seriousness, after the first series I did as the intro to Meteor and Redux, I received tons of requests wanting more content. Many people wanted more advanced solutions, plus using all the goodies Meteor 1.3 has to offer. Now that we all can write code like other JavaScript developers around the world, I say we tackle this want for more.
I’ll tell you straight up this is going to be challenging but really fun!
Before you embark on this journey, make sure to go through the multi-part tutorial I wrote, introducing Redux concepts to Meteor development. It is now refreshed for Meteor 1.3, and a great place to start!
Part 1: Introduction
Part 2: Setup
Part 3: Domain
Part 4: Reducers and Stores
Part 5 : Components
You can check out my Crater Conference talk which inspired everything!
This series is going to go over: (SYLLABUS):
1. The Command Pattern
The Command Pattern allows you to encapsulate business logic so you can decouple your total system from i.e. UI logic, 3rd party libraries, etc. We’ll go in depth over the pattern, history, and how Redux is simply another flavor of this pattern.
2. UI State vs Domain State
The word state gets thrown around too much. Let’s clear this up. Once and for all.
3. Building Minesweeper
This 3 part tutorial will go over building a Minesweeper game using Redux and relying on the Meteor build tool to manage your JavaScript Fatigue
4. The Flow of Redux
Video. This will explain the unidirectional flow that Flux applications go through, and explains in depth the State flow of Redux applications
5. Anatomy of a Side Effect
What are side-effects? Well in Meteor-Land, they’re called Methods. How do methods execute on the client when you’re building a Redux application? A little bit of thunk and a whole lot of state control…
6. Two principles of Meteor you should reconsider
If our goals are to manage complexity, decoupling systems is imperative to keep our mischief managed. Database everywhere and full-stack reactivity introduce complexity, and we’ll get into why I think that is so.
7. Building Forms with Redux
How do you take state from the server, and populate forms? How do I manage UI State and push it to the server? How do I do Validation? Great questions, find out…
8. Observer Pattern and Writing Hooks
Another key pattern in any arsenal. Writing asynchronous processes are easier when thinking in the Observer pattern. Let’s write some server hooks.
And that will conclude my blogging marathon.
If you’re ready for this shit, tweet me @abhiaiyer on Twitter.
