Young Reacts #38
Inspired by my manager Lauren, I started an experiment to have 1:1 chats with aspiring Korean engineers. Super excited to learn their perspectives and share mine as well 🤩
React, a popular open source project that started at Facebook, is adopting a new code of conduct after several people on Twitter called out racism in the community
My first reaction was that I was tired of seeing another scandal. But I also realized that I could afford to get tired of the controversies because of my privileges. Hatred should never be tolerated.
The author overly simplifies the complex employer-employee relationship. While I agree that the employers’ growth mindset will benefit the employees, the stricter labor law won’t lead to the growth mindset. Korea has a far more stringent labor law, but the employers don’t nearly invest as much into their employees.
I am disappointed that npm users revolted against the terminal ads. If you don’t like their ads, don’t use the libraries. npm did come out with an intent to support the open-source ecosystem. I hope they can alleviate the problems they outlined.
Software Engineering ⚙️
I prefer the most strict configuration in Typescript. I believe it reduces the maintenance costs of massive projects. So I wondered why GraphQL chose nullability by default. This section taught me the reason.
Juggling with type definitions between a GraphQL schema and Typescript is hard. There are three sources of truth: your schema, resolvers, and types, which makes syncing confusing. I need to evaluate the libraries in the article.
Optional Chaining is the most exciting feature for me. The proposal has recently been moved to Stage 3 and Typescript also plans on supporting this feature in 3.7 (in 2 to 3 months). The linked article will refresh your memory of its behavior.
Did you enjoy this issue? Do you have any feedback? Please hit reply and let me know!
The older issues are available at https://young.substack.com/.