[Info-vax] Should VSI create a modern day VMS applications book ?

[Bill Gunshannon]

On 08/21/2018 10:41 PM, Arne Vajhøj wrote:
> On 8/21/2018 9:50 PM, Kerry Main wrote:
>>> -----Original Message-----
>>> From: Info-vax <info-vax-bounces at rbnsn.com> On Behalf Of Arne Vajhøj
>>> via Info-vax
>>> Sent: August 19, 2018 10:37 PM
>>> To: info-vax at rbnsn.com
>>> Cc: Arne Vajhøj <arne at vajhoej.dk>
>>> Subject: Re: [Info-vax] Should VSI create a modern day VMS applications
>>> book ?
>>>
>>> On 8/19/2018 10:04 PM, Kerry Main wrote:
>>>>> From: Info-vax <info-vax-bounces at rbnsn.com> On Behalf Of Simon
>>>>> Clubley
>>>>> Sent: August 19, 2018 8:07 PM
>>>>> On 2018-08-18, Kerry Main <kemain.nospam at gmail.com> wrote:
>>>>>>
>>>>>> DevOps needs to be defined because in most large enterprises I have
>>>>>> been in the last 10 years (including Federal Govt), this concept is
>>>>>> just a water cooler discussion topic. Integrating OPS and Developer
>>>>>> groups is just way to hard as they live in different worlds and
>>>>>> seldom discuss common strategies.
>>>>>
>>>>> The best typo I've ever seen for "DevOps" is "DevOops". :-)
>>>>>
>>>>> I think that sums up very nicely the results if only you try to be
>>>>> buzzword compliant instead of actually implementing the concept.
>>>>
>>>> Those that try to implement the DevOps concept are either part of a
>>>> small office or have no experience in the culture of medium to large
>>>> IT environments.
>>>
>>> Companies known to use DevOps include:
>>>
>>> Walmart
>>> Target
>>> Norstrom
>>> Apple
>>> Starbucks
>>>
>>> United Airlines
>>> Hertz
>>>
>>> Amazon
>>> Facebook
>>> LinkedIn
>>> Netflix
>>> Sony Pictures
>>>
>>> Adobe
>>>
>>> GM Financial
>>> Rabobank
>>> Key Bank
>>> Fidelity Investments
>>>
>>> USCBP
>>> NASA
>>>
>>> I would think they have experience in the culture of large IT.
> 
>> While there may be a few exceptions, many large companies state "they
>> are doing XYZ" (insert latest buzz word), but when one digs deeper,
>> you find it is only a very small component of their real Operations
>> environment that is actually doing this. In many cases, these
>> examples are POC's and/or pilot projects.
> Many on the above list has published details about what they do.
> 
> So that does not seem to be the case.
> 
>> Getting even 5 different App groups and Operations groups in the
>> same room for a meeting is a big challenge. Getting them all to agree 
>> on a
>> common way of doing things is the equivalent of scaling Mt Everest.
> 
> Maybe.
> 
> But the companies that can change make money and those
> that are stuck in the old ways goes bankrupt.

Yet another person that assumes new better - old bad.  That's the
attitude that has done the most damage to VMS, you know.

I know of places that changed and went bankrupt, too.  Change for
changes sake is folly.  Change should only bne done when the change
brings something of value to the table.  (Hear that OOP and Agile?)

bill