C2C is a history now. I attended .NET stream and one session on SQL. The conference as a whole was very interesting, well organised, and basically developing. It was a Polish conference so most sessions were conducted in Polish but there were a couple of speakers from abroad too, and they spoke in English.
Basically I’m happy I had a chance to attend the conference. Below are my notes and comments. Please note they are my comments; should I write something which is not true or accurate, please let me know, sometimes pace was fast so I might have skipped something
Julia Lerman, the author of Programming Entity Framework, provided 10 Tips and Tricks on Entity Framework: working with foreign keys, improving the queries in LINQ and Entity SQL Queries, use Entities with .NET Generics, deal with Entity and Stored Procedures. An interesting presentation, very well delivered – Julia knows how to keep the audience focused
Piotr Leszczyński described the reasons why Dependency Injection is a bad thing. He recalled good programming practises which make the quality of the code better and delimits Dependency Injection.
Ingo Rammer’s presentation was a really good one. His pace was really fast but I kept tuned all the time! The title of his prestentation was ‘Hardcore Production Debugging of .NET Applications’. He showed how to debug applications which are already deployed on client’s machine which are not supplied with Visual Studio. He introduced the audience to WinDbg tool which allows doing so, even remotely. Ingo showed a couple of example usage scenarios, how to use WinDbg commands. That tool seems to bebrilliant! Ingo also introduced GFlags tool.
Udi Dahan was brilliant too! In ‘Avoid a Failed SOA – Business and Autonomous Components to the Rescue’ presentation he described why a couple of his SOA projects failed, and showed live examples of the correct attitude to creating SOA solutions. Basically the problem with delivering systems that confirm SOA assumtions might be too much focus on the technology aspects: don’t repeat yourself, loose coupling, the whole usage scenario as a path in a sequence of differnet Web Services. As a result loose coupling at design time can result in tight coupling at runtime, so architectural problems which can’t be solved with technology and hardware. The development team must keep the balance between business and technology, design and architecture. Udi presented PubSub (Publish Subscribe) concept, where components can subscribe to get (periodical) update from other componets and keep some (duplicated) data locally, which decreases the amount of communication between components and can result in more stable and therefore better solutions. Udi showed that SOA (Service Oriented Architecture) abd EDA (Event Driven Architecture) are twins and developer must keep that fact in mind.
Finally Marcin Szeliga talked about isloation levels in SQL Server – th theory and how they work in real world. Again a good, enthisiastic and funny speech, which helped me to realise I need to refresh some DB-related terms