3 ms·
For my server work, I almost exclusively use print(). That’s mainly because I don’t spend much time there, and it’s not worth it for me to spend the time settin
by ChrisMarshallNY 4y ago
For my server work, I almost exclusively use print(). That’s mainly because I don’t spend much time there, and it’s not worth it for me to spend the time setting up xdebug, or whatever. It’s worked fine. I’ve written some pretty huge systems, that way.
For my client (native Apple) work, I use breakpoints all the time, but they are not always that useful; especially when working in a threaded/time-critical environment. I often add print() statements, to display aggregate and calculation results. Swift has a fairly nice reflection system, that can be used to rabbithole a lot of information.
When running in debug mode, my console spews out all kinds of stuff. It can be a firehose, so it works best, coupled with breakpoints.
Been debugging for over 35 years. I’ve learned use whatever tools are available, but my most useful tool is in my noggin.
Those of us "of a certain age," that have done firmware development, may remember ICEs (In-Circuit Emulators). These would probably be impossible to do, these days, but they were about the best debugging tool you could ever hope to have.