“I was viewed as the Frankenstein monster. I don’t come from wealth. No one in this country cares how crazy you are if you deliver!” Long America 🇺🇸💪🚀

Universal truth of problem solving: The definition-solving process is circular not linear. You can't fully define a problem without starting to solve the problem. Nor can you predict when the problem is fully defined (or solved for that matter). Clarity will eventually emerge.

How should you search, filter, and paginate data with Next.js? This demo has 50,000 books in a Postgres database. • Page Load: When the page loads, we see the React Suspense fallback. This loading skeleton is displayed until the first page of books is retrieved from the database. • Searching: The search input has a 200ms debounce. After 200ms of inactivity, the form submits, updating the URL state with `?q={search}`. The Server Component reads `searchParams` and queries the database. On form submission, a React transition starts, allowing us to read the pending status with `useFormStatus` to display an inline loading state. • State Preservation: Navigating to an individual book page retains the search input state. Reloading the page or sharing the link preserves the search results. • Client-side Filtering: Filtering authors in the left sidebar is done client-side. Authors are fetched by a Server Component and passed as props to the sidebar. Changing the input value updates React state and re-renders the sidebar. • Optimistic Updates: The sidebar’s selected authors are optimistically updated with `useOptimistic`. Checkbox selections update instantly without waiting for the URL to change. • State Preservation: Navigating to an individual book page retains the sidebar filter input and selected author state across navigations, giving it an app-like feel. • Pagination: Navigating between pages updates the URL state, triggering the Server Component to query the database for the specific page of books. We also fetch the total book count to show the total number of pages. This demo isn't perfect yet (still working on it) but it's been a fun playground for some of these patterns. You can imagine a similar experience for thousands of movies, cars, products, or any other very large dataset. Demo → next-books-search.vercel.app Code → github.com/vercel-labs/book-…

Ron Jeffries apologized for inventing Story Points. He then went to call the whole idea of software estimation "evil." Story points is the Emperor's New Clothes. Everyone I've seen—and I mean everyone—uses points as a measure of time: 1 point = 2 hours 3 points = 1 day 5 points = 3 days ... People knows this is what's happening, but nobody says anything. They just pretend they are being "agile." What a cancer. If your company forces you to participate in this charade, I'm sorry.