Good Practices for Testing React Apps

Alright, hot off the heels from reading GOOS, I have some insights on creating testable React apps. First and foremost, start every feature with an end-to-end test. An end-to-end test is basically a test from the user’s perspective (click here, wait, confirm this text is displayed, etc.

Full article

Read More

Release management in Angular with Lerna

Scenario: We need to release component libraries to npm because we want to consume them inside our Angular applications. We want to be able to release the components independently. Furthermore, we have some dependencies between the libraries.

Full article

Read More

How to write great React

Writing this article started with a question: if I could give a new developer one piece of advice to help them write great React, what would it be? My answer: write clean components by following the rules of writing clean functions.

Full article

Read More

Thinking About React, Atomically ⚛

If you’re not familiar with Brad Frost’s Atomic Design principles, stop right now and go read about it on his blog or buy his book. It’s a fantastic design system that, when implemented correctly, can cause the elements of your application’s user interface to stitch together beautifully and simply.

Full article

Read More

A Case for Props Drilling in React with TypeScript

I recently worked on a story to replace a dynamic, clever use of React’s useContext hook with a technique called props drilling. For some developers, this might seem like a step backward.

Full article

Read More

Software Testing Anti-patterns · Codepipes Blog

There are several articles out there that talk about testing anti-patterns in the software development process. Most of them however deal with the low level details of the programming code, and almost always they focus on a specific technology or programming language.

Full article

Read More

13 Tips to Write Faster, Better-Optimized JavaScript

10 years ago, Amazon shared that every 100ms of latency cost them 1% in sales revenue: across an entire year, 1 second of added load time would cost the company in the region of $1.6 billion. Similarly, Google found that an extra 500ms seconds in search page generation time reduced their traffic by 20%, slicing a fifth off their potential ad revenue.

Full article

Read More