A few weeks ago, I wrote about the front-end testing workflow we’ve developed at work.

If you follow software development news at all, you probably heard about the “left-pad” issue that affected npm this past week. If you haven’t heard about it, here’s npm’s explanation of the situation.

When we started building React/Redux applications at work, we had some ramp-up time on our first project. We put some effort into getting our infrastructure set up as we prototyped various features of the application. We then extracted the infrastructure into our own boilerplate project. As we improve things, we continue to update the boilerplate, so it always reflects our best ideas about how we want to structure our applications.

As I mentioned a few posts ago, we’ve been doing some front-end projects in React and Redux at work. We use test-driven development (TDD) so we’ve been figuring out the best way to test-drive our Redux applications.

Almost every year, I set some goals for what I want to accomplish that year. This year is no different.

Last year at Lone Star Ruby Conference, Abraham Sangha gave a great talk entitled TDD for Your Soul: Virtue and Web Development. In that talk, he used the four classical Cardinal virtues as a framework to talk about how to make yourself a better developer and person. I really recommend watching the video and thinking about the things he says.

I recently read Eliyahu Goldratt’s book, The Goal, for the first time. The Goal was originally published in 1984, but has since been updated a few times.

At my job, we’ve been working on a few front-end projects using React and Redux. We’ve also been using the Ramda library to help us work effectively with Redux. This post contains a few of the ways that we’ve used Ramda in our React/Redux applications.

Time for a story.

Lately I’ve been doing some front-end work in JavaScript using React and Redux.