To me, DevOps has absolutely nothing to do with helping to deploy code any faster or automating anything, although that's frequently the end result of a proper development and support culture. DevOps is a culture that more readily allows information and expertise to flow more easily and, if nothing else, is the necessary culture of communication between departments so that people don't have to redevelop the wheel and are much more aware of insitu problems and changes in requirements. Heh... to me, the clean version of what "DEVOPS" stands for is "Doing Everything to Validate Other People's Stuff".
Much like suggested in the article, I'm a bit of an "old timer" and I don't understand what all the buzz is about. DevOps is the type of culture that SHOULD ALREADY EXIST in every company, regardless of size. Companies that have "silos" are doomed to repeating problems and having either very bad releases or very slow releases and both will likely entail a shedload of rework or failures at the customer level. Shoot... for that matter, the very concept of this forum is a type of DevOps where what seem like incredibly complex problems are frequently solved quickly and easily as well as providing insight on alternatives and speculation on what's really needed instead of just what was asked for. Good forums are actually the epitome of DevOps and a similar model is very frequently the model that people should shoot for as a culture for their company and, yes, it should be across ALL departments. After all, all the departments work for the same thing... to make the company successful and to keep those paychecks coming in.
is pronounced ree-bar and is a Modenism for R
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
If you think its expensive to hire a professional to do the job, wait until you hire an amateur. -- Red Adair
How to post code problemsHow to post performance problemsForum FAQs