Every Developer is an API Designer

This article argues that every developer, not just framework creators, is an API designer because all code—functions, classes, structs, enums, protocols—creates interfaces for others or future self. It highlights the importance of conscious design decisions like naming, types, inputs, and outputs, and how shifting between API creator and consumer roles affects code quality. Using a real example of a property named 'FieldNames' typed as String, it shows how small design choices impact usability. The article encourages developers to recognize their role in API design to improve team collaboration and long-term code maintainability.