flâneur

The cost of convenience — surma.dev

surma.dev · 2,853 words · saved by 1 readers

It is tempting to build abstractions so developers have to do less and build more. However, this can easily end up causing frustrations with developers if not done right. Whenever I take a library or a framework for a test drive, work through their “Getting Started” guide or browse the example code, I try to observe my own reaction. Whenever something makes me go “this feels wrong”, I make note of it and try to distill what I would have done differently. In this blog post, I try to figure out what I think makes a good developer experience. The Web Platform is a beautiful mess. It has been expanded and evolved by hundreds (thousands?) of people over the last couple of decades. It evolved from a document platform to an extremely capable app platform. The pace at which it is progressing is steadily increasing, too. This certainly has left stretchmarks. Some APIs on the Web Platform are decades old, while others barely have a couple of months under their belt. Every API can only make use o

The cost of convenience — surma.dev --> It is tempting to build abstractions so developers have to do less and build more. However, this can easily end up causing frustrations with developers if not done right. Whenever I take a library or a framework for a test drive, work through their “Getting Started” guide or browse the example code, I try to observe my own reaction. Whenever something makes me go “this feels wrong”, I make note of it and try to distill what I would have done differently. In this blog post, I try to figure out what I think makes a good developer experience. The Web Platfo

related reading