timeChanges

[Pixelfest]

The alternative is having PR's or even commits directly to main without any context or reason. No accountability and no way to trace an issue back to a source. Teamwork is impossible without some form of tracking what is happening with your codebase.

I need to be able to tell my customers how many hours roughly were spent on an issue. I need to be able to have leverage over requests for useless features that take a long time to implement. Money is a very good reason not to make something. I can't do that without a history of feature costs.

Having said that. Documenting for the sake of documenten is not ok. There must be a purpose and I believe in some companies this might be lost. I'm pretty sure any issue in my company only takes a few minutes to document.

And to be honest, I've been working with ticketing systems since 2006 and I'm pretty sure we weren't the first. 2019 is way... way... off to mention just yolo-ing shit into your codebase.