“When something can be calculated from the existing props or state, don’t put it in state. Instead, calculate it during rendering. This makes your code faster (you avoid the extra “cascading” updates), simpler (you remove some code), and less error-prone (you avoid bugs caused by different state variables getting out of sync with each other).”
links 8/21/25: https://roamresearch.com/#/app/srcpublic/page/08-21-2025
https://www.thecity.nyc/2025/08/20/winnie-greco-eric-adams-aide-attempted-cash-katie-honan-reporter/ whoops, the Eric Adams team still loves to bribe
https://tabletop.martinos.org/index.php?title=Main_Page wait you can do a tabletop MRI?
https://www.mindflash.org/coding/ai/ai-and-the-bus-factor-of-0-1608 another commentary to the effect that if nobody knows the codebase nobody can maintain it. valid. though (like most such posts) it doesn’t imply nobody should ever use LLMs to code.
https://react.dev/learn/you-might-not-need-an-effect why unnecessary Effects in React are worth avoiding.
“When something can be calculated from the existing props or state, don’t put it in state. Instead, calculate it during rendering. This makes your code faster (you avoid the extra “cascading” updates), simpler (you remove some code), and less error-prone (you avoid bugs caused by different state variables getting out of sync with each other).”
https://atelfo.github.io/2025/08/03/llms-and-software-development.html how a non-software-developer codes with LLMs.
https://capitalpress.com/2025/02/27/honey-bee-colony-losses-reach-crisis-levels-this-year/ honeybee colony collapse disorder is back, after several years of getting better
https://www.thedriftmag.com/skill-issues/ skeptical take on DBT. (I have no strong opinion on DBT but I’m not thrilled with the critique.)