1) The Debugger and the program being debugged -- are effectively running in the same execution environment; the same memory space (both programs are different ranges of the same memory and both can access each other's memory without restrictions, but only one can be running at one time (single stepping swaps control (for an instant) and then swaps it back again, as does running under the debugger until a breakpoint is hit -- as there are absolutely NO threads (concurrent code execution paths) in this environment!)
If the debugged program crashes for any reason, for example, enters an infinite loop and/or doesn't yield control back to the debugger via executing a RET instruction -- then the entire PC (if DOS is running directly on hardware (as opposed to under Windows and/or a VM) will crash, AKA "lock-up"! Powering the entire machine on and off is now necessary to reboot it! (Dave Letterman, many years ago, in response to the then-feared upcoming Y2K disaster: "Just Reboot!")
2) While this mode of programming is hard, laborious, counter-intuitive, slow, and error-prone(!) -- it should also be lauded, praised -- because equal-and-oppositely, whoever is programming at this level has effectively gotten rid of 99.99% of the "tech stack" dependencies -- the code written by other programmers in compilers, operating systems, programing languages, programming environments, libraries, frameworks, tech stacks, other software components, etc., etc.
Oh sure, there's still DOS in the background... but the DOS code/API fits into like what, like 32KB? (That's Kilobytes with a 'K', not Megabytes or Gigabytes... several orders of magnitude smaller...)
And a pure assembly low-level programmer -- does not even need to depend/rely on DOS or BIOS calls... they can effectively get rid of those too by writing their own hardware drivers... OS developers that write in Assembly typically do this or something like this...
Anyway, an excellent article!