Of course, the most important aspect of fixing a problem, is writing down how you fixed it. Never know what a different, but similar problem might crop up again. Sometimes getting a quick answer, or having a human readable explanation for an error goes a long way. Often enough I’ll have complex logs entries that I can’t parse what the problem actually is, I can quick copy paste and get a normal people paragraph. Sometimes “os: error (-4) aborting” actually just means you forgot to change user permissions on your volume folder. In a perfect world, all program’s logs would be perfectly readable by machines and people at the same time. :P
Of course, the most important aspect of fixing a problem, is writing down how you fixed it. Never know what a different, but similar problem might crop up again. Sometimes getting a quick answer, or having a human readable explanation for an error goes a long way. Often enough I’ll have complex logs entries that I can’t parse what the problem actually is, I can quick copy paste and get a normal people paragraph. Sometimes “os: error (-4) aborting” actually just means you forgot to change user permissions on your volume folder. In a perfect world, all program’s logs would be perfectly readable by machines and people at the same time. :P