Phrases in computing that might need retiring
181–190 of 291 posts
Re: Phrases in computing that might need retiring
#182Re: Phrases in computing that might need retiring
#183Sinister used to mean left handed. "A shambles" used to mean a slaughterhouse. Sanction used to mean allow, now it means not allow. It is fine for words to change meaning, even to their own opposite. Natural language has done that forever. Edit: you're all right, sanction has both meanings.
And autoantonyms are not good. They're confusing and lead to confusion.
Re: Phrases in computing that might need retiring
#184Earlier quoted context omitted.
Those are polar opposites. A button for 'disagree strongly' should upvote a comment. When Einstein and Niels Bohr 'strongly disagree' on quantum physics in 1927, they start a debate that makes both of them more enlightened. When a bullshit artist, who couldn't care less about the truth, hijack a discussion to make it all about Him (it's almost always a dude), everyone become dumber. "Moving along" is not enough becau…
> Him (it's almost always a dude) I'm curious as to how you know the sex of anonymous posters.
Re: Phrases in computing that might need retiring
#185Earlier quoted context omitted.
> The difference between Ops and DevOps isn't just in how the team is organised, but rather what the job itself consists of. Do you mean that a DevOps engineer's role and skillset is different from an operations engineer? And that hiring DevOps engineers instead of operations engineers is more in line with DevOps?
If we go by the original usage of the term, then yes, it's different skillsets between Ops and DevOps. You can't announce an Ops position with a DevOps title since the two are different by definition. However, even if we go by your definition that it is the same thing, then the "Dev" part is completely redundant and we should just call it "Ops", since it's by definition the same thing and it doesn't warrant a new tit…
Re: Phrases in computing that might need retiring
#186Earlier quoted context omitted.
> The difference between Ops and DevOps isn't just in how the team is organised, but rather what the job itself consists of. Do you mean that a DevOps engineer's role and skillset is different from an operations engineer? And that hiring DevOps engineers instead of operations engineers is more in line with DevOps?
If we go by the original usage of the term, then yes, it's different skillsets between Ops and DevOps. You can't announce an Ops position with a DevOps title since the two are different by definition. However, even if we go by your definition that it is the same thing, then the "Dev" part is completely redundant and we should just call it "Ops", since it's by definition the same thing and it doesn't warrant a new tit…
Re: Phrases in computing that might need retiring
#187Oh man, I wish most of this would go away. RE: Agile 'We have to find a new way to discuss the idea that maybe we focus on the working software and not on the organisational bureaucracy, and that way does not involve the word…' Which is rather hilarious, because the only people I ever hear use the word agile are the beaurocrats. RE: DevOps, I still don't know what it actually means. When I first heard the term, it wa…
I've been hired for multiple DevOps roles. For me it means Syadmin (happy Syadmin day btw) but also responsible for managing the plethora of AWS etc service, CI/CD pipelines, dealing with security audits, the occasional diving into code for back end stuff and being on hand for advice/comments.
Re: Phrases in computing that might need retiring
#188Earlier quoted context omitted.
> … "devops". It's really job title for "sysadmin … Uhm, that what it has become, but not what it ought to be. I define the «DevOps» as an experienced software engineer with the black belt in networking and system administration. It almost never works the other way round, though, and ex-sysadmins who choose to transition into a DevOps role as an exit path from editing configs in vi, remain as cantankerous and unhelpf…
I’ve also found a lot of devops to be generally unhelpful and adversarial as well. They seem to forget the developer part of the job title and don’t help the developers deliver value to the customer. Instead some devops teams just break things unannounced, make sweeping changes that leave everyone unhappy, require unnecessary extra steps for simple procedures, and remain passive or negative. I call those teams “devel…
Re: Phrases in computing that might need retiring
#189Earlier quoted context omitted.
Regarding DevOps, a major aim was to embed operational concerns into all stages of development. In that sense, it was a massive success; a developer cannot anymore just say "here's a binary that I made on my machine, make it work in production", throw it towards ops and sign off.
> Regarding DevOps, a major aim was to embed operational concerns into all stages of development. In that sense, it was a massive success... I strongly disagree here. If it was such a success, then why are there devops jobs at all ? If it was meant to signify that developers should share responsibility on deployments and integrations, what's the role of a "devops engineer"? It seems to me that self-proclaimed devops…
Re: Phrases in computing that might need retiring
#190Earlier quoted context omitted.
> Him (it's almost always a dude) I'm curious as to how you know the sex of anonymous posters.
On websites where it's anonymous I infer that from what I have seen since 25 years on websites where it's not, and from attitudes people have IRL.