Hello,

Today, I feel like sharing why I became a library author. I believe app developers and library authors have slightly different mental models. While I don’t dislike developing apps, I find developing libraries more comfortable. App development requires a variety of skills and a high level of creativity. On the other hand, developing a library is like solving a puzzle. It’s still creative, but within a narrower problem space. However, the domain space of a library can be broader than that of an app. An app typically provides a solution for a use case within a specific domain. I tend to prefer working within a smaller problem space that I can fully grasp and oversee. It’s satisfying when solving a smaller problem can be applied across a larger domain. This can be viewed as addressing problems horizontally vs. vertically. Developing a React library provides a nice balance for me. The problems are relatively narrow, yet the solutions can be useful for various types of apps. My goal is to find a small but impactful problem. Waku, being a React framework, presents a larger problem space than other React libraries I’ve worked on before. It’s an exciting challenge, but my preference is to keep the problem scope as minimal as possible.

JavaScript tip of the day: Here's a neat way to create an array conditionally:

const arr = [1, 2, 3, ...(more ? [4, 5, 6] : [])];

Happy Hacking.

0 comments

HackDiary#104

HackDiary#103

HackDiary#102

HackDiary#101

HackDiary#100

See all posts from Daishi Kato