• Kissaki@programming.dev
    link
    fedilink
    English
    arrow-up
    1
    ·
    6 hours ago

    I find a commit message describing consequential effect and intended goal/change more useful than technical details. And those are usually what the customer cares about. “function/action works again” “fix x by y” “introduce functionality x”.

    But as a developer I want to know what your commit did.

    I agree. I don’t see them as opposites or contradicting to pulling them. Either as a free information forward, or as a basis for describing it into something a customer understands, or into what is notable about a release.