![]() ![]() ![]() My thinking is to make it as easy as possible for potential collaborators to understand the issue I am facing so that they have minimal work to do to understand what my goal is and what I am experiencing. If I then can't make further progress, I package that up with full recreate instructions and as much commentary as possible and make available as either a new defect report on Github (assuming I have a very high confidence that it should work) or else post it to pastebin with a forum post link explaining in as much detail the nature of the issue. then I study and test just that by itself. When I have a minimum problem, I then copy the project/code and actually remove the now commented out clutter so that what remains is a source file that is 100% the minimum to recreate the issue. This removes as much "chaff" from the puzzle as possible. I isolate (comment out) sections of logic until I have a minimum environment in which the problem manifests. When I hit problems like this my technique for debugging is slow and painfull. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |