Speaker
Description
It's 2023 so everything is automated in our network's because we're all so cool, we're all even using Python and Go instead of BASH and expect, but beyond simply writing code, do you know when to implicitly model your infrastructure vs explicitly model it? You have network design standards, but do you have coding and contributing standards too? What would they look like? Are you checking whether you're compromising supportability for ease of development?
I'm currently working on the deployment of a greenfield network and greenfield automation stack, in a group of people who range from "hardcore networkers with minimal coding skills" to "hardcore developers with minimal networking skills". Along the way we have all learned many lessons, some were lessons regarding coding, some were lessons regarding collaboration, some were lessons regarding automation strategies.
In this talk I will share some general lessons learned and considerations we've had to make, with the community, which most people should be able to relate to, in the new age of "automated everything".
| Talk Duration | 25 Minutes Presentation (+5 Minutes Q&A) |
|---|---|
| Presentation delivery | In-person at the meeting venue |
| Your consent for us to publish your name and affiliation as a Speaker on the UKNOF50 website | Yes |
