> I am working in an organisation with one and a half developers. I am lobbying that the third of fourth developer concentrates on Dev Ops here. not sure you'r

> I am working in an organisation with one and a half developers. I am lobbying that the third of fourth developer concentrates on Dev Ops here. not sure you're doing the right thing here. you might want to consider hiring some kind of linux guy that can can do some basic devops. or maybe hire some devops contractor that can work with you on a part-time basis and "curate" some specific aspects of your operations. I've seen this done in the past: so you've got this consultant on retainer, and you tell them something like: "i've got this issue, can we do something about it? our constraints would be x y z" and the consultant would make 1-3 proposals (different approaches, different pricing levels, different ETAs etc) and then you agree on what gets done. The key aspect here is that a good devops consultant can get stuff done very quickly. > It is very important. Look at the back up/recovery procedures at your organisation. Has there ever been a fire drill? Are you sure the back ups are sound? Can you recover? What if data corruption occurred a week/month ago. Have you a back up of the uncorrupted data? Yes (to all questions). I ended up in working in heavily regulated environments. All the things you mentioned were not just niceties, but mandatory by legal requirements. > That is a very unsexy aspect of Dev Ops, and without somebody dedicated to the job, your backups will not be any of those things. That's basic system administration. Most devops engineers are former sysadmins.