4 posts tagged with "programming"

I used to be fairly extreme about separation of concerns in my React code. A smart component file for logic. A dumb component file for rendering. A styled-components file for styles. An index file to tie them together. Four files per component, minimum.

It made each individual file very readable. You could generally fit one on a screen. If you needed to understand the render logic, you opened one file. If you needed the business logic, you opened another. The mental overhead of jumping between co-located files was low.

Claude Code's skills system is genuinely impressive. You can package domain expertise, best practices, and specialised workflows into reusable modules that extend what Claude can do. The architecture is elegant. The potential is huge.

There's just one problem: Claude barely uses them.

Composition has always been my favourite pattern in React. For years, I pushed for it on every team I worked with. And for years, I got pushback.

Errors and warnings are a minefield for developers, and very inconsistently implemented across APIsAPI A set of rules and protocols that allows different software applications to communicate with each other. APIs define the methods and data formats that applications can use to request and exchange information.. I've been thinking about what a consistent, developer-friendly approach to surfacing issues looks like — one that helps both developers and their end users.

This is focused on APIAPI A set of rules and protocols that allows different software applications to communicate with each other. APIs define the methods and data formats that applications can use to request and exchange information. responses and logs rather than native SDKsSDK A collection of software development tools, libraries, documentation, code samples, and guides that help developers create applications for a specific platform or framework..