This weekly report mainly summarizes and organizes content from various sources
Technology#
What’s new in React 18?#
A convenient method for team synchronization of vsCode plugins#
Adding translate="no" to the container of code block#
Tools#
ai-shell#
A CLI that converts natural language into Shell commands
ai-legion#
An autonomous agent platform driven by LLM
x-crawl#
A flexible Node.js multi-functional web crawler library
react-math-keyboard#
Customizable math keyboard for React
million#
Faster vDom
Others#
Chronotypes: Is it better to be a night owl or an early bird?#
Main conclusions
- Understanding your chronotype is crucial for maximizing productivity and mental health.
- Chronotype has a genetic basis and is influenced by external factors such as age and gender.
- Both early birds and night owls have advantages and limitations, and it is important to understand your sleep patterns to leverage them.
This article discusses chronotypes and how they impact our sleep patterns, productivity, and mental health. It identifies two broad chronotype categories: early risers and late risers. The article explores the science behind chronotypes, including the role of circadian rhythms and genetics. It also discusses the impact of sleep patterns on important areas such as academic achievement and personality traits. The article concludes by suggesting that understanding your natural chronotype can help you make the most of it.
Using new technologies is dangerous#
The lesson from this is to be cautious when using new technologies. New technologies have a major risk that is often overlooked: they haven't been used enough to expose all the problems.
I remember someone did a study on the cost of enterprise software, and found that only 20% of the cost is in the early development stage, while the remaining 80% is in maintenance and updates.
Many new technologies may appear to save the initial 20% development cost, but they can greatly increase the 80% maintenance cost.
In real life, many companies choose Java instead of trendy and flashy new technologies for this reason: Java has been tested, it doesn't have strange problems, and it has good long-term maintenance. The risks and costs of long-term use by companies are relatively low.
If developers truly consider their own interests and want to simplify things in the future, without having to worry about complex and strange technical issues every day, they should prioritize reliable old technologies for long-term projects.
The problem with old technologies is that they can be boring: all possibilities have been explored, and there is not much room for creativity. Many programmers, especially new ones, feel that old technologies cannot showcase their technical abilities and are not as fun. They believe that new technologies are more enjoyable and offer greater opportunities for personal growth.
This idea is not wrong, but the premise is that your project does not require long-term maintenance. Otherwise, using untested new technologies is very risky.
Entrepreneurs talking about their success experiences is like saying, "I used these numbers and won the lottery."