What comes after DevOps?
 

Hello,
The DevOps is a high demand skill, but what comes after DevOps? I read this article and saw something like the SecOps and TechOps.
What is TechOps?
Anyone agree with VirtOps?


Thank you.

Architect is another option

Hello,
Thank you so much for your reply.
Architect?

Meaningless buzzwords.

Hello,
Why?

DEVOPS is an organizational structure for optimizing development. It is not a product or knowledge base, and although the name is new the structure is one of the original startup development structures and is quite old.

I would focus on the skills, rather than the buzzwords.

I don't understand your question. Because it looks good in CVs.

Again, these are pretty much made up buzzwords/titles. Much like this thread:
https://www.linuxquestions.org/quest...re-4175690890/

...not sure what you're wanting to hear. There is no job that is, "If you know x,y,z you will ABSOLUTELY be successful". Just isn't, anywhere, in any field. You need to develop logical thinking skills, be able to research, and find things out for yourself. Asking others to do such things for you won't get you far. Rather than asking what the 'high demand' skills are, it would appear you need to focus on basics first, before moving forward.

https://www.linuxquestions.org/quest...os-4175684055/
https://www.linuxquestions.org/quest...em-4175683407/
https://www.linuxquestions.org/quest...er-4175683989/
https://www.linuxquestions.org/quest...st-4175688374/

Dev writes the code and builds the system, ops runs the servers and such. Architect does designed fro a higher big picture level.

Okay ... okay ... okay ... there are always "new buzzwords." And, those "buzzwords" just might be invented for use in resumes and job descriptions. In time, you will become jaded-enough to expect such things, but when you are just starting out as (of course) "a newcomer in today's market," you might well be so unsure of your own abilities that you're tempted to "load your resume" with these buzzwords.

Undoubtedly, much of the impetus for the very invention of these terms dates back to the times when "search-engine optimization" was supposed to be The Next Big Thing.™ If you could figure out what keywords the search-bot was looking for, and loaded your web-page with them, then somehow your web-site would float above the millions.

The unfortunate reality for any hiring company with any sort of internet exposure is that "junk mail" gushes in. Filters are used to help with that. But, companies quickly learn which terms produce useful winnowing of the flood and which ones don't. And, I would quickly advise that "---ops" is now dead. (In fact, it might be a strike against you.)

Because – "in real life, nobody knows what-the-hell such terms actually mean." Everybody's heard of them, so everybody uses them, but nobody uses them to mean the same thing.

All right – your resume made it through the filter, then the HR Department scanners flagged it for my attention, and: "here you are – you have ten seconds."

Here's my advice: "Just tell me where you've worked, and what you did there." What I need to sense ... and I've got about ten seconds to do this ... is whether-or-not you might have skills that are applicable to the situation that I am hiring for. "Please, do not over-think this." You are a salesman. "Why do I want to buy your Fuller Brushes?" Present a simple and easily-understandable sales pitch which doesn't convey the idea that you're "just spamming me."

You're talking about career progression?

What comes after dev-ops is dev.

There are many ways that you can find a career in computing: software development, technical operations and support, systems analysis, software design and project planning, quality assurance ... the list goes on forever, and doesn't lend itself too well to buzzwords.

For instance – you might love to be a "source-code wrangler." There's nothing about "git" that you don't know. Or, you might be more interested in people ... stakeholders, users. You might be the sort of person who loves solving problems and who prides himself that "no bug gets out of here alive." You might like fiddling with hardware. Maybe a "network closet" is where you like to be, and you use a soldering iron like a pen. You might most-comfortably think in abstractions. You might dig very-high-level architectures. You might be a strategist, or you might be a tactician.

The very nicest thing about the business is that you can move around to different areas of interest as your interests change. I have personally written many hundreds of thousands of lines of original source code ... but I don't do much of that anymore. And, so on. Somehow, I've spent a lifetime at it, and it still engages me, albeit now in different ways.

Think about what aspect of the business now interests you the most, such that you could personally enjoy doing an excellent job of it. Knowing that you don't have to keep doing that forever. But, whatever you next decide to do, "do an excellent job of it." Your reputation will precede you. Have pride in everything you do.

Hello,
Excuse me for saying this, you are here to just write something and increase your "Posts:" section in your profile.
You said that some of my posts are funny or something. OK, about https://www.linuxquestions.org/quest...em-4175683407/
, can you tell me how you check your system? I must tell you that, it is somewhat impossible to detect some malware and etc, because some of them are completely hidden.
I'm not here to make up buzzwords/titles, but you are and as you see, I asked my question in the "Linux - General" section.

I disagree with you on this. TBone did not "make up" any buzzwords, and had no need to increase his posts count. Buzzwords are generally coined by advertising agents for vendors to increase sales, although some have been generated by professors or journalists.

Malware can hide, but can be detected by either behavior or clean scanning (after boot from a removable device and scanning with the appropriate detection). Cleaning malware is a different matter that I will not discuss or recommend.

We were discussing proprietary blobs and vulnerability, not malware. And those only as they relate to the buzzword DEVOPS. That term was coined recently, but the organizational system it describes is almost as old as private computer development companies. (So, it has been around since at least the 1960s.)

As for what comes after it, most likely a newer buzzword. But if you mean for a company, after the organizational system: generally over management, vertical reorganization, inefficiency, increased prices, short term success and gradual decline. If you mean in personal development, DEVOPS is not really a skill, it is an environment in which you express a skill. The skills you learn are ones that should apply in many environments, including in a DEVOPS structure.

I can find or draw you organizational charts expressing the structure differences if you wish.

Not even sure what this means, or why it would matter to anyone. However, it is pretty ironic that YOU say others are posting just for more posts (?), when you post over and over, and ask very similar questions.
Did you not read or understand the things given to you there?? As you were told, you apparently have a good deal to learn. And since you 'must tell me' about such insidious malware and how it's hidden/invisible, why don't YOU post what you would do, since you're apparently claiming to be an expert by disputing everything others have told you (on more than one occasion).
Didn't say you made them up, but you apparently just don't understand what you're being told. There is no 'programming language with bright future'. There is no 'path after devops'. They are meaningless terms, and it's been explained to you clearly. A company can use any language they want, for as long as they want. They can call people whatever title they want, and say "If you want job XXX, then you HAVE TO DO YYY and ZZZ first". Other companies may not. Do you understand that???

You keep posting articles, then seem to post here, asking us to validate what you think. Why? Want to move ahead? Then *LEARN* what you're doing, and quit going after buzzwords. There is no 100% 'path' to advancement. Learn and do a good job and you'll move ahead; don't listen to anyone else and not learn, and you'll move in a different direction.