It has been my pleasure to spend the last 2+ years writing with Mike Wienhardt. I remember fondly his first piece. When I give feedback, I work very hard to let the author know just exactly what I think so that they can bring their work to its highest possible potential. When Mike sent me his first draft, I was as careful as I could be to point out the parts that I liked to let him know that he had real potential, but basically, I ripped it apart. I have literally caused authors to tear up reading my feedback in the past, but I give Mike credit — he turned his piece around and came right back for more. We did this 5 or 6 times, but by the end, his first piece was better than most of the experienced authors filling magazines and web sites. It has been a real pleasure watching him grow into his writing talent and it made me very happy when he accepted the major writing duties on the 2nd edition of Windows Forms Programming in C# and when he took over my Wonders of Windows Forms column.

In his most recent blog post, it was very interesting to read about Mike working his way through the worst part of writing: writer’s block. Nearly all authors get this occasionally and it’s a real killer (and a pox on those authors that don’t suffer from it). It makes me proud to see him so concerned about his writing that he’s willing to share these kinds of experiences with the world. I wish more engineers took that kind of pride in their work. You’re setting an example for us all, Mike.

It’s generally know that the thing we call software “engineering” is nothing like that. We just don’t have anything like the rigor that real engineering disciplines do and we need them. I wonder if Brian’s quest to understand the real software life cycle and codify them constitutes another step down the road that the other engineering disciplines took to become predictable, schedule-able, reliable, budget-able and robust. I hope so.

I haven’t read Coder To Developer, but I love the term that secretGeek has pulled from it: “Inch-Pebbles.” When I was running DevelopMentor Software I learned to schedule from my then-mentor John Robbins, who learned it at NuMega (of BoundsChecker fame).

John’s insight was that nobody can look at a software release or even a feature and come up with an accurate schedule. Instead, they hold up their thumb in the wind and say, “Hmmm… Two weeks.” Of course, it’s never anywhere close to that. However, if you break something down into tasks of 1-2 days, aka “inch-pebbles,” those can be accurately estimated and then rolled up into how long each feature and then each mile-stone will actually take (“What? Three months?!? I had no idea…“). Once I learned how to schedule debugging time (rule of thumb: as long as coding time), we were able to schedule our software to w/in a week or two (although John, to show off, would pad a little and pick the day and time and deliver the golden master CD with balloons, champagne and marching band music : ).

At the time, we didn’t have a name for the granularity that could be accurately scheduled and, since I haven’t read Mike’s book, I don’t know how he defines the term “inch-pebble,” but from now on, that’s what I’m going to call it and if that’s different from what Mike called it, well, then he’ll just have to update his definition in his next edition. : )

Here.

I love Luke’s RSS Aggregator [1]. He loves my book. For what more could a man ask?

[1] I just tried the lastest RSS Bandit — don’t get me started…

Here. The one where I spend a day at jury duty but don't actually get to serve on a jury (and realize that serving on a jury was pretty darn unlikely in the first place).

Friday, May 28, 2004

Today was the first time that I was called to jury duty, even though I’ve been eligible for almost half of my life. I always dreaded being called when I was a consultant because the $10/day didn’t cover a day’s meals, let along the revenue I would miss as the sole breadwinner of the family. However, much like the body puts off illness when you just can’t afford to take the time (stress has its uses), my dread seems to have put off my jury duty ’til I had a full-time job with enough redundancy to live w/o me for a day or so.

Even when your job pays, most folks seem to want to get out of jury duty in any way possible. George Carlin says that the best way to get out of it is to admit to the judge that you know how to tell if someone is guilty, “It’s all in the distance between their eyes…” Personally, I’m a believer in America’s system of justice (I’ve often fantasized about a life as a prosecuting attorney and as a judge), so I didn’t mind serving my turn on a jury. Unfortunately, it was not to be. While I went down to the court house, my number wasn’t even called to appear on one of the two juries needed today.

Doing a little math, I found out that the overall odds of me actually being on a jury were actually pretty low. Here are the stats:

• 47 people showed as potential jurors on 2 juries

• 28 were called for the 1st jury, of which 12 were needed

• 15 were called for the 2nd jury, of which 6 were needed

• According to the State of Oregon Washington County Jury Director, 70% of people that show up for a trial see the assembled jury and decide to take the plea bargain after all

• Therefore:

  • Folks called to jury duty that were actually put on a potential jury: 91.5%

  • Percent of juries, once formed, that are used: 30%

  • People called for a jury actually placed on that jury: 42%

  • My chance of actually serving on a jury today: 11.5% or less than 1 chance out of 8

  • The opportunity to make the US justice system real for the brothers Sells w/o them actually committing a crime: priceless

Discuss

Here.

Steven Edwards is an OSS guy working with the Wine guys to build a new version of Windows from scratch called ReactOS. They’ve got 20-30 people, they’ve been working on it for a few years and they’re 6-8 months away from getting client-side of networking to work to the point that it supports HTTP.

Oh my god.

Why would anyone want to waste time doing this? I don’t even like to build my own autocomplete listbox when it’s already been done and that’s only about 12 lines of .NET code! Why the hell would anyone want to build Win32 all over again, let alone Win16 (what the Wine guys do)?!? We have all these programmers with all this free time and all they can think to do is to clone OSes and applications that have already been built? Why not add something new into the world?

I just don’t get it…

Newsgroups, mailing lists, web forums and blogs (with comments) are all very similar. Fundamentally, they’ll all about posts and replies. Sometimes the posts are replicated to servers around the world, acccepting replies in the same way. Sometimes the posts are replicated to a set of subscribers via SMTP and replies come in via POP3. Sometimes the posts are part of a web page and provided via HTTP, using HTML forms to take replies. Sometimes the posts are served up via a centralized server using HTTP + RSS or HTML, accepting responses via HTML forms or the CommentAPI. Fundamentally, it’s all the same thing, though: posts and replies. Why do I have to suffer with the limitations of any one of these protocols just to hang out with my friends to talk shop?

I don’t like newsgroups because I don’t like having a separate reader outside of my mail reader (and NewsGator ain’t anywhere close to what I want yet). Plus, newsgroups are very susceptible to spam, although the MS newsgroups are carefully patrolled to kill it before it spreads.

I don’t like web forums because I either have to poll the site (which RSS has cured me of) or the integration of the forum into my mail reader is limited to notification only. Plus, every single web forum has a vastly different UI and set of features and the inconsistencies bug me. On the other hand, web forums are pushing the envelope on features that I really want, like author and content ratings. I love mailing lists, but don’t want to duplicate any of the WinFX newsgroups in mailing lists just yet to avoid fracturing the budding developer community.

Blogs are wonderful, of course, and RSS is the only thing that’s worth me spinning up a whole separate reader than my mail reader, but it’s impossible to follow a thread of conversation between blogs or comments on other people’s blogs. On the other hand, the server-per-poster model is great because I can just subscribe to the posters that I like, increasing the signal to noise ratio substantially.

I think we should pack all of the features of mailing lists, newsgroups, web forums and blogs into a single backend and expose it via HTTP, NNTP, SMTP/POP3 and RSS as appropriate. Is it time for a new protocol that can be dumbed down to the existing protocols for the diehards that won’t give up their readers of choice? Personally, I’d like to get everything via SMTP/POP3 except for my RSS feeds (although I don’t know why — maybe it’s just that I can’t seem to get a handle on a keyboard-only mode for RSS reading in NewsGator the way I can in SharpReader…).

Discuss