Three example programs in Mapping the Atari crash or misbehave on most machines. Here is why each fails (an OS-A-only address, a misprinted opcode, two logic bugs), with tested fixes and general lessons.
Practical ways to find bugs in Atari BASIC: stopping and inspecting a running program, how CONT really resumes, finding the current line, listing variable names to catch typos, runtime-stack leaks, and profiling slow code.
A practical reference to every Atari BASIC and I/O error number, with what really triggers each one (tested on Atari BASIC revision C) and how to fix it.
Find and fix slow Atari code: Altirra's profiler modes, columns, counters and frame triggers, cycle counting with debugger commands, and measured 6502 optimisations including DMA.