chaospatterns@lemmy.world to Programming@programming.devEnglish · 2 days agoHow GitLab decreased repo backup times from 48 hours to 41 minutes with a fix to Gitabout.gitlab.comexternal-linkmessage-square25linkfedilinkarrow-up1185arrow-down13
arrow-up1182arrow-down1external-linkHow GitLab decreased repo backup times from 48 hours to 41 minutes with a fix to Gitabout.gitlab.comchaospatterns@lemmy.world to Programming@programming.devEnglish · 2 days agomessage-square25linkfedilink
minus-squareFizzyOrange@programming.devlinkfedilinkarrow-up7arrow-down1·2 days agoThere isn’t. This is the colloquial use of “exponentially” which is very obvious from the context.
minus-squaredrspod@lemmy.mllinkfedilinkarrow-up0arrow-down1·2 days agoOn a technical blog post by a software company about the details of solving an algorithmic complexity problem? Careless, and showing that the author does not understand technical communication, where precision is of great importance.
minus-squareFizzyOrange@programming.devlinkfedilinkarrow-up2arrow-down2·2 days agoThis is fine precisely because it is a blog post. If it was a scientific paper… sure maybe they shouldn’t say that. But the meaning is abundantly clear from the context. There is no ambiguity.
minus-squareFizzyOrange@programming.devlinkfedilinkarrow-up1arrow-down1·19 hours agoBecause I can read? Lol ok.
There isn’t. This is the colloquial use of “exponentially” which is very obvious from the context.
On a technical blog post by a software company about the details of solving an algorithmic complexity problem?
Careless, and showing that the author does not understand technical communication, where precision is of great importance.
This is fine precisely because it is a blog post. If it was a scientific paper… sure maybe they shouldn’t say that. But the meaning is abundantly clear from the context. There is no ambiguity.
Enjoy being mediocre.
Because I can read? Lol ok.