mike's web log

Entries as of Wednesday, November 19, 2008
 

Blog Search


(Supports AND)

 

Google Ads

 

Technorati

 

Feed

Subscribe to the RSS feed for this blog.

See this post for info on full versus truncated feeds.

 

Quote

Novels could be called thought experiments. You invent people, you put them in hypothetical situations, and you decide how they will react. The 'proof' of the experiment is if their behaviour seems interesting, plausible, revealing about human nature.

— David Lodge



 

Navigation






<November 2008>
SMTWTFS
2627282930311
2345678
9101112131415
16171819202122
23242526272829
30123456


 

25 Most-Visited Entries

 

Categories

  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
 

Blogs I Read

 

Blog Statistics

Dates
First entry - 6/27/2003
Most recent entry - 11/19/2008

Totals
Posts - 1966
Comments - 1899
Hits - 970,096

Averages
Entries/day - 1.00
Comments/entry - 0.97
Hits/day - 492

Update every 30 minutes. Last: 12:03 PM Pacific

 
   |  Roundup

posted at 01:14 AM | | |

Tired. So tired.

Kafka for the Kindergarten Set. Aaron Swartz with another dispatch about our educational system. He doesn't like NCLB-inspired testing:
Every year, a couple months before school ends, a kind of controlled experiment happens in NCLB schools: The principal remains the same, the teachers remain the same, the students remain the same. The only thing that changes is that the test is over, forgotten until next year starts. And suddenly everything changes: test prep boards come off the wall, students start writing poetry, they go on field trips and do science experiments, they work in groups and do real reading.

City Museum Photo Tour. Sabrina visited St. Louis over the weekend and sent me a link to this. Looks amazing, I'd love to go.

Fox Says, "Smile, You're Under Arrest". Summary: “It’s COPS as comedy and no one’s ever tried it before." Reality TV: it's a race to the bottom. (Hey, maybe that's a new show: Race to the Bottom.) [via naum]

It's Lovely! I'll Take It. Subtitle says it: "A collection of poorly chosen photos from real estate listings." Everything from bathrooms with underwear hanging up, to bedrooms with guys lounging on the bed, to $500K houses with plywood in the windows:


Ya know, the bar is very, very low for real-estate listings.

[via Kim]

[categories] , ,
[tags] schools, no child left behind, st. louis, city museum, FOX TV, real estate, reality TV

   |  The dad-in-law ... again

posted at 11:11 PM | | |

Earlier this year, the Seattle P-I ran a piece about doctors who do housecalls. The featured patient was John Devine, my father-in-law. We found this amusing because John has a knack for attention.

Case in point. KING 5, one of our local TV stations, picked up the story and they sent a reporter to go tag along with Sarah Babineau as she made her rounds. The story aired today. And which patient was featured? Correct:


And this is exactly what you'd expect him to say:
If it weren't for Babineau, Devine wouldn't see a doctor as much as he should because he likes to stay right where he is.

"I specialize in inactivity," said Devine.
Once a ham, always a ham, I guess. :-)

[categories]
[tags] doctor, housecall, KING 5, news, TV

   |  Well, I think they're interesting

posted at 09:23 AM | | |

Sarah and I read a lot, and we typically have multiple books scattered around the house that are at various stages of completion. In spite of our book diet, we still are always on the lookout for new things. For example, no Costco trip is complete without a scan through the books. Instead of buying, tho, we usually write down interesting-looking titles and then add those books to our respective queues at the library.

For all the reading we do, we don't overlap that much. I read about history and technology, and I seem to end up reading novels about middle-aged men (#, #, #). Sarah reads about medicine, public health, and biography, and she'll have a go at all sorts of things might grab her eye on the shelf at the library. Plus she reads novels of all sorts, including, for purposes of parental oversight and solidarity, books currently popular with her girls (#).

The other day I found two books at Costco that seemed interesting: The Airplane by Jack Spenser[1], and Hitler's Empire: How the Nazis Ruled Europe by Mark Mazower. I believe I've established that I have an interest in aviation. Jack Spenser was the co-author of 747: Creating the First Jumbo Jet and Other Adventures from a Life in Aviation, and has, among other things, been the director of the Museum of Flight here in Seattle. The book on Hitler's empire brings together an early and intense interest on WWII with the fact that I studied German in college and that one of the best classes I had was a 400-level class in 20th-century Germany.[2]

I came home and put both of these in the library queue. The library site helpfully told me that I was, respectively, #4 of 4 holds on zero copies, and #16 of 16 holds on zero copies. The library, it seems, was still waiting for their own copies, with patrons ready to read as soon as the books came in.

Later that day I was telling Sarah about this zero-copies thing at the library. She looked at me for a second and then said, "You know ...," which I thought was a preface to a remark about the library queue. She continued, "... both of those titles sound about as interesting to me as watching paint dry." Heh. I have no idea what she's talking about. How could someone not find books about aviation and WWII fascinating, really? :-)


[1] Another noun book.

[2] In fact, the book here might cover a lot of the same ground that one of the texts for that class did: Hitler's War Aims by Norman Rich.

[categories] ,
[tags] aviation, books, history, world war II, library

   |  Apple style guide

posted at 05:34 PM | | |

Gordon Meyer links to the latest incarnation of the Apple style guide (PDF). Of course, many of the entries contain familiar advice. (You'd be hard-pressed to find style guides that disagree with much of what's in here.)

Still, I was interested that some of the Apple style recommendations are different than ours at Microsoft (ie, in MSTP). Here are a few examples of where Apple has a different style:
  • companywide (v company-wide)
  • dialog (v dialog box)
  • email (v e-mail, e-mail message)
  • filename (v file name)
  • web (v Web)
  • webpage, website (v Web page, Web site)
I wonder if the Apple recommendations reflect more, you know, modern sensibility about these terms. Time will tell, I suppose.

[categories] ,
[tags] MSTP, style guide, Apple

   |  Roundup

posted at 06:45 AM | | [1] |

A dollop of information in an easy-to-open, obselescence-resistant package.

Amazon Frustration-Free Packaging. Yay. Amazon is leaning on working with manufacturers to create less-wasteful and, incidentally, easier-to-open packaging. Here's a picture from their site:


[via kottke ... I think.]

Time stands still. Michael Broschat has a Kodak photo CD that's only 10 years old, but already the format is obsolete and he can't read the images. As the pace of technological innovation accelerates, so does the pace of technological obsolescence.

Monster Smart. [video] Seems to be missing the point, somehow. (Turn audio down -- it's wretched and not needed anyway.) [via Friend Dennis]

How 10 Famous Technology Products Got Their Names. Where did the name iPod come from, anyway? [via Code Project]

[categories] ,


   |  Every little bit counts

posted at 10:25 AM | | |

You might not normally think of software as a product that you can slap an Energy Star sticker on. If so, you just haven't thought about it enough. However, the people who created Notepad++, a text editor, have considered green design for their coding. From their Web site:


By optimizing as many routines as possible without losing user friendlyness[1], Notepad++ is trying to reduce the world carbon dioxide emissions. When using less CPU power, the PC can throttle down and reduce power consumption, resulting in a greener environment.
How have you coded green today?


[1] They're also helping to reduce the critical -i- shortage here.

[categories] ,


   |  How not to honor veterans

posted at 01:41 PM | | [2] |

It never ceases to amaze me how willing businesses are to appropriate any holiday for their own commercial purposes. This showed up in my Inbox recently:



Presidents' Day, well, whatever. When the Feds combined Washington's and Lincoln's birthdays to make a generic holiday, and then made it one of their Monday-based "observed"-type days off, the shine was pretty much off that particular celebration.

But Veteran's Day, for heaven's sake. This is a holiday that's about reflecting on service and on sacrifice:
To us in America, the reflections of Armistice Day will be filled with solemn pride in the heroism of those who died in the country’s service and with gratitude for the victory, both because of the thing from which it has freed us and because of the opportunity it has given America to show her sympathy with peace and justice in the councils of the nations.

-- Woodrow Wilson [source]

On [this] day let us solemnly remember the sacrifices of all those who fought so valiantly, on the seas, in the air, and on foreign shores, to preserve our heritage of freedom, and let us reconsecrate ourselves[1] to the task of promoting an enduring peace so that their efforts shall not have been in vain.

-- Dwight D. Eisenhower [source]
Free shipping, c'mon. You can't even pretend that that's anything but blatant hucksterism. If they really wanted to observe Veteran's Day, they could try the two minutes of silence that is observed at 11:00am in many places to remember the fallen of WWI. Like, shut down the Web site for two minutes and post a tribute to veterans for those two minutes. Yeah, right. That would be too much of a sacrifice, no doubt.

I was born at a unique time in 20th-century American history. My grandfather fought in WWI; my parents' generation (including my stepfather) fought in WWII, and some later in Korea. Older brothers of people I knew (and indeed, friends of mine now) were in Vietnam. Children of people I know now are in Iraq and Afghanistan. I had the good fortune that at no time during what would have been my eligible years were we involved in any major conflict. I did not join the service as a volunteer, nor was I ever called up. Veteran's Day is not about me in any way. Even so, I think it's disrespectful to use the holiday as an excuse for simple commerce. Instead, how about we just salute those who have served.


[1] Sounding very Lincoln-esque.

[categories] ,


   |  When do you use Design view?

posted at 06:09 PM | | [2] |

At PDC2008, Jeff King demonstrated features and improvements that his team is proposing for the next release Visual Web Developer. Among them are lots of tweaks to HTML editing. This got me thinking about my own use of Design view and Source view, and when and why I use each.

From one narrow perspective, the history of the Visual Studio tools for creating Web pages -- starting with Visual InterDev (remember him?) through Visual Studio 2008 SP1 -- has been a history of improving Design view. If you remember that far back, in Visual Studio .NET (for versions 1.0 and 1.1 of ASP.NET), the page you edited in Design view and the page in Source view were related but separate; when you switched views, each view recreated the page from scratch. Lots of people did not like how switching views could hose up your formatting. Plus the editor inserted some Visual Studio-specific (and of course non-standard) attributes into the page to give itself some formatting clues, and that likewise was not popular in certain quarters.

In Visual Studio 2005 and beyond, it was a priority to make sure that when you switch views, Source view formatting is maintained scrupulously. And (AFAIK) thus it is: what you do in Design view is persisted in Source view, and in addition any custom formatting you've done in Source view is retained. We don’t mess with your markup. (Selection is maintained between views as well.)

And yet I spend most of my time in Source view. Partly this is because Source view itself has gotten more and more capable. You can drag from the Toolbox and you can use the Properties window. IntelliSense now works with pretty much everything. You can set options for how the editor formats tags and code.

I thought about it, and here's when I do use Design view:
  • Data binding. Specifically, I use the Design-view wizards to initially configure a data source control. For controls like GridView, if I'm already in Design view, I use the Task Pane to select a data source and set some initial properties (e.g., EnablePaging).


  • Template editing. I'll usually at least start template editing by using the Task Pane menu. I'll generally tweak thereafter in Source view.


  • Control property builders. In GridView or ListView, if I have to create TemplateColumn objects or some other non-default column or item type, I'll use Design-view builders.



  • Previewing pages. Of course, Design view does not provide true WYSIWYG; by default, there's a lot of detritus such as non-visual controls, borders for div element etc.[1] But because the page reflects current CSS settings, it's good for a quick look. For a real preview, tho, I run the page.


  • Creating handlers. I will double-click controls to create skeleton handlers for default events, and I'll often use the Properties window to create a handler for non-default events.



  • Adding a CSS style sheet to a page. It doesn't get any easier than dragging a .css file onto the page.
Here's what I don't use Design view for:
  • Dragging controls around to locate them to absolute x and y coordinates. Two reasons. One is that I rarely use absolute positioning, oops. The second is that I find that it can sometimes be dang hard to select an individual control within, say, nested div elements.


  • Setting most control properties, unless: a) I already happen to be in Design view, or b) I'm dealing with complex properties for which a builder might be handy. Even then, for relatively simple complex properties many times I'll create (e.g.) ListBox items in Source view by hand.



  • Table editing. The table editor in Design view got a big overhaul in Visual Studio 2005, I think it was, and it's much better. Even then, I rarely use it. It never seems to do quite what I want.


  • Setting any kind of attribute on any kind of non-ASP.NET markup. I do pure HTML almost exclusively in Source view.


  • Working with styles. CSS editing facilities made huge progress in Visual Studio 2008. Indeed, if I remember to use the CSS editing windows while I'm in Design view, I'm always impressed. Still, I do CSS in Source view, which has been made easier by IntelliSense.


  • Master pages.

What do you use Design view for? When do you explicitly avoid it?


[1] Configurable, I realize. I haven't set up a macro to allow me to easily switch, tho. (Plus VWD Express doesn't support macros.)

[categories]


   |  Engineers who write/Writing for engineers

posted at 06:39 PM | | [1] |

In the latest MSDN magazine Richard Ward has a column titled "Engineers Who Write." It might also have been titled "Writing for engineers." Ward's thesis is that engineers need to be able to communicate in writing, and that this is harder than being able to communicate in person. One of things he sees in engineering documents, he says, is this:
A precise model helps, for example, when specifying the interactions between two instances, such as a network protocol. These forms can express the how of a design very effectively because they are, in a sense, only one step removed from the actual code expressing that design. They do not, however, explain the why of a design.
Emphasis mine. I have seen this approximately one (1) million times. Not unexpectedly, I almost always see it (don't see it?) in feature specifications, where (as Ward says), you find lots of detail about how to implement the feature, but very, very rarely do you find an answer to the question "What problem does this feature solve?" To the author of the document, and presumably to the immediate intended audience, this question has already been answered.

Ward makes a particularly salient point about how this type of information becomes less obvious, hence more necessary, as a document goes out to a wider and wider audience:
As the design trickles out from the original conception to the organization as a whole, the requirements for communicating with each new audience become broader. It is rarely necessary to take a low-level design document to a customer, but it is often helpful to have the requirements in a form that is both understandable to a diverse audience and written in a way that can appeal to the audience at many levels.
To pick one particular example, the very early documents for the ASP.NET MVC framework assumed that the audience already understood the MVC pattern and was interested in applying it to ASP.NET. (My guess is that overall this was a pretty small slice of the ASP.NET developer base.) As such, the documents did not contrast MVC with the alternative (Web Forms), nor provide any reasons for why a customer might choose between these models. The early docs dove straight into URL rewriting, mock objects, exposing controller methods, and so on -- in other words, they were aimed straight at an audience that already understood the overall approach and just needed implementation information.

As MVC was unveiled at conferences and in preview releases, it became clear what sorts of issues customers were raising. Does MVC replace Web Forms? No, we had to clarify. What do you use for the view leg of the model? Oh! ASP.NET pages. In other words, as the information went to a wider audience, fewer of the assumptions inherent in the design were obvious.

Over time, we've filled in a lot of these holes. What is MVC, anyway? Why is it useful? How does it contrast with Web Forms? Included in this last, tho you won't find it stated in exactly these terms, was an explanation of "What Web Forms problems does MVC solve?"[1]

I cannot count the number of times I have said to a writer "Tell me what I need to know if I walk up cold to this technology." By the time I finish reading the first page a document that describes a technology, I expect to know why I should be interested in it. You'd be surprised how often that doesn't happen.


[1] I was talking to Brian MacDonald the other day, and he noted that when he started working with C#, everything he read assumed that you were already familiar with C++ or with Java. I noted to him that the early ASP.NET documentation assumed you were upgrading from classic ASP. Assumptions about what your audience knows are especially a problem for 1.0 documentation, it seems.

[categories] ,


   |  Tim O'Reilly on Twitter

posted at 12:36 PM | | |

If you're a heavy Twitter user already, this won't be surprising. But for the rest of us, Tim O'Reilly summarizes nicely why Twitter is more than just a way to record what you are watching on TV:
So, if you wonder whether Twitter matters for business, remember, if you will, when people new to cell phones used to call each other to report the most trivial details of where they were and what they were doing; remember how blogs at first were thought of merely as personal diaries of no interest to anyone in business, and how they grew up to become the heart of a new media paradigm. For that matter, remember how the personal computer was dismissed by the titans of the computer industry as nothing but a toy.

The future often comes to us in disguise, with toys that grow up to spark a business revolution.

Twitter is like that.
I actually had an experience yesterday that made me think that maybe I'm starting to get it. I got a call from someone (long story, doesn't matter) who was looking for someone to live-blog an event. My very first reaction was "Shouldn't you be using Twitter for this?" Maybe they will.

Hat tip to Laurel at O'Reilly.

[categories]