Tech
How to Debug Python Code You Didn't Write
You open the repository. Nobody who wrote it still works here. There are no tests. The one README file describes a feature that got deleted two years ago. And something is broken in production.
Welcome to the job.
Debugging code somebody else wrote is one of the least talked-about skills in software engineering, yet most of us spend more time doing it than writing anything fresh. The hard part is that you have no mental map of how the thing works. Python makes this trickier than most langu...
Read the full discussion on Dev.to
This article was aggregated from Dev.to. Click to join the conversation.
View on Dev.to