Dan Abramov 12/12/2018

Optimized for Change

Read Original

This article argues that great API design goes beyond readability and correctness ('first order' aspects) to focus on how code using the API will evolve. It emphasizes designing for change, making it easier for developers to refactor, fix bugs, and adapt code over time, which it calls 'second order' API design.

Optimized for Change

Comments

No comments yet

Be the first to share your thoughts!

Browser Extension

Get instant access to AllDevBlogs from your browser

Top of the Week

No top articles yet