← back NO. #9c2a9b85

NO.: #9c2a9b85
Topic: OTHER
Source: Simon Willison
Published: 2026-04-25 04:13:36
Importance: ★ 6/10 — radar 60
Original: simonwillison.net/2026/Apr/25/gpt-5-5-prompting-guide/#atom-everything

GPT-5.5 Prompting Guide Pushes Fresh Prompt Baselines

This post highlights OpenAI’s GPT-5.5 prompting guidance and the key message is that GPT-5.5 should be treated as a new model family, not a drop-in swap for older GPT-5 variants. For indie developers, the practical takeaway is to re-baseline prompts, test tool flows again, and add brief progress updates for long-running agentic tasks to improve product UX.

[ KEY POINTS ]

OpenAI recommends rebuilding from a minimal prompt baseline instead of reusing prompts tuned for GPT-5.2 or GPT-5.4.
A short user-visible progress update before multi-step tool use is presented as a simple UX improvement for long-running tasks.
For small teams, migration cost is less about changing the model string and more about prompt retuning, regression testing, and validating tool/output behavior.

Originalsimonwillison.net/2026/Apr/25/gpt-5-5-prompting-guide/#atom-everythingRead original →

// related

#0001
#0001Other GeekNews10 hours ago
`Bambu Studio` Faces Broad AGPLv3 Compliance Challenge
40radar
Bambu Studio3D printing slicer — based on PrusaSlicer
Copyleft obligations can reach bundled dynamic libraries and install info. If you fork AGPLv3 software, partial source drops are not enough.
- AGPLv3 Corresponding Source covers code needed to generate, install, run, and modify the work, not just visible app changes.
- A tightly coupled proprietary networking library may need source disclosure if it is dynamically linked into the modified app.
- Forking strong-copyleft projects for commercial software demands release-process checks before binaries ship.
Source: news.hada.io/topic?id=29694Read original →
FIG-0011:1
40radar
FIG-0011:1
#0002
#0002Other GeekNews10 hours ago
What's New in `Chrome` from Google I/O 2026
50radar
The web is shifting from human clicks to agent-driven browsing and AI-assisted development. Worth tracking before specs turn into defaults.
- Paul Kinlan, who leads Chrome DevRel, framed the last 6 months as a fast reset for web development workflows.
- One axis is preparing sites for agents that browse on users' behalf. Structured, machine-readable UX will matter more.
- Another axis is developer tooling. Chrome is positioning DevTools around AI-assisted debugging and building, not just inspection.
- The source is short and lacks API-level details, so this is a watchlist item rather than something to implement today.
Source: news.hada.io/topic?id=29693Read original →
FIG-0021:1
50radar
FIG-0021:1
#0003
#0003Other GeekNews13 hours ago
JavaScript Debloating: Complexity, Libraries, and the WASM Trade-off
40radar
Small browser UIs can become heavy fast. WebAssembly helps, but async bridging to the JavaScript event loop keeps the payoff situational.
- Nested syntax and callbacks make JavaScript complexity grow quickly; bundle size is often a design outcome, not just tooling noise.
- Small UI surfaces can still pull in many libraries. Dependency defaults deserve review before reaching for another package.
- WebAssembly opens the browser to other languages, but Pyodide-style async event-loop integration adds real coordination cost.
Source: news.hada.io/topic?id=29675Read original →
FIG-0031:1
40radar
FIG-0031:1

GPT-5.5 Prompting Guide Pushes Fresh Prompt Baselines

// related

`Bambu Studio` Faces Broad AGPLv3 Compliance Challenge

What's New in `Chrome` from Google I/O 2026

JavaScript Debloating: Complexity, Libraries, and the WASM Trade-off