CodeStock 2008
I'm a little late posting this as I was on vacation last week (or at least that's my excuse), but CodeStock registration is now open. Here's the info:
CodeStock's mission is to bring the best and brightest code experts to East Tennessee for a one day conference open to all developers. This is not a trade show with slick salesman giving prepared demos - this is a gathering of real programmers learning about the latest in technology from each other. Sign up now at CodeStock.org and join us for CodeStock 2008!
- Keynote by author and MVP Jeff Prosise
- 30 amazing sessions, by industry leading speakers
- An area reserved for Open Spaces (self-organizing sessions)
- Great prize giveaways including: VSTS 2008 Team Suite with MSDN Premium ($10,939 Value!)
- Space is limited, register today!
Feedburner
On a whim today, I switched all my RSS feeds over to Feedburner. Mainly, I was tempted by all the nifty stats they promise (I'm a sucker for stats).
So, for those of you interested, here are the new feed URLs:
A Post About How I Haven't Posted
It seems like it's been about a month and a half since I posted anything substantial. Which is sad, because I actually do have a nice long backlog of programming stuff I could post about. No, literally. I have a text file of about five or six topics I could write about.
Plus I could gripe about how Dungeons and Dragons 4th Edition turned the game into WoW.
I also considered posting about all the new header photos I've put on the site... mainly to give credit where credit is due. I'm not a narcissist, I just keep finding pictures begging to be tweaked into header images among other people's photos. (Like Charlie's picture of me in costume at MTAC, or Liz's random picture of me in the hall at MTAC, or Crystal's photo of me at the Knoxville Zoo.)
So, there's credit where credit is due. Also, if anyone needs some similar graphics for their website, I'd be glad to take a look at their photos and see what I can do. (I'm looking at you, Nathan, with your new site design. :P)
Also among potential blogging topics was the rantworthy call I received from a recruiter yesterday. He cold-called me about a developer position... because he found my name and my company listed on the ETNUG site. And so he called my company, and somehow eventually got to me... after going through my manager.
Which is awkward, since I'm about to start a new job, and have sworn that it's an opportunity that sort of fell into my lap and I wasn't looking. Which is true, but a call like that would make it seem like it wasn't.
So, yeah. Professionalism and confidentiality. It's awesome.
Anyway, that's a summary of what I could have been posting. Except I guess I just did, if greatly summarized.
I can technically blame preparation for MTAC, or preparation for a recent cookout at the house, or the fact that I'm about to start a new job, or the fact that I've had a lot of offers for contracting work (outside of my normal job) recently. And I'm going to blame the fact that I'm going to be on vacation in Florida next week for the fact that it'll probably be another two weeks before I actually post anything.
There. I have absolved myself of all responsibility for my laziness, despite the fact that posting about how you haven't posted is bad form in blogging.
I Almost Died On Sunday
Well, not really. But I like telling everyone that because it sounds cool. And it got you to read this post, right?
And now, you can enjoy it too, thanks to the magic of YouTube:
I obviously have no clue how to ride a motorcycle, and it's pretty clear that it would be safer if I didn't even try.
What's SharePoint Good For?
In a previous post I discussed some of the trials and tribulations I've encountered with the mandate that we replace our current document management system with SharePoint. From the comments on that post, it sounds like pretty much everyone hates SharePoint to some extent.Now, users, tend to hate anything that requires that they follow procedure or document their work, so it's not entirely SharePoint's fault. But some of it might be that SharePoint is being used for things it shouldn't be used for. It's a tool, and just like any other tool, it's only good for certain situations. And even more to the point, it seems to have certain economies of scale as far as productivity goes.
1 . 2 . 3 . 4 . 5 . 6 . 7 . 8 . 9 . 10 . 11 . 12 . 13 . 14 . 15 . 16 . 17 . 18 . 19 . 20 . 21 . 22 > >>