For a project where multiple people are involved, I think it's better to split concerns. Deployment should be handled transparently and reproducible in a CI pipeline that the team members who are allowed to deploy have access to.
I don't care how you prefer to do things on your own, but if I were interviewing you for a senior position in a team with a handful of people, and you tell me that's how you want them to work, it would be an almost immediate NO HIRE.
OP's comment was "I do this for my Go project's" and goes on to describe how to use a (open source) library that even deploys to Hetzner.
So, either the commenter was trying to extend their practice to the point of the blog post or the comment was just expressing a preference when working by themselves, which has little to do with the content of the post.
If a deployment procedure is easy for non-DevOps people then by definition that also makes it friendly to programmers, so why wouldn't they do it if it they can do it properly with minimal effort. But I do realize that "properly" is doing a lot of work in this sentence.