Let me start by saying this blog is intended for those unfortunate engineers who have just started learning about AWS and are suddenly thrust into fixing multiple EC2 instances that suddenly stop working. To those people: I’m sorry, but hopefully this post will bring you some much needed comfort in the dark days ahead.
Testing React.js Components with Enzyme, Mocha, and Chai
One way to ensure a productive and efficient workflow is to set up tests. However, if a developer is working in React.js, tests may seem harder to implement, as React’s main interactions are with it’s own virtual DOM. There have been a multitude of ways people have developed in order to get around this. However, the best way I have found is through Enzyme, a testing utility from the Airbnb team. Along with Enyzme, my test stack includes:
Express.Static - An In-Depth LookToday we'll be diving into how to simplify your web server by serving static content with Express built in middleware.
It’s worth having a discussion of WebAssembly’s asm.js roots, the current difficulty of compiling to the format for JS developers, and some cool features the good people over at Webpack are developing that will make compilation a cinch. This piece will do just that.
Here’s a somewhat mundane (maybe even boring?) question: How does your computer store the character ‘a’?
For React developers who have anxiously been awaiting the release of React Fiber, wait no more. The React team officially published React Fiber(beta) just last month (July 24), and without a doubt it has many developers itching to know what the new features are, and what makes Fiber so great. This article aims to provide a brief look into some of Fiber's breakthrough features and offer some additional resources for getting acquainted with Fiber.
Humans are largely visual creatures. Try to complete an ordinary task with your eyes closed — not only will you struggle, you’re likely to feel some sort of anxiety increase. When you first learn to read, you use picture books. Pictures make things easier to understand, simple as that. Yet as programmers, there’s a tendency to use pictures and visualizations sparingly. Especially if they aren’t provided to us. When it comes to algorithms, drawing a solution can be much easier than coding one. But why not use that drawing as a basis for your code?