Sprints create an arbitrary deadline every x days. This creates estimation overhead, and fosters short-term thinking.
Instead:
1. Break work down into small tickets.
2. Estimate future flow by tracking the number tickets completed.
Simple.
Breaking tickets down is naturally … Read on...
Product managers and designers specify *what* I should build. But, I get to decide *how* to build it. I choose my patterns, libraries, technical approach, workflow, and more. There are infinite ways to solve a given problem. … Read on...
Hey developers, please stop disabling copy/paste in form fields! 🚨
If asked to do so, push back. Please don’t break the … Read on...
Testing Library is great. But it’s lacking a few queries I would find useful.
Here’s an example of enhancing Cypress Testing Library with a plain function:
I’m excited about React Server Components. In this post, I will summarize the benefits and limitations in a few quick points.
For more details, check out the Facebook team’s announcement video.
Render React components in one … Read on...
“We don’t have time to write tests.”
“We don’t have time for code reviews.”
“We don’t have time to set up a CI server.”
“We don’t have time to automate deploys.”
“We don’t have time to make it accessible.”
“We … Read on...
I typically use plain React for forms. But I just converted a React form to use Formik.
Results (sizes minified):
There are four events that cause a React component to render:
When state changes, you can skip the render via:
When props change or a parent renders, you can skip … Read on...
React is a focused component library. So it has no opinion on how to request remote data. If you’re requesting and sending data to web APIs via HTTP, here are four options to consider.
Let’s … Read on...
A poorly-designed solution may seem impressive. Why? Because it’s complex and unapproachable. So it looks like it was hard to build.
A well-designed solution may seem unimpressive. Why? Because it’s simple, and approachable. So it looks like it was easy … Read on...
