Ask HN: Can no-code automation and no-code in general help DevOps?
4 comments
Do you see any room for automation?
I would not take GP's word as general sentiments in DevOps. We have plenty of automation and "low-code" if you look at it right. That's really the name of the game. It's mostly scripting and config, while tools are programmed. DevOps is also a hard space to build a product in. Lots of competition, especially with open source, but also everyone's setup and needs are a little different.
Can you mention any examples? I'm keen to know. I personally don't use any such tools. I also agree that building any products in the DevOps space where many people are passionate about their DIY solutions is usually not a good idea.
Keep your low and no code solutions away. It's an instant pass for me. Even as config files. It can die in a fire.
You're forgetting the "dev" part of DevOps if you think we need or want no-code solutions. Code is actually easy. We need more code, code is easy. Testing and resilience are hard. Programmatic reuse and logic are essential. We need libraries in full programming languages that solve the hard problems, not closed off GUIs or low code config files that hide the control we actually do need for day to day work.
I think the world needs a git or C for infrastructure at this point. In short, yes to code.