On Theory and Practice
I recently read a must-read blog post by Russ White in which he argued that you need to understand both theory and practice (see also Knowledge or Recipes and my other certification rants) and got a painful flashback of a discussion I had with a corner-cutting SE (fortunately he was an exception) almost two decades ago when I was teaching my Advanced OSPF course at Cisco.
Him: How many OSPF routers can you have in an area? (asked during the first morning of a 3-day course)
Me: As you’ll see in these three days, OSPF is a pretty complex protocol, so there’s no right answer. It depends on the area topology, the frequency of topology changes, the type of routers… For example, areas with low-end routers have to be smaller due to their limited CPU power, for example.
Him: You don’t understand. I need a simple answer that I can use in my desings.
Me: How about 50?
Him: And how many OSPF areas can you have on a router?
Me: Obviously that depends on the area size (and all other things I already mentioned), the CPU power of the router, what other things that same router is doing, the desired convergence speed…
Him: That’s too complex. I need a simpler answer.
Me: Well, the official answer is three. Is that good enough for you?
www.anvari.org/fortune/Miscellaneous_Collections/255425_the-great-tragedy-of-science-the-slaying-of-a-beautiful-theory-by-an-ugly-fact.html
Theory is when you think you know something but it doesn't work.
Practice is when something works but you don't know why.
Usually we combine theory and practice: nothing works and we don't know why.