A few more things that have come to mind.
- Lunches seemed a bit rushed. I was surprised to see that Wagga's schedule only allowed 30 minutes for lunch too.
Even though I liked the BBQ, they did appear to have problems keeping up with demand - eg. the second tray of cooked food came out just as we were heading back in.
- Not enough time for questions. Most sessions probably ran over-time (I suspect I was guilty of this too). Having a consistent 5 minute warning would probably help everything keep on track better.
- A better web site. I'm not convinced that the "news" page on ADNUG's site was the best place to promote the event and session times. Carl and Richard from DotNetRocks seem to agree - I was pleased that the event was promoted on their podcast, but they commented a number of times about the lack of information on the web page.
I'm thinking it either needs its own independent web site, or see if we can have a space on CodeCampOz.
Don't get me wrong, while I've listed things that I think could be improved, I did enjoy the weekend and got a lot out of it!
I just discovered that I was twittered (tweeted?) at CodeCampSA.
This limit caused us problems yesterday. For some reason, the temporary files weren't getting deleted.
The first clue was that the temp directory contained exactly 65535 .tmp files. The corroborating clue was that the last .tmp file was named "uplFFFF.tmp" - FFFF would be 65535 in hex.
The .NET Framework mentions this limit for the GetTempFileName method, but curiously the corresponding unmanaged GetTempFileName API doesn't (so I've submitted some Community Content to note this).
I discovered this morning that there are no buses or trains that go to the city early on Sunday mornings. Thankfully my wife was able to drive me in instead!
ORM overview. A pity this wasn't before my LINQ talk yesterday, but hopefully it helped people understand the theory behind mapping objects to relational data.
Overview of features in Windows Mobile 6. Dave made use of Pocket Controller in his demo. He also mentioned using CompressSoapExtension to compress data with SharpZipLib going through web service calls.
A good presentation on the sales process, and how important it is that your web site is found by Google. I now have a better idea about "organic" (aka 'Free') search and "Paid" (aka AdWords) search.
Peter pointed out that for quick changes and campaigns, paid search is the way to go, as Google will display your new ads immediately, rather than waiting weeks or months for your site to get re-indexed.
Don't forget that keywords are what the client/customer types in to Google - they might not be the same names as you use in your business yourself.
Talked about K2 and MOSS, but I missed this session as I had to do some birthday present shopping.
DMV's - dynamic management views in SQL 2005. These views were originally developed for the SQL Team at Microsoft to aid in their internal debugging and diagnostics. They live in the SYS schema.
Greg showed how you can use CROSS APPLY to run a TSQL function for each row of a result set.
There's also a new feature in SQL 2005 SP2 that let's you view reports of your databases (you don't need Reporting Services for this to work).
An overview of NHibernate (seems like there's a bit of an ORM theme this year). Greg asked a good question about dealing with concurrency. As an NHIbernate user myself, I'll have to research this a bit more.
Yes, it was ironic that James - self-confessed Database non-fan was sandwiched between the two Greg SQL gurus :-)
SQL Server execution plans explained. Greg really knows his stuff and it was very worthwhile to see this talk, which was similar to his presentation to the Adelaide SQL group last year.
Remember, execution is serialised, read execution plans from top-right to bottom-left, and clustered indexes aren't always the best choice.
A talk about how Readify manage all their staff who are out there developing remotely.
They use Scrum, but the stand-up daily meetings don't really work if you're not all in the same place, or if you're all working on separate things.
They really like WSS v3, and use SharedView to share documents and screen views (eg. do pair programming remotely)