Russ

Author Archives: Russ

Hedge 315: Engineering Psychology

We often talk about “human infrastructure” in network engineering–but what does this mean, and how do we help engineers “produce” while helping them to flourish as individuals? Catherine Hicks joins Tom and Russ to discuss the psychology of software engineering, and how the lessons learned apply to network engineering.

download

You can find Catherine’s new book on the psychology of software engineering here.
If you would like to follow Catherine’s writing in this area, including the impact of AI on work, you can find her blog here.
You can connect with Catherine on LinkedIn.

Hedge 313: Out of Band Management Networks

Most designers and operators default to carrying all traffic–including network management traffic–across the same paths as application data, or in band. Is this the right choice, or should operators seriously consider creating an out-of-band network just for network management? If you decide to build an out-of-band network, what are some of the considerations and lessons learned? Daryll Swer joins Tom and Russ to discuss.
 

 
download

Hedge 312: Keys and DNS

The entire technology world has, for decades, treated the IP address as a shorthand host identifier. This is clearly not the way IP was designed, but what are our other choices? In this episode of the Hedge, Scott Robohn joins Russ And Tom to discuss a recent paper arguing cryptographic keys should be the primary host identifier, and another article on the centrality of DNS to the Internet.

download

Hedge 311: The Dangers of AI

We are often told that if engineers who don’t go “all in” on AI will be left behind. While there are a few voices who argue that AI can be a dangerous tool, impacting not only the quality of our work, but the very quality of our thinking skills. Doug Smith, a critic of using AI for engineering, joins this episode of the Hedge to argue the contrary view of AI.

What are the dangers of relying on AI?

download

You can find Doug’s blog here.

Hedge 309: DNS Persist

As DNS is more widely used to distribute certificate information, proving ownership of a resource becomes more critical. The constant challenges required to prove resource ownership, however, increase delay in connecting or using a resource. DNS persists–as the name implies–creates a persistent connection between a resource and a certificate authority. Henry Birge-Lee, Michael Slaughter, and Shiloh Heurich join Russ and Tom to explain how this new record type works and it’s importance to DNS.
 

 
download

1 2 3 169