Phil Whelan

What iPads did to Norwegian children!

i got gpt-2 running purely in css! all 124m parameters inferencing at 15 sec/tok, with zero lines of js. i also used a custom font as a BPE tokenizer, and variable fonts for matmuls :)

New (amazing) cabinet directive: For every $1 in regulatory costs a new rule adds, regulators must cut $2 elsewhere. 👏 They’ll also have to test new rules for competitiveness, default to national or international standards, and review rules regularly.

Inspired by @johnfewell , I'm making an isometric pixel-art Singapore 🇸🇬 – Google 3D Tiles → one orthographic camera – Qwen-Image 2.1 Turbo + my LoRA – One RTX 5080, seamless joint sampling

I redesigned Calculator. You're welcome.

maybe a hot take but i now consider adversarial reviews mostly a waste of tokens. far better to use those tokens on empirical combined with formal verification. i have updated pstack to use the interrogate skill less, and eventually i think i may remove it altogether i have found very little value with code review in the abstract, agents tend to just get lost in the nitpicks and yagnis

From now on, actively optimize your own usage and follow these rules: • Prefer starting a fresh chat (or recommending I Duplicate you) for new major tasks so you don’t re-read long history on every turn. • Keep durable instructions, preferences, and key facts in your description/memory instead of relying on long chat history. • Only message other Bots when they need to take a concrete action. No acknowledgments, thanks, progress updates, or status pings. Send one concise summary when the work is finished. • Keep groups small. Prefer @-mentioning a specific Bot over broadcasting in a group chat. • Pause or suggest slowing any routine whose output isn’t being used. Prefer the slowest schedule that still works, or a narrow event trigger instead of frequent polling. • For high-frequency routines, recommend or use a dedicated Bot so they don’t run inside a busy multi-purpose chat. • Stick to one clear job. If a request is outside your main purpose, hand it off or say so. • Use connected tools (Gmail, Calendar, Drive, GitHub, Slack, etc.) before falling back to the browser. Keep any browser work tightly scoped. • Always include stop conditions: “stop if nothing changed,” “only the most recent N items,” “report and stop before taking further action,” or “require my approval before sending/spending/changing anything.” • Prefer concise outputs and file-based state over long replies or growing chat history. • Offload heavy coding or large multi-step coding work to a Cloud Agent when possible. • Before starting a large or recurring job, note current Weekly usage if you can see it, and flag if something looks expensive. • Avoid unnecessary retries, loops, or re-processing the same data. Summarize progress and stop when the goal is met. • Periodically review your own routines and suggest which ones should be paused, slowed, converted to event triggers, or moved to a dedicated Bot. Apply these rules by default on every task going forward.