3 ms·
Two thoughts. (1) Wrangling YAML is still coding; you’re using the API for a software system it’s just exposed in declarative YAML. I suspect your definition o
by sovietmudkipz 5y ago
Two thoughts.
(1) Wrangling YAML is still coding; you’re using the API for a software system it’s just exposed in declarative YAML. I suspect your definition of coding may be a bit narrower than mine, which is fine.
(2) I can’t help but thank of “no-code” solutions. They work great if you’re using the platform how the developers thought you would. However; beware when you start to improv/hack things around because you’ll find little support and extension points.
All this said I do agree with the sentiment that there are tool builders and tool users, and the tool user shouldn’t always be expected to know how to build tools.
- _8j50 5y agoYou're thinking of Ansible, I am thinking of Siemplify or XSOAR but for networking. A Graphical/visual playbook/workflow declarative system that exposes flexible building blocks (which in turn are backed by reusable pieces of actual code). It may not be "real code" but it is essentially a programming language as you alluded, except it allows engineers to focus on engineering networking solutions. Heard of Powerapps from Microsoft? They've had a ton if impact in the corporate world, similar logic. Instead of office macros and paying devs for scripts, office workers come up with workflow and connect input/output of building block elements/tasks and voila, they made an app!