Craig Johnson's Radio Weblog : Serendipity happens!
Updated: 01/22/2003; 9:00:28 AM.

 

Subscribe to "Craig Johnson's Radio Weblog" in Radio UserLand.

Click to see the XML version of this web page.

Click here to send an email to the editor of this weblog.

 
 

Wednesday, January 08, 2003

The drought continues - YMMV

This last weekend we traveled west to Breckenridge via US 24 and CO 9 from Colorado Springs.  The whole trip to Hoosier Pass was brown, dry and it is clear that the whole South Park area is very dry.  Once we crossed over the pass, we were immediately into the snow which was at least a couple of feet deep in shade.  I would guess that it is mostly left over from the early season big snow that come through the northern and central mountains, but which had minimal impact on us.

So if you want to find snow, best to stay north of Hoosier Pass.  That would be between Alma and Breckenridge on this map.


11:10:05 AM    comment []  

Nice writeup on the complexity problems in networking

Via Tomalak's Realm, a link to the latest Bob Frankston article called "Bad Coupling".  This is related to the "leaky abstraction" discussion that took place recently on Joel Spolsky's "Joel on Software" blog.

There seem to be two entirely different ways that abstractions can leak.  The first is what I will call original sin:)  In this case the development team seeks to make an abstraction that simplifies the development effort, but inadvertantly does not deal with some error or boundary condition well and suddenly, the underlying software reaches out and bites. This kind of leaky abstraction simplifies software development but can lead to nasty failures.

The second way an abstraction can leak is in the ways described in the Frankston article.  Well meaning engineers stretch the existing infrastructure abstractions in ways that work, but in a very different dimension than the original abstraction.  In these cases, the leaky abstraction complicates software configuration while enabling capabilities that were not envisioned or accepted by the original abstraction's developers.

If you are developing software, the first kind of abstraction will be your biggest concern (unless you are one of those who gets to write the configuration wizards:)).  If you are a purchaser or user, the second kind of leaky abstraction will intrude in unpleasant ways. When this second type of leak becomes embedded in the infrastructure, the whole community pays with configuration taxes for a very long time!


10:31:49 AM    comment []  

© Copyright 2003 Craig Johnson.



Click here to visit the Radio UserLand website.

 


January 2003
Sun Mon Tue Wed Thu Fri Sat
      1 2 3 4
5 6 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29 30 31  
Dec   Feb