2 ms·
You never really state why network engineers should not be required to write code, and imply an arbitrary limit of "domain-specific GUI" and YAML/golang. What'
by unethical_ban 5y ago
You never really state why network engineers should not be required to write code, and imply an arbitrary limit of "domain-specific GUI" and YAML/golang.
What's the difference between writing if/else/commit() in golang, vs. writing the commands in a proprietary command language, writing the inputs in Excel, and then pasting the combination into a terminal?
Coding/APIs/etc. should be a required course for any dev/sec/ops person. APIs and glue code are the future.
- _8j50 5y agoI state specifically why netengs should not write code. I don't like yaml. I think you haven't seen a good nocode solution. What's the difference? They are both essentially programming languages except nocode allows abstractions, modularity and building blovks that lets networkers focus on network state and infrastructure. Similar to R helps data scientists focus on data science, matlab allows mathematicians to focus on math, powerapps allows office workers to focus on automating office work. Your last comment: I agree, except neteng people are not dev/sec/ops. And tbf, asking people to wear 3 hats and be really good at all, and expect those people to be replacable and then whine about lack of talent is bullshit! Have a dev build building blocks sec and ops people can use. If you have people wearing 3 hats then they should be there to enable specialists not to be your developer and network engineer and it admin and cloud architect and operations engineer and SRE and security engineer and compliance auditor and whatever else. Do things right, try to do them right the first time and learn from others' mistakes!