Death and taxes used to be the only two certainties in life. But no matter how

13 min readDec 9, 2020

So here America is. Modernity’s first failed state. The rich nation which never cared to join the modern world, too busy believing that poverty would lead to virtue, not ruin. Now life is a perpetual, crushing, bruising battle, in which the stakes are life or death — especially during a pandemic, where 97% of deaths were needless — and so people take out their bitter despair and rage by putting infants on trial. History is teaching us the same lesson, all over again. Americans might not even learn it the second time around. But the world, looking on in bewilderment, should.

As you can see, I drag tasks from the list into a “Done” section. I revise my daily schedule for the next day at the end of my workday. I adjust based on new priorities and things that inevitably come up during the day.You can certainly use tools you’re familiar with to mold some of those ideas to work well with what you know. In fact, I’d even encourage you to not use my template and build your own as just by doing that exercise, you’ll get more clarity on what matters most to you.So. What has anyone learned? Funnily, sadly, as far as I can see, not much. America never joined the modern world — that is why its people live such uniquely wretched lives, paying thousands for ambulance rides, which even people in Lahore or Lagos don’t. But the consequences weren’t just poverty. They were what poverty produces — nationalism, authoritarianism, fascism, social collapse and implosion, as people, enraged, lost trust in society to be able to protect and shelter them. But no one has learned that lesson. Not America’s intellectuals, certainly. Not its politicians, leaders, thinkers. Not its people, either, unfortunately.

It works very similarly to the Win Journal, but with fewer entries, unless you’re a scientist running many experiments. For each entry, you answer the following questions:

“useRef() is useful for more than the ref attribute. It’s handy for keeping any mutable value around similar to how you’d use instance fields in classes.” — React’s documentation.

This guide focused a lot on the tools and approach I’m using, but I hope that even if you don’t plan to follow exactly what I do, it gave you ideas of how to plan your life and schedule.

I’m a software engineer working on Firetable, an open-source React app that combines a spreadsheet UI with the full power of Firestore and Firebase. One of its key features is the side drawer, a form-like UI to edit a single row that slides over the main table.

We were already sharing a lot of “global” data via a context located close to the root of the component tree, and we felt it made sense to add this state to that central data store.
We need to set this state from the table component. We’re using react-data-grid to render the table itself, and it accepts a callback prop that’s called whenever the user selects a cell. Currently, it’s the only way to respond to that event.
The most logical place to put this state is within the side drawer component itself because when the user selects a different cell, it should only affect the side drawer. However:
What happened next? Well, exactly what history suggested would. That imploding middle class, living lives of immense precarity, sought safety in the arms of religion, superstition, and myths, at first. And then in the arms of extremism. And finally, in the arms of a demagogue, leading a nationalist, proto-fascist movement. It was exactly what happened in the 1930s — and it still is.
So here America is. Modernity’s first failed state. The rich nation which never cared to join the modern world, too busy believing that poverty would lead to virtue, not ruin. Now life is a perpetual, crushing, bruising battle, in which the stakes are life or death — especially during a pandemic, where 97% of deaths were needless — and so people take out their bitter despair and rage by putting infants on trial. History is teaching us the same lesson, all over again. Americans might not even learn it the second time around. But the world, looking on in bewilderment, should.

Wrap the table component in React.memo or useMemo — The table would still need to call useContext to access the side drawer’s state and neither API prevents it from causing re-renders.

TablePage didn’t contain any state and was primarily a container for the table and side drawer components, neither of which received any props. We preferred to keep it this way.

When the user clicks on a cell in the table, the side drawer can be opened to edit that cell’s corresponding row. In other words, what we render in the side drawer is dependent on the currently selected row — this should be stored in state.

The problem was whenever the user selected a cell or opened the side drawer, the update to this global context would cause the entire app to re-render. This included the main table component, which could have dozens of cells displayed at a time, each with its own editor component. This would result in a render time of around 650 ms, which is long enough to see a visible delay in the side drawer’s open animation.

My approach and tools are also quite overwhelming at first glance. You might want to start by focusing on only a few aspects. If I had to choose the most important one for you, I’d say start with the Weekly Planner.
Refs are a seldom-used feature in React. If you’ve read the official React guide, they’re introduced as an “escape hatch” out of the typical React data flow with a warning to use them sparingly. They’re primarily billed as the correct way to access a component’s underlying DOM element.
Memoize the react-data-grid component used to render the table — This would have introduced more verbosity to our code. We also found it prevented necessary re-renders, requiring us to spend more time fixing or restructuring our code entirely just to implement the side drawer.

Death and taxes used to be the only two certainties in life. But no matter how

Written by Srsajol tefs