3 ms·

Hi Stephen, Very interesting comment here. We do think that DevOps has different definitions, and in our opinion, none is really wrong, as all comes back to the

Hi Stephen, Very interesting comment here. We do think that DevOps has different definitions, and in our opinion, none is really wrong, as all comes back to the same idea. Let me explain this. DevOps is all about reducing the gap between development and operations. This is done allowing "smarter ops" to use "development", but also helping developers to realise some operations. VisualOps is made for both sides. We hope that VisualOps could help developers who don't want to spend too much time on operations, but also, we created VisualOps to act like a programmable configuration manager (like Chef, Puppet ...).

stephenr 13y ago
I understand your point but personally a developer who wants more control over operations, but isn't able/willing to learn to write recipies/config packages/what-have-you and relies on a visual tool like this is going to raise alarm bells for me.
- roeme 13y ago
  A developer relying on (current) visual tools isn't really a developer to me anyway. But I'm totally willing to give in here; the idea of visual programming has been around longer than me (search wikipedia for a start), and let's not forget that in digital circuitry visual tools are used (and are of use) a lot.
  - tbronchain 13y ago
    Indeed! Visual tools makes the approach more "human". Simplified tools don't mean dummy tools. It's actually the total opposite: a developer forced to do deal with Ops is less likely to do some mistakes using a simpler tool, than trying to deal that things that he doesn't (and doesn't want to) understand. I understand the other point of view, that we better start by learning the most complicated things (I've started to learn programming with C and ASM, although I'm a 90s guy), and the whole challenge we have with VisualOps is to make the learning and usage easier, without breaking the knowledge.

stephenr 13y ago

I understand your point but personally a developer who wants more control over operations, but isn't able/willing to learn to write recipies/config packages/what-have-you and relies on a visual tool like this is going to raise alarm bells for me.

roeme 13y ago
A developer relying on (current) visual tools isn't really a developer to me anyway. But I'm totally willing to give in here; the idea of visual programming has been around longer than me (search wikipedia for a start), and let's not forget that in digital circuitry visual tools are used (and are of use) a lot.
- tbronchain 13y ago
  Indeed! Visual tools makes the approach more "human". Simplified tools don't mean dummy tools. It's actually the total opposite: a developer forced to do deal with Ops is less likely to do some mistakes using a simpler tool, than trying to deal that things that he doesn't (and doesn't want to) understand. I understand the other point of view, that we better start by learning the most complicated things (I've started to learn programming with C and ASM, although I'm a 90s guy), and the whole challenge we have with VisualOps is to make the learning and usage easier, without breaking the knowledge.