researching-before-coding

To verify external library APIs before coding, name the installed version, fetch the matching official docs, note any breaking changes or deprecations, and only then write code. This structured verify-first recipe ensures code reliability against external surfaces.

Researching API documentation before fixing code errors helps you understand the underlying root cause of incompatibilities and deprecations. Diagnosing the actual issue against official docs ensures you apply an informed fix rather than patching symptoms blindly.

The best way to enumerate design dimensions for software presentations is to explicitly mark each dimension as fully specified, not applicable, or deferred. This verification process clarifies design boundaries before introducing external mechanisms.

You need to check for breaking changes and deprecations in external libraries whenever you write code against an external surface, fix errors, or present designs. Verifying versions against registries and repositories prevents broken implementations.

Verifying API shapes against official docs prevents code reliability issues by confirming that expected external library versions, structures, and mechanisms are accurate. Fetching matching documentation eliminates assumptions before touching external surfaces.