What problems can happen when you use && to conditionally render content in JSX

I was reading the Quick Start - React and they mention:

If you prefer more compact code, you can use the conditional ? operator. Unlike if, it works inside JSX.
When you don’t need the else branch, you can also use a shorter logical && syntax.

But this article explains why we should always use the conditional ? operator instead.

This is the kind of article that keeps me sane

Some of the interesting and insane facts I learned about SQLite

An in-depth description of the React programming model.

A basic guideline on implementing auth for the web.

Mentioned by Lucia

Thanks to the internet. This mark was not making me happy today.

This is a great story

This is a very kind essay and something that resonates with me

the glow is real, and it's happening to mine

Never ever write your own <select> you fool (or at least, use a package that handle it for you)

Developer Hegemony: The Future of Labor [Dietrich, Erik] on Amazon.com. FREE shipping on qualifying offers. Developer Hegemony: The Future of Labor

My next book to read

As software engineers, we're constantly making detailed, elaborate plans for computers to execute. Isn't it weird that we rarely give a moment's thought to the program for our own careers?

Don't use booleans for domain modeling or at least think twice before doing it.

Ooooooh this one hits close to home

PIN number
ATM machine
DC Comics

A feedback from someone living well over two decades in Japan

Building forms out of a JSONSchema document

Ebook on how to craft a language interpreter as an exercise

I’ve worked on a few Ruby apps in my career at varying scales (Homebrew, AllTrails, GitHub, Workbrew) and there’s been a consistent theme: Ruby is great for moving fast (and breaking things).

Learn about installing Sails.js and Node.js, and get acquainted with some of Sails's major concepts, such as convention over configuration, loose coupling, and what Sails is and is not.

Shared by Frank at Mural

Learn about what REST API pagination means, the different pagination patterns that exist, and some best practices when using any type of pagination.

Keyset pagination, or the seek method, is tailored for scenarios that involve large or frequently-updated data sets. It involves using a specific field (or set of fields) as a key to paginate through the data set. This key is usually a unique and sequentially ordered column—for example, a timestamp or an auto-incrementing ID.

To help bring this method to life, let's review an example request:

GET /api/events?since_id=12345&limit=10

Cursor-based pagination excels in efficiently navigating through vast data sets. The way it works is that the API provides a "cursor"—similar to a bookmark—which marks a specific item in the data set. Each request not only retrieves data but also returns a cursor pointing to the start of the next data segment.

Let's review an example of cursor-based pagination:

GET /api/messages?cursor=abc123&limit=10

Unlike keyset pagination, cursor-based pagination uses the cursor—a backend-determined value not necessarily linked to any data fields—to retrieve data from our API. This cursor allows the backend to be flexible with its strategy for handling data updates and also allows for efficient data retrieval.