Because, sadly, I more often than not do NOT have access to a debugger.
Learning how to write good debugging print messages is a skill. And nicely transfers to writing good debug log messages. Which makes diagnosing user issues much easier.
Because, sadly, I more often than not do NOT have access to a debugger.
Learning how to write good debugging print messages is a skill. And nicely transfers to writing good debug log messages. Which makes diagnosing user issues much easier.
I’m sorry, friend.
If any of those deployments included code you or your team wrote, I highly encourage archiving it in VCS somewhere, even if only internally.
Also do a formal write up of all the deployments and why each tech choice was made.
Your hard won knowledge and skills should be preserved somewhere.