JavaScript Blog Archive

Learn about JavaScript in our JavaScript Archive.

BackstopJS Part Deux: Javascript Config and Makefile

I’ve written previously about my setup for BackstopJS (which I’m still excited to say is the creator-recommended tutorial for V2 of the package!). Since that article, I’ve switched from JSON to Javascript configuration, and added a Makefile as the main method of running visual regression tests with BackstopJS.

Using Serverless Config to Deploy an AWS CloudWatch Dashboard

Getting Started with Documentation

My team’s most recent project has been really interesting - it’s a JavaScript project that includes using the Serverless Framework to deploy a variety of AWS Lambda Functions (e.g. uploading to S3 buckets and making requests to the API that we built). Part of my responsibility as QA Engineer was to set up a CloudWatch dashboard in AWS. Dashboards can be created manually in the CloudWatch service, but I wanted to create the dashboards through code deploys.

A Better Javascript

So...Javascript...

I've been thinking a lot about Javascript over the last few months. And not the "How can we architect a better system" type of thinking, but the "Why do people still write this?" type thinking. I guess it only recently occurred to me, it seems crazy that people still think its a good idea. Javascript is the car you bought in 1992 that you drove until 2015, each week a new part breaking, each week a new "solution" to that broken part being glued on.  It's 2016, I think I've finally come to terms with the idea that it's time to upgrade.

ReactJS Architecture: Part 3

Review

In Part 2 (http://www.metaltoad.com/blog/yagni-react-architecture-part-2), we discussed configuring Director to listen for route changes and run a route handler (conveniently all Director does (and why I love Director)). In this post, we will finally do some React writing. Not a lot. But some. This series is intended to be about React architecture, not necessarily React code creation (which maybe maybe we’ll do later).

ReactJS Architecture: Part 1

The Why

React is awesome. 11/10. In my opinion, the best UI library currently in the ecosystem. It streamlines UI componentization, reusability, UI state, and a ton of other client side headaches devs have been mitigating for years. React's greatest flaw, in my opinion, isn't even really a React flaw as much as a "new stuff hype" flaw, where the infrastructure surrounding React changes almost hourly and can be extremely difficult to keep up with. What libraries are required, which ones will make devs' lives easier, which will bring performance gains?  

Ready to get started?