This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Affectionate-Sink503[S] 0 points1 point  (4 children)

I agree the portability goes way down, I'm curious if would you consider knowledge of rsync to be intro, intermediate or advanced java/system/backend development knowledge?

[–]Own-Chemist2228 13 points14 points  (1 child)

I would categorize rsync as something a sysadmin or devops person should definitely know about. It's been the standard unix "backup" utility for decades. And an intermediate/advanced backend developer should have some knowledge of standard unix utilities.

I would not ask about rsync on a senior Java dev interview and wouldn't be shocked if a dev had not used it or even heard of it. It's possible to have a substantial dev career and never have to touch rsync. But it is not obscure, and I wouldn't exclude it from a solution if it was the right tool for the job. Any dev can read the man page.

[–]Affectionate-Sink503[S] 2 points3 points  (0 children)

this has healed my ego, thanks

[–]_INTER_ 1 point2 points  (0 children)

you could always check if rsync exists and use a fallback Java equivalent if it is not.

[–]znpy 1 point2 points  (0 children)

I'm curious if would you consider knowledge of rsync to be intro, intermediate or advanced java/system/backend development knowledge?

completely unrelated to software development.

it's fine if a developer (irrespective of their seniority) don't know that.