nbsp;
One of the "great fears" advancing AI unlocks is that most of our jobs can, and will, be replaced by various forms of AI. Join us on this episode of the Hedge as Jonathan Mast at White Beard Strategies, Tom Ammon, and Russ White discuss whether we are likely to see a net loss, gain, or wash in jobs as companies deploy LLMS, and other potential up- and down-sides.
--------
36:56
Hedge 267: Can modularization solve people problems?
Solving technology problems often involves breaking a problem into multiple smaller problems, build interaction surfaces between the pieces, and glue the pieces back into a larger system. We also know every technology problem is actually a people problem--whether in the past, the present, or the future.
Given these two points, can we say something like: "If technology and people problems are interchangeable, we should be able to solve people problems the way we solve technology problems--via modularization?"
--------
32:59
Hedge 266: SR/MPLS
When most people think of segment routing (SR), they think of SRv6--using IPv6 addresses as segment IDs, and breaking the least significant /64 to create microsids for service differentiation. This is not, however, the only way to implement and deploy SR. The alternative is SR using MPLS labels, or SR/MPLS. Hemant Sharma joins Tom Ammon and Russ White to discuss SR/MPLS, why operators might choose MPLS over IPv6 SIDs, and other topics related to SR/MPLS.
You can find Hermant's recent book on SR/MPLS here.
--------
39:00
Hedge 265: Out of Band Networks
Out of band management networks were once more common than they are today. Should we go back to building out of band management networks? Should out of band management networks be virtual or physical? How can we sell out of band management networks to the folks paying the bills? Daryll Swer joins Tom Ammon and Russ White to discuss the importance of OOB management.
--------
46:32
Hedge 264: Documentation and Tech Debt
On this episode of the Hedge, Eyvonne, Tom, and Russ talk about topics near and dear to every network engineer's heart--documentation, legacy, and tech debt. What should our philosophy of documentation be? What are legacy, end of life, and tech debt, really?
Netherlands