for small teams (mostly solo hackers) yes the run-print-change works;

for anything bigger, when code #reasonably# grows and span among 10+ developers, break-debug-change is much more productive than log.PrintLn all over the palces and figuring out myself, or interrupt my colleague to explain sth to me.