Loduz_247@lemmy.world to Bluesky@lemmy.worldEnglish · 8 days agoA COBOL programmer explains that this migration is impossible without catastrophe unless they want to destroy social security.lemmy.worldimagemessage-square49fedilinkarrow-up1554arrow-down15
arrow-up1549arrow-down1imageA COBOL programmer explains that this migration is impossible without catastrophe unless they want to destroy social security.lemmy.worldLoduz_247@lemmy.world to Bluesky@lemmy.worldEnglish · 8 days agomessage-square49fedilink
minus-squareLovableSidekick@lemmy.worldlinkfedilinkEnglisharrow-up4·8 days agoEven as a software dev with decades of experience I still chronically underestimate projects by like half, and even I agree the idea of replacing the social security data processing system in under a year is ridiculous.
minus-squareFeyr@lemmy.worldlinkfedilinkarrow-up2·8 days agoI solved that estimation problem years ago. Now I double all my estimates and then add 20pct for slack
minus-squareLovableSidekick@lemmy.worldlinkfedilinkEnglisharrow-up2·8 days agoLOL I’ve heard a rule of thumb to double it, also to quadruple it, and one guy said multiply it by five.
minus-squaredebil@lemmy.worldlinkfedilinkarrow-up2·7 days agoI usually take a realistic estimate and multiply it by π.
Even as a software dev with decades of experience I still chronically underestimate projects by like half, and even I agree the idea of replacing the social security data processing system in under a year is ridiculous.
I solved that estimation problem years ago.
Now I double all my estimates and then add 20pct for slack
LOL I’ve heard a rule of thumb to double it, also to quadruple it, and one guy said multiply it by five.
I usually take a realistic estimate and multiply it by π.