13 subscribers
Go offline with the Player FM app!
Podcasts Worth a Listen
SPONSORED


1 SISTER WIVES: The Brown Family Plans Garrison's Funeral, Gives NEW Details About His Passing. Justin Baldoni v Blake Lively UPDATES, First Pictures Of Micah Plath’s Broken Nose Have Surfaced!… 36:16
Fork Yeah! Git in Network Engineering
Manage episode 476020364 series 3444546
Network engineers have traditionally drawn a line between "our tools" and "developer tools," often rejecting powerful solutions that could dramatically improve our workflows. But what if we thought about tools the same way tradespeople do? A plumber wouldn't refuse to use a hammer just because it's "for carpenters" – so why do we resist Git?
In this eye-opening discussion, we explore how Git – the version control system created by Linux founder Linus Torvalds – can transform how network teams manage configurations, collaborate on changes, and maintain system history. Far from being "just for developers," Git provides elegant solutions to problems network engineers face daily.
Think about how many times you've emailed configuration files with names like "config_v2_final_REALLY_FINAL.txt" to your team, trying to track which version is current. As our guest William Collins puts it, "If you're versioning in the file name, you've already lost." Git eliminates this chaos by providing a structured approach to tracking changes that's actually remarkably similar to how routing protocols work – distributed nodes maintaining a consistent state through carefully managed updates.
We break down the differences between Git (the technology) and platforms like GitHub (commercial services built on Git), demonstrate how branching and pull requests can formalize peer review of network changes, and show why you don't need to understand every Git command to start benefiting from it today. Whether you're backing up configurations, collaborating on documentation, or building automation workflows, Git provides the structure and accountability that network operations desperately need.
Ready to stop emailing configurations and embrace a better way? Listen now to discover why Git isn't just for developers – it's for anyone who wants to work smarter.
Find everything AONE right here: https://linktr.ee/artofneteng
Chapters
1. Introduction to Git for Network Engineers (00:00:00)
2. Breaking Down Tool Barriers in IT (00:03:10)
3. Origins of Git and Its Purpose (00:06:02)
4. Git vs. GitHub: Understanding the Difference (00:13:00)
5. How Git Works Like Network Routing (00:16:37)
6. Practical Network Engineering Use Cases (00:22:12)
7. Benefits of Git for Configuration Management (00:27:49)
175 episodes
Manage episode 476020364 series 3444546
Network engineers have traditionally drawn a line between "our tools" and "developer tools," often rejecting powerful solutions that could dramatically improve our workflows. But what if we thought about tools the same way tradespeople do? A plumber wouldn't refuse to use a hammer just because it's "for carpenters" – so why do we resist Git?
In this eye-opening discussion, we explore how Git – the version control system created by Linux founder Linus Torvalds – can transform how network teams manage configurations, collaborate on changes, and maintain system history. Far from being "just for developers," Git provides elegant solutions to problems network engineers face daily.
Think about how many times you've emailed configuration files with names like "config_v2_final_REALLY_FINAL.txt" to your team, trying to track which version is current. As our guest William Collins puts it, "If you're versioning in the file name, you've already lost." Git eliminates this chaos by providing a structured approach to tracking changes that's actually remarkably similar to how routing protocols work – distributed nodes maintaining a consistent state through carefully managed updates.
We break down the differences between Git (the technology) and platforms like GitHub (commercial services built on Git), demonstrate how branching and pull requests can formalize peer review of network changes, and show why you don't need to understand every Git command to start benefiting from it today. Whether you're backing up configurations, collaborating on documentation, or building automation workflows, Git provides the structure and accountability that network operations desperately need.
Ready to stop emailing configurations and embrace a better way? Listen now to discover why Git isn't just for developers – it's for anyone who wants to work smarter.
Find everything AONE right here: https://linktr.ee/artofneteng
Chapters
1. Introduction to Git for Network Engineers (00:00:00)
2. Breaking Down Tool Barriers in IT (00:03:10)
3. Origins of Git and Its Purpose (00:06:02)
4. Git vs. GitHub: Understanding the Difference (00:13:00)
5. How Git Works Like Network Routing (00:16:37)
6. Practical Network Engineering Use Cases (00:22:12)
7. Benefits of Git for Configuration Management (00:27:49)
175 episodes
All episodes
×




1 Is Network Automation Worth the Struggle? 1:02:58

1 Making Ethernet Cool Again—The Ultra Ethernet Consortium 1:01:17



1 Bytes and Books: EVPN VXLAN, with author Aninda Chatterjee 1:02:20

1 Net Eng career success now and in the future, with Dr Nic 1:15:46

1 Exploring the Future of Networking with IPv6 Adoption 1:18:55

1 Sponsored - Meter’s Approach to Full-Stack Networking 57:52

1 The State of the Network Engineering Union, with William Collins & Scott Robohn 1:08:05

1 (Sponsored) Simplifying Data Center Management with Apstra 43:27

1 Career Paths Beyond Network Engineering: What’s Next? 59:04
Welcome to Player FM!
Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.