spout

February 1, 2004 spout

On Behalf of Software Engineers, I’m Sorry

Sunday, February 1st, 2004

I just got off the phone with my step-mother and boy are my arms tired. She way trying to do a mail merge. I told her about a month ago put data into an Excel spreadsheet in a data-like format (and I sent her an example spreadsheet to start from). Then, after entering the data into her spreadsheet, I recommended to her that she choose Mail Merge from the Tools menu in Word and she’d be home free.

Of course, she wasn’t. For example, after choosing her Excel spreadsheet, she was asked if she wanted to use first name, Sheet1$, Sheet2$ or Sheet3$ as her data. Having zero idea what SheetN$ was, she chose something vaguely human-sounding, which was exactly what she didn’t want, then was frustrated when her data didn’t come up. Later, after going away to buy hundreds of dollars worth of books (none of them telling her how to do Mail Merge using words that she could understand, btw), she opened up her document and was presented with a dialog box asking whether it was OK to run an SQL statement. What’s SQL?” she asked. Nothing that any normal human should ever have to see,” I replied, growing more embarrassed about the state of the output of my industry by the minute.

Later, when we got the data working with the merge (Remote Assistance, even over a slow phone line to Fargo, ND, works *very* well, once I figured out how to take control of her computer [answer: Take Control in the upper left]), she turned her attention to reformatting her letter. For example, she’d pasted some text from the web, which, by default, left this weird web formatting instead of making it look like the rest of her letter, so the styles were very different. Luckily, selecting the text and turning off the bold was enough, otherwise I’d have either had to reformat her entire letter or talk her through doing it. And how did I tell her to turn off the bold? By selecting the text and pressing Ctrl+B? Why did I tell her that? Because Word had taken the Bold toolbar icon off the toolbar and I couldn’t imagine describing to her what the little chevron was for so that she could get it back.

I’ve listed only a small percentage of issues I worked through with her, but lest you think otherwise, my step-mom is no idiot. She’s a nurse anesthetist, so has to keep tons of details in her head all day long or people die. Also, she’s trained her dogs to win first place obstacle courses in competitions around the country, one of whom was said to be untrainable. But when it came to Mail Merge, she worked for three weekends straight before giving up and calling me. It’s clear to me that for anything but the simplest of tasks that computers are not even close to ready for normal humans. On behalf of the software engineers everywhere, I’d like to apologize to Charlene (my step-mom) and the rest of the normal humans everything who are merely trying to make computers actually work. Hopefully Longhorn will fix this problem, but until then, I recommended that she return her computer to the manufacturer and get herself a Nintendo. After working through this with her for over an hour, I was only half kidding.

Discuss

January 31, 2004 spout

What Would You Save If Your House Was On Fire?

Here. The one where I spend a peaceful Saturday morning contemplating my life's possessions.
January 31, 2004 spout

What Would You Save If Your House Was On Fire?

What Would You Save If Your House Was On Fire?

Saturday, January 31, 2004

On a recent thread on my favorite mailing list ever, Jon Kale answers the question what would you save if your house was on fire,” which triggered my own thoughts along this line.

Assuming I’ve already made sure that the humans and the pets were out of the house, I’d make sure to grab my Omega X-33 (purchased during the bubble, of course), but since I go almost nowhere without it, it’s not likely to be burned up w/o its owner.

Also assuming I had a set of back-up CDs/DVDs for the last year in my safety deposit box (which I don’t have right now… please excuse the pause while I purchase a DVD burner… OK, $155 got me a top-reviewed DVD+R/DVD+RW drive with 30 blank DVD+RW disks delivered), the thing I would most miss is my book collection. The computer books could be replaced on demand, but my collection of just-for-fun books has literally taken a lifetime to collect and cull down to just things that I really love (click on the picture to get a closer look).

Often, when I want something comfortable to read, I’ll scan the shelves til something pops out at me and re-read it. Also, when friends & family come to town, I often take them to Powell’s City of Books and we play the Top 5 Books of All Time” game, purchasing what they point out for me and writing their name in the book so that when I read it, I can talk about it with the recommender (man, I’ve gotten some wacky books that way…). Losing those books, especially the ones I haven’t gotten to yet, would really hurt.

On the other hand, because you never know when you’re going to need to jam, my goal is to fit my entire set of positions on a memory hypercube (or whatever). But how do I back up the books when the atoms themselves are so satisfying? I mean, how can I recapture the feel of my leather-bound The Complete Frank Miller Batman, the back-pocket-worn The Silicon Mage, my copy of The Hobbit and The Lord of The Rings signed by my mother when I received my Master’s Degree because she read them to me when I was 10 or the ancient copy of The Complete Sherlock Holmes given to me by my father and to him by his father?

But even if I wanted a lossy digital backup of my books, how do I do it? I mean, I can scan all of my books and graphic novels, but only by destroying them. Why haven’t books, which are produced in digital form, made the transition to electronic availability? Are we waiting for the Tablet PC to get to a point of ubiquity?

So, in summary:

  • How do I back up my favorite atoms?
  • What would you save if your house was on fire (after humans and pets)?

Discuss

January 30, 2004 spout

MS Blogging About Longhorn 14% of the Time

Here. Just following up again on When In Doubt, Ignore Longhorn to point out an interesting survey of MS bloggers by David Weller. Apparently, out of 56 recent blog entries by Microsoft employees, 8 were related to Longhorn. That's about 14%, which is a little higher than the 10% that I argued for, but I bet if you took out the ones from me (whose job it is to talk about Longhorn), we'd be closer. : )
January 30, 2004 spout

Betting on Longhorn-Only?

Here. The one where I address some specifics about what amout of effort you should be putting into Longhorn right now.
January 30, 2004 spout

Betting on Longhorn-Only?

Friday, January 30th, 2004

In response to my post yesterday (When In Doubt, Ignore Longhorn), Shaun asked whether he should be targeting Longhorn-only right now:

[ed: the following has been edited to remove identifying remarks at Shaun’s request]

Thanks for all the great posts and community participation over the past year. Your recent ‘Ignore Longhorn’ post alarmed me a bit. I hope that was not born from some aspect of it being pushed past 2006.

Anyway, I know you are busy, so I will get to the point. We are mid-sized, established s/w company, and a Microsoft shop to the core (SQL Server, Analysis Services, VB, we embed VBA etc…). I am facing a huge decision regarding building our next gen app architecture. We need to ship in 1H 2006, and (IMO) we need to target rich and reach, so Longhorn is on my list of possible directions along with some ASP.NET 2.0 / ClickOnce combination.

I am enjoying working with Longhorn (XAML in particular), but I’m having a hard time shaking the feeling that I am taking too much of a gamble if I go Longhorn-Only, but some of the aspects are just so compelling. On the other hand, I’d hate to make a huge 2-3 year dev investment in ASP.NET only to ship something in 2006 that is not revolutionary/differentiated. I firmly believe our existing 3 million lines of solid COM code has plenty of life in it too.

Any insight or advice you might have would be greatly appreciated. I know it is probably difficult without understanding our company or market, but maybe some general advice to someone who is targeting a 2006 release. I guess my other worry surrounds the Longhorn adoption rate, but obviously none of us can predict that!

Here was my answer:

Shaun, if you think that Longhorn is going to help you build a differentiated product that’ll help you be more successful, then great! That’s why we’re building it.

On the other hand, if I were you, I wouldn’t put all my money into a single investment. Instead, I’d use some diversification strategies like you would with your financial portfolio. At this point, the ship date of Longhorn, along with the list of features it will support when it ships, is merely speculative. I won’t put more than 10% of my available investment time/money/staff into it, leaving the rest of my portfolio for getting the most I can from my existing and/or near future technologies.

Specifically, you ask about ASP.NET 2.0 and Windows Forms/ClickOnce. Both of those technologies rock. ASP.NET is going to be the way to build web sites and services for the next decade at least, even after Longhorn’s been out for years, since it has the reach across our existing OSes and competing OSes. Plus, ASP.NET 2.0 has a dizzying list of new features that people will spend years just taking full advantage of. For reach, you can’t make a better investment than ASP.NET.

For rich, on the other hand, Windows Forms + ClickOnce is a killer combo. The updated Windows Forms in Whidbey along provides some amazing new capabilities, not the least of which is the new GridView, which you can read about in Michael’s new Wonders of Windows Forms piece. Also, look for a What’s New in Whidbey Windows Forms” piece in MSDN Magazine RSN. ClickOnce (which you can learn more about in Duncan’s ClickOnce piece and in Jamie’s ClickOnce talk) is the way to deploy rich clients in Whidbey and in Longhorn, so digging into that technology is a very good idea.

As time goes on and Longhorn becomes a more solid development investment, you should put more of your portfolio into it. If you’ve got plenty of time/money/staff, than 10% now could mean an entire pilot project in Longhorn, which would be a good thing. But if you’ve got limited amounts of time/money/staff that you really need to yield a dividend now, Longhorn is dangerous for you and should only be something you dabble with at this point.

For you specifically, a mid-sized company, you should carve off a chunk of your dev. staff to build a pilot in Longhorn. This lets you dabble while the rest of your staff is busy with existing and near future technologies. And as you dabble and notice things that don’t work at all as you expect or need, let us know! Operators are standing by to take your calls! We’re at a stage in our development process where we’re able to give much more attention to the fundamentals than we will be at beta, so the 10% you put into Longhorn now could yield large dividends in the future.

And as to your follow up comment, I’m happy that you enjoyed my response, but I’m pretty sure an autograph from Sting would be cooler. : )

January 29, 2004 spout

When In Doubt, Ignore Longhorn

Here.

The one where I list my favorite sources of information for development with today’s shipping .NET Framework.

January 29, 2004 spout

When In Doubt, Ignore Longhorn

Thursday, January 29th, 2004

A guy walks into an exotic car dealer and asks the salesman the price of the fancy new Ferrari in the corner. The salesman looks at him with a sad look on his face, shakes his head and says, I’m afraid, sir, that if you have to ask, you won’t be able to afford it.”

If you’re wondering whether you should be paying attention to the information on Longhorn that has appeared on the web and in the news lately, then you shouldn’t be. Longhorn RTM is years away. This is the most lead time we’ve given on any Windows operating system ever. The reason we did it was so that we could get super early adopters to give us meaningful feedback while we still had enough of the development cycle left to make meaningful changes. If you’re not a super early adopter, than Longhorn is just going to be noise that you should ignore til the beta hits.

For day-to-day development, you should pay attention to .NET 1.1 news sources. For the near future, you’ll want to listen for Whidbey, the next version of the .NET Framework, which should work on all supported OSes when it ships. Here are a list of my favorite news sources for current information and near future information:

.NET Framework 1.x Information Sources:

  • MSDN: The vast majority of existing and new information you’ll find on MSDN is on currently shipping technologies. My Developer Center brethren post tons of new stuff every month all about helping you be successful today. Also, one part of the Longhorn Developer Center that you should check out is the Preparing for Longhorn section, where I keep resources that you’ll need to know about today so that you can keep Longhorn in mind for tomorrow (or the day after tomorrow : ).
  • MSDN Magazine: MSDN Magazine does a fabulous job of helping folks take advantage of .NET 1.x and have recently been doing articles on Whidbey and Yukon.
  • MSDN Columns: If you haven’t seen the columns that MSDN hosts online, you’re missing a ton of great stuff from experts in the field. Besides the Longhorn columns (which you should ignore if you’re in doubt!), my personal favorite is Wonders of Windows Forms, which has also been focused on taking the best advantage of Windows Forms and where Michael Weinhardt has just started with a series of Whidbey Windows Forms topics that’ll make you drool.
  • GotDotNet: This site is host to a raft of content and tools and code samples from the .NET product teams along with active web forums.
  • CodeProject.com: CodeProject is my favorite user-contributions site and has tons of new source code samples and articles all the time about all manner of existing Microsoft technologies.
  • DotNet Newsgroups: The newsgroups are a hotbed of information on current technologies and are staffed by a large number of Microsoft employees to answer your questions.
  • International .NET Association (INETA): Don’t just sit around and code by yourself, find a user group near you!
  • DevelopMentor mailing lists: The .NET mailing list hosted at DevelopMentor launched a development culture. Their mailing lists are still tops in my book.
  • .NET 247: I can’t tell you how often my Google searches on Microsoft-related technologies yields an answer on this site.
  • Most Microsoft bloggers: Sure, Box, Anderson and Scoble hog the limelight, but some of my favorite bloggers concentrate on today’s technologies. Don’t miss Adam, Chris, Duncan, Dino, Kent or Raymond.
  • Whidbey Series on MSDN TV: If you want some info on the not-too-distant future, Erica Wiechers’s series of Whidbey topics on MSDN TV is a great place to start.
  • Whidbey/Yukon PDC talks: Contrary to popular belief, most of the talks at the PDC were not Longhorn-related and it’s not too late to catch the videos or download the slides if you weren’t able to catch them all.
  • Scott Guthrie’s Blog: For juicy bits of ASP.NET 2.0 information, you can’t beat Scott Guthrie’s blog.
  • theServerSide.NET: I haven’t spent much time on this site yet, but Richard Burte, an MS PM, says he likes it well enough to add it to this list.
  • What did I miss?

That’s not to say that Microsoft is going to stop talking about Longhorn in the WinFX newsgroups, on the Longhorn Developer Center and in blogs of all kinds. We do this so that those folks that can think about the distant future today have a chance to make their voices heard at a time when we can most take advantage of what they’re saying.

However, there continues to be more information than any human can consume on current Microsoft technologies, so don’t be alarmed when you see something go by with Longhorn in the title; just ignore it until you think that Longhorn can help make your business more successful. That’s why we’re building it after all. : )