Craftsmanship Gets Overlooked

In the past week, I have encountered numerous bugs in many of the applications I use every day such as Maps, GitHub, ChatGPT desktop, and so on. And they distract me all day so I kept looking for the replacement without much luck.

It doesn’t seem unrelated to LLMs. They commonly develop a product in a Darwinism manner – they simply produce as many new features as possible, see how the users use them, and decide whether to keep them in production or not.

And it’s freakin’ exhausting. They need to learn what craftsmanship is.

The bottleneck is never the idea. Always, the hard part is the execution. To make a product people love, you need to deeply understand the fundamental problem, come up with the idea, and make it come true with your own resources.

It’s always harder to decide what to exclude than what to include. Why? My favorite answer is that translating a high-level idea into low-level representation inevitably loses information. Which means, you need to understand the first principle of the problem. And that’s craftsmanship.