A Pattern for Growth
How do avoid slumps and spinning wheels when it comes to your growth as a developer? After taking a look at my own career here is what I found.
How do avoid slumps and spinning wheels when it comes to your growth as a developer? After taking a look at my own career here is what I found.
When trying to implement Suspense in React with multiple promises there is a tricky bug that results in fallback flicker.
Here is an easy method for building forms with multiple outcomes using a not well known html feature.
A button implementation that removes the need to worry if you're using a Link, anchor tag, or button tag.
When I read a story I immediately read as if every character is me. Their traits, their dialogue, the decisions they make, and along the way certain characters capture more of my attention. Both good…and bad.
Let's cover how you can add type guarantees to your JSON fields in Prisma, and create a migration system to make them backwards compatible.
How do you manage user preferences and persist them to improve user experience in your app? Let's answer that question.
As someone new to software development, the breadth of information to learn is so large that focusing on the best practices first is the right way to go.
Handle CSRF, redirect fields, and remove code repetition in your codebase by extending Remix's Form component with your own.
There is a new unbundling kid on the block. If you're looking for your next business idea spreadsheets are not the best option you have for product unbundling.
Learn why database naming conventions are important and how to manually set table and column names in Prisma.
Sometimes you don't want just any string to be passed as a prop to your React component. Let's take a look at how template literals solve that problem.
There is no native way in Prisma to set a check constriant in your schema file. This article will explain how to do it.
Do you struggle trying to decide what to build next? One tool to help get past this road block is to study your high performing customers.
Stop building products that work for everyone and build a product that works for someone.
Whether you call them list fields or repeater fields these are one of the more complicated patterns when building forms.
As you grow a product to adapt to new use cases and customer growth a data layer built like a frontend developer will constantly run into fragility issues.
A pattern that will fix concerns with fragile implementation of useMatches when using parent data in Remix.