Learn how we tracked a performance bottleneck to a 15-year-old Git function and fixed it, leading to enhanced efficiency that supports more robust backup strategies and can reduce risk.
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.
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.