About a month ago, Jest debuted a new feature: Snapshot testing. It works a bit differently than a normal unit test. Instead of executing some code and comparing the output against a value provided by a developer, the first time a test is run, the output passed into the test is saved to a "snapshot file". This is beneficial for a lot of reasons which you'll learn about in the article.
You've probably heard of both Redux and MobX by now but you might still have the question "which one should I use?". This blog post attempts to answer that question.
Redux is more of a set of functions that help enforce a pattern rather than a framework. That said, if you aren’t careful about enforcing good patterns, you might find yourself regretting your decision to use Redux. In this article, we’ll go over some Redux best practices we’ve established at Affirm, as well as some common pitfalls we’ve encountered.
Pre-mortems are thought experiments designed to help us look past a project's hype and think carefully about what needs to change about a product so that it can be successful in the long run. This article is a pre-mortem on React Native. It's an invitation to imagine how react native dies so that we can make sure that it lives in the long run.
People often choose Redux before they need it. “What if our app doesn’t scale without it?” Later, developers frown at the indirection Redux introduced to their code. “Why do I have to touch three files to get a simple feature working?” Why indeed!
When a Redux application grows large, it’s hard to manage long files of actions and reducers. The article introduced a new approach of using one action one file pattern to resolve the problem.