← Back to context Comment by mgfist 13 hours ago Which circles back to why it's important for leadership to tackle this 6 comments mgfist Reply PUSH_AX 13 hours ago Yes, but not in the form of commit messages, the parent comment described things better suited to jira tickets, documentation etc.It feels like we're trying really hard to stretch the utility of commit messages here... macintux 12 hours ago Mainly I was pushing back on: the code is the "truth"I don't feel that is an accurate statement for any complex system. PUSH_AX 12 hours ago I don't like complex systems, and I work hard not to create them. 2 replies → cratermoon 10 hours ago You'll at least need the discipline to include the ticket ID in the message. Links to documentation are ok, but they will likely rot and even if they don't the content may change such that it no longer accurately reflects the commit changes.
PUSH_AX 13 hours ago Yes, but not in the form of commit messages, the parent comment described things better suited to jira tickets, documentation etc.It feels like we're trying really hard to stretch the utility of commit messages here... macintux 12 hours ago Mainly I was pushing back on: the code is the "truth"I don't feel that is an accurate statement for any complex system. PUSH_AX 12 hours ago I don't like complex systems, and I work hard not to create them. 2 replies → cratermoon 10 hours ago You'll at least need the discipline to include the ticket ID in the message. Links to documentation are ok, but they will likely rot and even if they don't the content may change such that it no longer accurately reflects the commit changes.
macintux 12 hours ago Mainly I was pushing back on: the code is the "truth"I don't feel that is an accurate statement for any complex system. PUSH_AX 12 hours ago I don't like complex systems, and I work hard not to create them. 2 replies →
cratermoon 10 hours ago You'll at least need the discipline to include the ticket ID in the message. Links to documentation are ok, but they will likely rot and even if they don't the content may change such that it no longer accurately reflects the commit changes.
Yes, but not in the form of commit messages, the parent comment described things better suited to jira tickets, documentation etc.
It feels like we're trying really hard to stretch the utility of commit messages here...
Mainly I was pushing back on: the code is the "truth"
I don't feel that is an accurate statement for any complex system.
I don't like complex systems, and I work hard not to create them.
2 replies →
You'll at least need the discipline to include the ticket ID in the message. Links to documentation are ok, but they will likely rot and even if they don't the content may change such that it no longer accurately reflects the commit changes.