ylai@lemmy.ml to Programming@programming.devEnglish · 4 months agoStudy finds 268% higher failure rates for Agile software projectswww.theregister.comexternal-linkmessage-square129fedilinkarrow-up11arrow-down10cross-posted to: becomeme@sh.itjust.works
arrow-up11arrow-down1external-linkStudy finds 268% higher failure rates for Agile software projectswww.theregister.comylai@lemmy.ml to Programming@programming.devEnglish · 4 months agomessage-square129fedilinkcross-posted to: becomeme@sh.itjust.works
minus-squareAwkwardLookMonkeyPuppet@lemmy.worldlinkfedilinkEnglisharrow-up0·4 months ago If documentation is the root cause of that then you should fix that by creating enough documentation to allow your software to continue to work Or create a better UI that doesn’t require so much documentation.
minus-squarepivot_root@lemmy.worldlinkfedilinkarrow-up0·edit-24 months agoThis assumes front-end development. If I had somebody tell me to use their API or backend software and they handed me a tarball instead of proper documentation, I’d look very far away from their company.
minus-squareAwkwardLookMonkeyPuppet@lemmy.worldlinkfedilinkEnglisharrow-up0·edit-24 months agoYeah, I almost added a clarification for that very point, and see now that I should have.
minus-squareMajorHavoc@programming.devlinkfedilinkarrow-up0·4 months ago Or create a better UI that doesn’t require so much documentation. Sacrilege!! /s
Or create a better UI that doesn’t require so much documentation.
This assumes front-end development. If I had somebody tell me to use their API or backend software and they handed me a tarball instead of proper documentation, I’d look very far away from their company.
Yeah, I almost added a clarification for that very point, and see now that I should have.
Sacrilege!! /s