I can imagine a big Rust project where there is person who does nothing but updating dependencies. Trivial changes in the code he will do but most is delegated to the developers. The job includes:
* Analyze dependency updates for breaking and performance impacts
* Coordinate the cleanup of deprecated API use
* Feedback to upstream
* Resolving integration issues (usually by delegation and controlling)
This guy does not write significant amounts of code but will still create lots of commits.
As near as I can tell, the post is a response to comments in reply to a previous post which essentially states that the _existence of cargo_ is bad because there are bad libraries available.
This post further asserts that folks who like the fact that libraries are easily available are "not very good at something being discussed" and have "Peter Principled" themselves. It also states that they are, "almost rational."
What you're describing is an under-performer, or perhaps someone who is working specifically in a maintenance capacity (likely with a title that reflects that!). I don't think that is what the original post is talking about, but perhaps I have misread.
I guess this comment being downvoted indicates that this perspective is more widespread than I thought - can someone please explain to me how you would go about structuring a project with zero software development using libraries available via your preferred programming language's package manager?
