HN user

harryruhr

154 karma
Posts7
Comments23
View on HN

DevOps originally means a method. It is not a position or a job. But that doesn't stop companies to say, there are looking for an "DevOps engineer" or similar. The definition is vague at best.

Some seem to think a "DevOps" is a developer who knows how to administrate servers (or vice versa), as a modern term for a general IT person who can do anything, from programming, to firewall administration and repairing the printer.

Another definition is more specific, DevOps means in this case: working with CI/CD tools, programming "infrastructure as code" (Terraform, Ansible, etc) and doing all things "agile". This job is mostly cloud focussed.

I have a clear statement in my profile at linkedin: I am a Unix/Linux sysadmin, not a "DevOps" or a "Cloud/AWS/Azure engineer". I am only doing traditional Unix/Linux sysadmin stuff.

There is not a day going by where a recruiter doesn't tell me "we are urgently looking for an experienced Linux sysadmin. Are you interested?"

YML is the exact reason I don't use Ansible anymore. Writing complex YML for simple tasks is a time burner.

After I discovered https://efs2.sh I switched over to this simple config management solution, which simply executes commands and scripts over ssh. It is so much simpler and faster (both in regards to creation and execution) than Ansible.

I mean very specifically that I'm a member of the community and I'm speaking about us.

I still have problem with the word "us". What do you mean by "community"? If you mean a certain organization you should say so.

In the Asperger's forum in which I participate we agreed, that everyone should speak only for themselve, which means to use "I" and "me" instead of "us" and "we".

Of course there is the autism spectrum. But it is a spectrum, it is not something that goes from mild to severe or where people have every symptom on the list in a certain degree. The spectrum is diverse - so it is wrong to make any general assumption about it.

(Note: I am not talking about "autism spectrum disorder" diagnosis according to DSM V or ICD-11. These diagnoses have a defined set of required symptoms. But the spectrum is far bigger than that).

Person with Asperger's here. The one thing that bothers me more than neurotypical people writing about autism without actually speaking with people with autism are people with autism who think that they can speak for the "community"

The first rule is always "if you have met one person with autism, you've met one person with autism". There is no "us" in the sense that we have something in common which distingushes us from all neurotypical people. So I don't agree with large parts of this article.

E.g I prefer person-first language, but that's not because I think, that autism is a pathology. I do identify myself with autism, but I don't think that this is the largest aspect of my personality, so I don't like to be called "autist" (as much as I don't want to be called "bigfoot" because I have 13 shoe size).

Yes, the author says, that there are people with autism who might disagree. But if he knows this, why is he talking about "we" and "us" all the time?

Docker has its use cases. But running everything possible in a docker container just for the sake of "dockerizing" seems a little bit excessive.

One must basically maintain a (more or less) complete userland environment for every application. The idea of shared libraries is taken to absurdity this way. It would be better to build all static.

Then there is the waste of resources. I'm sure with plenty GB RAM, TB of SSD space and GBit of bandwith available nowadays many people don't notice. But for what?

It's all relative, of course. But getting a signed package from the repo of the distro I'm using for years is something different than using a random image from hub.docker.com.

Docker for every application? If you create and maintain the Docker image or Dockerfile for every applucation yourself, you must have plenty of time. If you rely on public images from Docker Hub, you must have plenty of trust in the creators of those images.

NetBSD 9.0 6 years ago

There was an Article "Are the BSDs dying" (https://www.csoonline.com/article/3250653/is-the-bsd-os-dyin...) where it us said, that NetBSD has the lowest code quality of all BSD variants. It also finishes last when it comes to security updates.

To this day NetBSD doesn't deliver binary security updates in a timely manner. Not in the base system and not for packages. Even OpenBSD manages to do this nowadays. If there is even a patch at all, it is delivered in source form only. Users are supposed to build the binaries for themselves. That's anachronistic in the year 2020.

Building from source consumes not only time but also energy. When everyone talks about saving energy and reducing carbon footprint, source based systems where every user is supposed to build binaries from sources are a not only a waste of time but are also contributing to the climate crisis.