▲ | hinkley a day ago | ||||||||||||||||
Once a bug is closed the value of those logs starts to decay. And the fact is that we get punished for working on things that aren’t in the sprint, and working on “done done” stories is one of those ways. Even if you want to clean up your mess, there’s incentive not to. And many of us very clearly don’t like to clean up our own messes, so a ready excuse gets them out of the conversation about a task they don’t want to be voluntold to do. | |||||||||||||||||
▲ | hnlmorg 21 hours ago | parent | next [-] | ||||||||||||||||
In DevOps (et al) the value of those logs doesn’t decay in the same way it does in pure dev. Also, as I pointed out elsewhere, modern observability platforms enable a way to have those debug logs available as an archive that can be optionally ingested after an incident but without filling up your regular quota of indexed logs. Thus giving you the best of both worlds (all logging but without the expense and flooding your daily logs with debug messages) | |||||||||||||||||
| |||||||||||||||||
▲ | pstuart a day ago | parent | prev [-] | ||||||||||||||||
My approach for this is to add dev logging IN ALL CAPS so that it stands out as ugly and "need adjusting", which is to delete it before merging to main. | |||||||||||||||||
|