Reading a paper to build a research post from (yes, I'll write about the paper in question in a later post!) jogged my memory about an old case that perfectly illustrated the concept of a
Over at the ACM blog, there is a terrific article about software design that has direct application to network design and architecture. The problem is that once you give a monkey a club, he is
One thing I'm often asked in email and in person is: why should I bother learning theory? After all, you don't install SPF in your network; you install a router or switch, which you then
So far, in our investigation of the design mindset, we've— Observed, specifically asking what, applying questions about state, surface, and optimization in our examination of the network as it's actually deployed. Oriented, asking why, really
Before talking the final point in the network design mindset, ,act, I wanted to answer an excellent question from the comments from the last post in this series: what is surface? The concept of interaction
So you've spent time asking what, observing the network as a system, and considering what has actually been done in the past. And you've spent time asking why, trying to figure out the purpose (or
In a comment from last week's post on the design mindset, which focuses on asking what through observation, Alan asked why I don't focus on business drivers, or intent, first. This is a great question.
How does a network designer, well, actually design something? What process do you use as a designer to get from initial contact with a problem to building a new design to deploying a solution? What