I'm back from some much needed time off, and here's an interesting idea that was sitting in my inbox on my return.

Check out the .NET Developer Virtual Conference, October 28 - 30, 2008, online everywhere. The conference is a very reasonable $100 for three days of content, with more than 30 how-to sessions. Julie Yack is the conference chair, and she got the idea after being very impressed with a SQL virtual conference she attended.

The speaker roster includes Ani Babaian, Rob Bagby, Kathleen Dollard, Scott Golightly, Tim Heuer, Ben Hoelting, Tim Huckaby, Dr. Neil Roodyn, Chris Sutton, and David Yack. That's quite some line-up.

Julie also volunteers with INETA, so if you are a member of an INETA user group, ask your user group president to contact Julie for a special discount.

Graham Watson, senior marketing manager at Microsoft has announced that Culminis will be transitioning to a volunteer-based organization, similar to INETA. Culminis is the association of Microsoft IT Pro user groups, sister organization to INETA which is the association of .NET user groups. I have been working with Culminis members for the last several years co-chairing the Birds-of-a-Feather track at TechEd conferences.

As I understand it, Culminis has been receiving funding for staff as well as programs from Microsoft. On the other hand INETA's funding covers programs and minimal paid staff who support volunteers. Graham takes care to point out that Microsoft values user groups highly, and that there are pros and cons to each funding model. That said, Microsoft and Culminis will be working together to move their organization closer to the INETA model. My very best wishes to the Culminis crew through the upcoming transition period.

"The core services will be available to the new volunteer Culminis community and INETA as well as other associations such as PASS," writes Graham. "We think this is particularly advantageous to the community as a whole, as it ensures that Microsoft support is available to all User Groups and not just IT Pro groups."

Got a comment? Graham is really interested in your feedback.

Last week I gave a Windows Workflow Foundation (WF) presentation at the Portland Area .NET Users Group (PADNUG). I figured it's summer, a couple of days ahead of the Fourth of July weekend, I should be prepared to have six people in attendance. But, in truth, it was around to 30. Not bad considering the competition. And it was great group for breaking in my new WF talk with several excellent questions and comments from the audience. And there was general beer drinking and WF merriment at Gustav's afterwards.

A PDF of the slides is available for you to download and enjoy.

Increase and decrease font size from the keyboard. I got tied up in traffic on the way to the talk, which discombobulated me slightly, and I forgot to bump up the font sizes in Visual Studio the way I always do. Thankfully, someone called the small fonts to my attention. As if on queue, Rich Claussen talked me through Sara Ford's Visual Studio Tip #242: "Did you know… You can bind macros to keyboard shortcuts (or how to quickly increase / decrease your text editor font size)?" That totally rocks. Thanks, Rich. Thanks, Sara.

Change font and size of IntelliSense. While I was looking that tip, I ran across an equally awesome tip for presenters on Sara's blog, "How to change the font and font size for Intellisense: Statement Completion, Parameter Info, and Quick Tips." I can see this one will be really handy for presentations where I am using IntelliSense to discover and explore some kind of object model. Nice.

Our story so far... Michael Eaton started it and tagged Sarah Dutkiewicz who in turn tagged Jeff Blankenburg and he turned around and tagged Josh Holms who did the tag thing to Larry Clarkin who so totally tagged Dan Rigby who put the tag on Chad Campbell who played his tagster card on Pete Brown who taggerized Shawn Wildermuth and he tagulated Julie Lerman who tagified Camey Combs and she tagged me. Clowns to the left of me, jokers to the right, here I am, stuck in the middle with you.

How old were you when you first started programming? I was 12 years old and access to computers were damn hard to come by in 1972. There was a PDP-8e in the basement of the math department building at Oregon State University where my father was earning his PhD. As children of a grad student, my brother and then I were allowed to use it. There was also a student-built 60-bit glass storage computer down there, much larger and far less useful as far as I could see.

How did you get started in programming? I played around with both of those computers for a few months, poking my way around some basic concepts of assembly language. Then I got a used copy of the textbook for Basic programming, and a small student account for the CDC-6600 in the new computer center.

What was your first language? I dinked aroudn with the PDP-8e assembly language, but didn't master it, so that doesn't count. That means good old Basic was my first language. Dad finished his PhD and we moved to Bellevue, Washington. After some searching around, my brother and I got a Xerox educational grant for a study group of junior- and senior-high school students to buy Fortran textbooks and some time on Xerox Sigma 9s to hone our skills. Hey, man, don't horde all the Hollerith constants, okay?

What was the first real program you wrote? The first program that I got paid for, if that makes it real, was in college. I wrote a pretty large simulation of the effects of Saturn's moons on its rings for a physics professor. That was in C.

What languages have you used since you started programming? Basic, Fortran, C, Pascal, C++, Forth, IA (x86) assembler, C#, Visual Basic .NET, and XSLT. I've experimented with a dozen others, stuff like Cω, Haskell, and F#.

What was your first professional programming gig? I took a year off from college in 1979 and landed a job with a small time-sharing firm, doing custom programming as well as operating a few PDP-11/70s. I remember working on several small projects, one of them was tracking oil well shareholders and productions. Another was running statistics on horse races.

If you knew then what you know now, would you have started programming? Absolutely yes. Without a moment's hesitation.

If there is one thing you learned along the way that you would tell new developers, what would it be? Cultivate a passion for learning. Everything in software development changes all the time. If you don't love learning new stuff all the time, you are in for a rough ride.

What's the most fun you've ever had... programming? Gosh, that is a tough one. Once I wrote a call-graph profiler for a language that didn't have one, and used it to analyze and boost performance about eight-fold. The combination of writing the tool and applying it was totally cool.

Who are you calling out?  Friends, please forgive me: Scott Hanselman, Sam Gentile, Adam Kinney, Jesus Rodriguez, and Pat Helland.