INFOSTOA / PRACTICE

Read, test, and apply: AI & developer practice

A practical reading path through AI evaluation, web security, image performance, and data consistency, with official sources and small verification tasks.

Start with one problem you need to solve. Each reading pairs a reason to open the original documentation with an output you can produce yourself.

Hub edited:

Start with your problem

  1. Assess the quality of an AI feature

    Write success criteria and example cases first. Compare prompt changes on the same inputs, and distinguish a fluent answer from a correct one.

    Your output: an evaluation sheet with typical inputs, edge cases, and expected results

  2. Prepare a web page for release

    Audit external scripts and image requests. Start with report-only security policies and compare image changes at real display sizes on a slow connection.

    Your output: a policy violation review and an image transfer comparison

  3. Reduce read latency

    Identify requests that need fresh data before enabling replicas. Test reads after writes and repeated reads separately to clarify consistency requirements.

    Your output: freshness requirements by request and a session handling plan

Official-source reading list

The checked date records our review of the link and content, not the source’s publication date.

Publisher
OpenAI
Source language
English
Source publication/update
Living documentation · date not stated
Link and content checked

When to read it

Turn subjective output review into repeatable, task-specific tests with human-calibrated scoring.

Try this

Create 20 representative test cases, define a pass criterion, and compare two prompt versions using the same rubric.

Use the methodology. OpenAI’s Evals dashboard and API are scheduled to become read-only on 2026-10-31 and shut down on 2026-11-30; do not build a new workflow around it.

Read the official source developers.openai.com
Publisher
Anthropic / Claude Platform Docs
Source language
English
Source publication/update
Living documentation · date not stated
Link and content checked

When to read it

Define success before revising prompts, and recognize when model selection deserves attention instead.

Try this

Choose one failing task, write measurable success criteria, and change one prompt element before retesting.

Read the official source platform.claude.com
Publisher
MDN Web Docs
Source language
English
Source publication/update
Link and content checked

When to read it

Understand browser-enforced resource restrictions, nonce/hash policies, and safe deployment testing.

Try this

On a staging page, test a report-only policy, inspect violations, and repair one incompatible script pattern.

Report-only policies require an HTTP response header; they cannot be supplied through a meta element.

Read the official source developer.mozilla.org
Publisher
Google / web.dev
Source language
English
Source publication/update
Link and content checked

When to read it

Connect image format, responsive sizing, and loading choices to actual transfer cost.

Try this

Add three width variants and accurate sizes to one image; compare selected files and transferred bytes at mobile and desktop widths.

Read the official source web.dev
Publisher
Cloudflare
Source language
English
Source publication/update
Link and content checked

When to read it

Understand the relationship between nearby database reads, replica lag, and session consistency.

Try this

In a test database, preserve a session bookmark across a write/read sequence and inspect serving-region metadata.

Replication needs the Sessions API. Writes still reach the primary; an unconstrained first read does not guarantee the latest database version.

Read the official source developers.cloudflare.com