@wxcafe Do some companies foster behavior where you're "trans-role"? Yeah, sure. Some folks like doing that, but not me.
There's myriad of titles in order to differentiate roles.
Many companies these days say "DevOps" to target a person knowing certain practices (communication, automation, business perspective).
Then in the job description they point out requirements. Most of the time you can see by looking at that description of what kind of person they look for.
If you see everything from ninja warrior to nuclear physicist then apparently, something's wrong. But that's for each individual to decide.
@wxcafe And I think I shouldn't emphasize on how poor of a job average dev would do when setting up an infrastructure :-)
@wxcafe my point, devops being person doing dev and ops work is bullshit. Devops is the process IMHO.
When something needs to be coded, I still reach for the dev as it would take him less time to do something than me. Saves my patience as well as company money (my time = company money).
@wxcafe as an ops person that is now working under "devops engineer" title I can still say I'm full blown ops. But now I do more communication with devs and am prioritizing business needs better.
As a pure Ops I wans't even aware of such needs, I only solved technical issues as they came. Seeing the whole picture I can say that it allows for better long-term decisions and allows presenting the case when you need budget and stuff like that.
@angristan It's still fun if you come up with funny responses :-D
Systemd is pretty good though. Nothing to joke about there. Snaps are decent as well... :-)
@pskosinski goodreads, yes.
social.tomica.me is one server in the network