Steve Weatherby

Steve Weatherby

Capability and Development Manager

About

With over 30 years of professional experience, I am a dedicated expert in learning and development and workplace health and safety (WHS) across diverse industries. My career spans the Aerospace Manufacturing, Transport and Logistics, and Nuclear/Radiopharmaceutical sectors, all of which are highly compliance-driven and demand the utmost in safety and competency.

Badges

Gemologist
Gemologist
Tastemaker
Tastemaker
Gone streaking
Gone streaking
Gone streaking 5
Gone streaking 5

Forums

Apple now sells $49.99 AI top-ups. How do you price AI features that cost you per use?

Even Apple has stopped pretending AI features are free to run. I'd like to hear how other small teams are handling the meter, because I don't think anyone has this solved.

On 9 November Apple started selling what it calls intelligence usage packs. Per 9to5Mac and iClarified's write-ups, it's a $49.99 one-time purchase, sold first inside Logic Pro, for people on a Creator Studio subscription who have hit their monthly limit on the AI features. Apple's own terms page for the packs says they don't renew, expire 12 months after purchase, are non-refundable except where the law requires, and, in the line I found most interesting, that Apple "does not guarantee that a specific amount of the Usage Packs will result in the same output." The reports say Siri and general Apple Intelligence features aren't covered, and that the monthly allowance itself isn't stated in numbers.

🧹 Lancetta 0.62.0 — what your coding agents leave behind

Lancetta 0.62.0 is out Maintenance now cleans up after your coding agents, and reads Claude Code's settings the way Claude Code does.

1. Storage

Codex installs that stopped halfway, old server releases, empty git folders, files ChatGPT copied out, build caches of ended sessions, Chrome's clones: each with what it frees and why it can go. Nothing a running program holds is offered, and it all goes to the Trash.

•

2mo ago

Is we'll refactor this later the biggest lie in software engineering?

Every dav team claims they care about clean code. Until a deadline hits. Then hacky workarounds become permanent architecture.

"Later" never comes. We just stack patch after patch on Friday afternoons, burning out the team on bugs that shouldn't exist in the first place.


At what point does "moving fast" just become bad management?

View more