Hacker News new | ask | show | jobs
by fragmede 815 days ago
You are erroneously invoking a fallacy that does not apply here. A qualified DevOps engineer will be able to pick up GoLang. I didn't claim that a DevOps engineer already knows GoLang, but that they're able to pick it up. If I'd say only true devops engineer's already know golang, you'd have a point.

Unfortunately, you missed it too.
1 comments
rglullis 813 days ago
> qualified DevOps engineer

Which is not something that one professional needs to be in order to have to perform some duties that fall within the role of DevOps.

I am, first and foremost, an application developer using Python and JavaScript. But I also have extensive experience:

- setting up Docker Swarm clusters

- managing cloud infrastructure with Terraform

- configuring deployments with Ansible

- setting up observability on Prometheus/Loki/Grafana stack

- putting up together CI servers for my team

- setting up backup/restore infrastructure.

- deploying and managing internal OSS tools for a dev/data team: Gitea, Taiga, Redash, Apache Airflow, Baserow...

These are all tasks that could be part of a "DevOps Engineer" job description, but if you tell me that "to work with a primarily Golang dev team you need to pick up Golang", I'd be assuming that you are not looking primarily for a DevOps Engineer, but a Go Developer who can do DevOps. And because I am not a Go Developer, you'd be putting my whole application on the bottom of the Stack.

link
fragmede 811 days ago
Your point, that doing this ad-hoc in go results in a half-baked shitty reimplementation of ansible/chef/fabric/whatever, was well made. I totally agree with it.

My point was, is that the DevOps person needs to be smart enough to pick up Go, which I'm sure you are.

Any hiring manager that puts your whole application on the bottom of the stack because of a lack of experience isn't a good hiring manager and isn't worth your time.

link